mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-08-31 23:27:20 +00:00
fd404435d4
The ivsc drivers may use the ipu-bridge but currently it's possible to
link the ivsc to the kernel and ipu-bridge as a module. This won't work.
Require that the ipu-bridge is either linked to the kernel or disabled if
ivsc is linked to the kernel as well, by depending on IPU_BRIDGE or
!IPU_BRIDGE.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202406132238.3hXHG7nB-lkp@intel.com/
Fixes: 33116eb12c ("media: ivsc: csi: Use IPU bridge")
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
22 lines
890 B
Text
22 lines
890 B
Text
# SPDX-License-Identifier: GPL-2.0-only
|
|
# Copyright (C) 2023, Intel Corporation. All rights reserved.
|
|
|
|
config INTEL_VSC
|
|
tristate "Intel Visual Sensing Controller"
|
|
depends on INTEL_MEI && ACPI && VIDEO_DEV
|
|
depends on IPU_BRIDGE || !IPU_BRIDGE
|
|
select MEDIA_CONTROLLER
|
|
select VIDEO_V4L2_SUBDEV_API
|
|
select V4L2_FWNODE
|
|
help
|
|
This adds support for Intel Visual Sensing Controller (IVSC).
|
|
|
|
The IVSC support is split into two devices, ACE (Algorithm
|
|
Context Engine) and CSI (Camera Serial Interface), each of which
|
|
have their own drivers. The ACE is used to select the ownership
|
|
of the sensor between the IVSC and the host CPU while the CSI is
|
|
used to both select the routing destination for the data the
|
|
sensor transmits over the CSI-2 bus between the IVSC and the
|
|
host CPU and to configure the CSI-2 bus itself.
|
|
|
|
The modules will be called ivsc-ace and ivsc-csi.
|