Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5206EC6FD1D for ; Mon, 20 Mar 2023 13:32:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230169AbjCTNcs convert rfc822-to-8bit (ORCPT ); Mon, 20 Mar 2023 09:32:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34138 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229878AbjCTNcp (ORCPT ); Mon, 20 Mar 2023 09:32:45 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 614DF358E for ; Mon, 20 Mar 2023 06:32:43 -0700 (PDT) Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1peFci-0007ke-Bw; Mon, 20 Mar 2023 14:32:28 +0100 Received: from [2a0a:edc0:0:900:1d::4e] (helo=lupine) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1peFcg-005THe-LI; Mon, 20 Mar 2023 14:32:26 +0100 Received: from pza by lupine with local (Exim 4.94.2) (envelope-from ) id 1peFcf-0009sl-Q9; Mon, 20 Mar 2023 14:32:25 +0100 Message-ID: <727949a9c3d9e639b046bcd86635796452b10300.camel@pengutronix.de> Subject: Re: [PATCH v2] media: i2c: ov5640: Implement get_mbus_config From: Philipp Zabel To: Sakari Ailus , Laurent Pinchart Cc: Jacopo Mondi , Francesco Dolcini , Sakari Ailus , Marcel Ziswiler , linux-media@vger.kernel.org, kernel@pengutronix.de, Francesco Dolcini , Aishwarya Kothari , Marcel Ziswiler , Mauro Carvalho Chehab , Steve Longerbeam , linux-kernel@vger.kernel.org, Marco Felsch Date: Mon, 20 Mar 2023 14:32:25 +0100 In-Reply-To: References: <20230306063649.7387-1-marcel@ziswiler.com> <20230320084844.tdjiv6kaxcosiwm2@uno.localdomain> <20230320092602.GE20234@pendragon.ideasonboard.com> <20230320095514.GF20234@pendragon.ideasonboard.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT User-Agent: Evolution 3.38.3-1+deb11u1 MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mo, 2023-03-20 at 12:15 +0200, Sakari Ailus wrote: > Hi Laurent, > > On Mon, Mar 20, 2023 at 11:55:14AM +0200, Laurent Pinchart wrote: > > On Mon, Mar 20, 2023 at 11:37:33AM +0200, Sakari Ailus wrote: > > > Hi Laurent, > > > > > > On Mon, Mar 20, 2023 at 11:26:02AM +0200, Laurent Pinchart wrote: > > > > In a (simplified) nutshell, > > > > > > > > ---------+ +----------+ +---------+ +-----+ +-----+ > > > > > Camera | --> | CSI-2 RX | --> | CSI2IPU | --> | Mux | --> | IPU | > > > > > Sensor | | | | Gasket | | | | | > > > > ---------+ +----------+ +---------+ +-----+ +-----+ > > > > > > Thank you, this is helpful. > > > > > > I suppose the mux here at least won't actively do anything to the data. So > > > presumably its endpoint won't contain the active configuration, but its > > > superset. > > > > > > > > > > > All those blocks, except for the gasket, have a node in DT. > > > > > > > > The IPU driver needs to know the number of CSI-2 data lanes, which is > > > > encoded in the data-lanes DT property present in both the sensor output > > > > endpoint and the CSI-2 RX input endpoint, but not the other endpoints in > > > > the pipeline. > > > > > > This doesn't yet explain why the sensor would need to implement > > > get_mbus_config if its bus configuration remains constant. > > > > If I recall correctly, the IPU driver calls .g_mbus_config() on the > > camera sensor to get the number of lanes, as it can't get it from its > > own endpoint. That's a hack, and as Jacopo proposed, calling > > .g_mbus_config() on the CSI-2 RX would be better, as the CSI-2 RX driver > > can then get the value from its own endpoint, without requiring all > > sensor drivers to implement .g_mbus_config(). > > The g_mbus_config op could be implemented by the CSI2IPU and mux, by simply > requesting the information from the upstream sub-device. No hacks would be > needed. I think implementing get_mbus_config on the mux might be enough. The IPU driver already recognizes the CSI-2 RX by its grp_id and could infer that it has to use MIPI CSI-2 mode from that. The video-mux would have to forward get_mbus_config to its active upstream port and if the upstream sensor does not implement it read bus width from the active upstream endpoint. regards Philipp