From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 401F6C433E6 for ; Mon, 8 Feb 2021 09:29:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1089964E66 for ; Mon, 8 Feb 2021 09:29:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231537AbhBHJ2z (ORCPT ); Mon, 8 Feb 2021 04:28:55 -0500 Received: from mga18.intel.com ([134.134.136.126]:24640 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231485AbhBHJ0w (ORCPT ); Mon, 8 Feb 2021 04:26:52 -0500 IronPort-SDR: S/ISST09jyy+SUtOmfOlWAIbfIuC77OMlpSg9QeUcffugya2Uwt5tnZoqY4xVaCfZVwDtP+HHI ZLrhAJX4YLkw== X-IronPort-AV: E=McAfee;i="6000,8403,9888"; a="169367583" X-IronPort-AV: E=Sophos;i="5.81,161,1610438400"; d="scan'208";a="169367583" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2021 01:24:59 -0800 IronPort-SDR: XYpLvQcUd8ACZzWwabhcolCGs9tvWytDztxdqt31uv3R2FeAha3J2H6UmpoVe1LOhvp8Sn/oOr muZR2i5HUOJg== X-IronPort-AV: E=Sophos;i="5.81,161,1610438400"; d="scan'208";a="435568358" Received: from paasikivi.fi.intel.com ([10.237.72.42]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2021 01:24:57 -0800 Received: by paasikivi.fi.intel.com (Postfix, from userid 1000) id 0DCF22082C; Mon, 8 Feb 2021 11:24:25 +0200 (EET) Date: Mon, 8 Feb 2021 11:24:25 +0200 From: Sakari Ailus To: Mauro Carvalho Chehab Cc: Jacopo Mondi , Linux Media Mailing List , Laurent Pinchart , Jacopo Mondi , Stephen Rothwell , linux-next@vger.kernel.org Subject: Re: [PATCH] media: i2c: fix max9271 build dependencies Message-ID: <20210208092424.GP32460@paasikivi.fi.intel.com> References: <20210208113208.35449879@canb.auug.org.au> <20210208065315.1914616-1-mchehab+huawei@kernel.org> <20210208072701.GI32460@paasikivi.fi.intel.com> <20210208083616.3iulzo56mhn4ymmq@uno.localdomain> <20210208084147.GN32460@paasikivi.fi.intel.com> <20210208100822.76ca0c2e@coco.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210208100822.76ca0c2e@coco.lan> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, Feb 08, 2021 at 10:08:22AM +0100, Mauro Carvalho Chehab wrote: > Em Mon, 8 Feb 2021 10:41:47 +0200 > Sakari Ailus escreveu: > > > Hi Jacopo, > > > > On Mon, Feb 08, 2021 at 09:36:16AM +0100, Jacopo Mondi wrote: > > > Hello everyone, > > > > > > On Mon, Feb 08, 2021 at 09:27:01AM +0200, Sakari Ailus wrote: > > > > Hi Mauro, > > > > > > > > Thanks for the patch. > > > > > > Sorry, that's cleary an oversight from my side. > > > Thanks for tackling it. > > > > > > > > > > > On Mon, Feb 08, 2021 at 07:53:15AM +0100, Mauro Carvalho Chehab wrote: > > > > > As described on its c file, the Maxim MAX9271 GMSL serializer isn't a > > > > > self-contained driver, as MAX9271 is usually embedded in camera modules > > > > > with at least one image sensor and optional additional components, > > > > > such as uController units or ISPs/DSPs. > > > > > > > > > > After chanseset a59f853b3b4b ("media: i2c: Add driver for RDACM21 camera module"), > > > > > there are now two drivers currently needing it: rdacm20 and rdacm21. > > > > > > > > > > Building with allmodconfig is now causing those warnings: > > > > > > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_serial_link' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_configure_i2c' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_high_threshold' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_configure_gmsl_link' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_gpios' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_clear_gpios' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_enable_gpios' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_disable_gpios' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_verify_id' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_address' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_deserializer_address' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: 'max9271_set_translation' exported twice. Previous export was in drivers/media/i2c/rdacm20-camera_module.ko > > > > > > > > > > Address the issue by adding a Kconfig item for it, that it is > > > > > seleced if either one of the modules that need max9271 is used. > > > > > > > > > > Reported-by: Stephen Rothwell > > > > > Fixes: a59f853b3b4b ("media: i2c: Add driver for RDACM21 camera module") > > > > > Signed-off-by: Mauro Carvalho Chehab > > > > > --- > > > > > drivers/media/i2c/Kconfig | 10 ++++++++++ > > > > > drivers/media/i2c/Makefile | 8 ++++---- > > > > > 2 files changed, 14 insertions(+), 4 deletions(-) > > > > > > > > > > diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig > > > > > index 2d3dc0d82f9e..a6802195d583 100644 > > > > > --- a/drivers/media/i2c/Kconfig > > > > > +++ b/drivers/media/i2c/Kconfig > > > > > @@ -712,6 +712,16 @@ config VIDEO_ST_MIPID02 > > > > > module will be called st-mipid02. > > > > > endmenu > > > > > > > > > > +# > > > > > +# Camera ancillary chips > > > > > +# > > > > > + > > > > > +# MAX9271 is usually embedded in camera modules > > > > > +config VIDEO_MAX9271_SERIALIZER > > > > > + tristate > > > > > + default y > > > > > + depends on VIDEO_RDACM20 || VIDEO_RDACM21 > > > > > + > > > > > > > > I'd instead make the RDACM drivers depend on this one instead. The RDACM20 > > > > driver directly depends on the symbols in the MAX9271 driver. > > While such solution is technically OK, it will make harder for the ones > wanting to use the RDACM drivers, because those two drivers will be > ridden at the config menu, until MAX9271 got selected. > > With the above solution, this driver will be auto-selected if either > RDACM20 or RDACM21 is needed. > > Btw, this is exactly the same strategy we use for tuner I2C modules: > the user doesn't need to know that his board uses tuner "foo" or "bar". > All it needs is to know that it will require, for instance, the em28xx > driver. > > > > > > > > > > > OTOH I it makes sense to have MAX9271 depend on the camera modules, as > > > selecting the serializer alone is not that useful. > > > > > > Could the two camera modules symbols instead select the MAX9271 one ? > > > > MAX9271 could be used elsewhere than in RDACM* devices. > > Sure, but then it is just a matter of adding the other driver there: > > depends on VIDEO_RDACM20 || VIDEO_RDACM21 || VIDEO_FOO > > To be frank, I doubt that we'll end having dozens of boards with this. > If we end having lots of drivers, we can work on a different > solution. Also note that there will be combinations of something compiled as a module and another driver linked directly to the kernel. So each of the RDACM drivers would likely also need: depends on VIDEO_MAX9271_SERIALIZER || !VIDEO_MAX9271_SERIALIZER > > > > > Also, as select does not handle dependencies, all drivers that need MAX9271 > > would have to include the dependencies of MAX9271. > > Yes. "Depends on" handles any dependencies that are required for building > MAX9271. In this specific case, the dependencies are the same, so select > could equally work. Sure. -- Kind regards, Sakari Ailus