All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Yong Zhi <yong.zhi@intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Bingbu Cao <bingbu.cao@intel.com>,
	Dan Scally <djrscally@gmail.com>,
	Tianshu Qiu <tian.shu.qiu@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/6] media: ipu3-cio2: make the bridge depend on i2c
Date: Fri, 16 Sep 2022 01:33:18 +0200	[thread overview]
Message-ID: <S230142AbiJTWql/20221020224641Z+958@vger.kernel.org> (raw)
In-Reply-To: <S229853AbiJTWkg/20221020224036Z+12888@vger.kernel.org>

drivers/media/pci/intel/ipu3/cio2-bridge.c: In function ‘cio2_bridge_unregister_sensors’:
drivers/media/pci/intel/ipu3/cio2-bridge.c:258:17: error: implicit declaration of function ‘i2c_unregister_device’; did you mean ‘spi_unregister_device’? [-Werror=implicit-function-declaration]
  258 |                 i2c_unregister_device(sensor->vcm_i2c_client);
      |                 ^~~~~~~~~~~~~~~~~~~~~
      |                 spi_unregister_device

Signed-off-by: Adam Borowski <kilobyte@angband.pl>
---
 drivers/media/pci/intel/ipu3/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/media/pci/intel/ipu3/Kconfig b/drivers/media/pci/intel/ipu3/Kconfig
index 39bd3be0b43d..65b0c1598fbf 100644
--- a/drivers/media/pci/intel/ipu3/Kconfig
+++ b/drivers/media/pci/intel/ipu3/Kconfig
@@ -21,6 +21,7 @@ config VIDEO_IPU3_CIO2
 config CIO2_BRIDGE
 	bool "IPU3 CIO2 Sensors Bridge"
 	depends on VIDEO_IPU3_CIO2 && ACPI
+	depends on I2C
 	help
 	  This extension provides an API for the ipu3-cio2 driver to create
 	  connections to cameras that are hidden in the SSDB buffer in ACPI.
-- 
2.37.2.609.g9ff673ca1a


  parent reply	other threads:[~2022-10-20 22:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 21:08 [PATCH 0/6] a pile of randconfig fixes Adam Borowski
2022-09-14 20:06 ` [PATCH 1/6] ASoC: mediatek: mt8186: fix an "unused" warning Adam Borowski
2022-09-14 20:06 ` Adam Borowski
2022-09-14 20:06 ` Adam Borowski
2022-09-14 20:13 ` [PATCH 2/6] certs: fips test: fix build failure with PKCS7_MESSAGE_PARSER=m Adam Borowski
2022-09-14 20:13 ` Adam Borowski
2022-09-14 20:13 ` Adam Borowski
2022-09-14 21:29 ` [PATCH 3/6] mtd: eject cfi_interleave code to its own header Adam Borowski
2022-09-14 21:29 ` Adam Borowski
2022-09-14 21:29 ` Adam Borowski
2022-09-15 23:33 ` [PATCH 4/6] media: ipu3-cio2: make the bridge depend on i2c Adam Borowski
2022-09-15 23:33 ` Adam Borowski [this message]
2022-10-10 18:33 ` [PATCH 5/6] i2c: mlxbf: depend on ACPI; clean away ifdeffage Adam Borowski
2022-10-21  6:43   ` Wolfram Sang
2022-10-21  6:47     ` Wolfram Sang
2022-10-21 12:43     ` Asmaa Mnebhi
2022-10-21 12:57     ` Khalil Blaiech
2022-10-10 18:33 ` Adam Borowski
2022-10-17  6:17 ` [PATCH 6/6] ASoC: Intel: boards: add missing dependency from realtek-common Adam Borowski
2022-10-17  6:17 ` Adam Borowski
2022-10-27 12:44 ` Mark Brown
2022-10-27 12:44   ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=S230142AbiJTWql/20221020224641Z+958@vger.kernel.org \
    --to=kilobyte@angband.pl \
    --cc=bingbu.cao@intel.com \
    --cc=djrscally@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tian.shu.qiu@intel.com \
    --cc=yong.zhi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.