From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B0F9830E84B for ; Thu, 19 Jun 2025 21:02:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750366979; cv=none; b=TD2vqAs8vB6YESw2TG+p3dMUUaX1NhV58aXyWkOudjMYBKB9/gQI3OUy2Y8pzZtxO9tBJI5YoygiccQmvAHIJBxSQ97yLh+PYm8lIL/6zJdzlWnh4vhicj8sBJrpmcebvHBisKL9sFp95836PItMRv78NkRCWkfm1Q8K7yJKMrI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750366979; c=relaxed/simple; bh=cMcgUkKcU4XsVXe3puMc1IqvW3rgKBUEbIiiJLipLQI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Wwz1v7ITBtacYHTNB9HGJGGhoDm6NSLc4iNn9cx6wxqHHL/nRBUg3T68bTR+v+/vxeEdGSScFnqhhOZVCQ/n9hKECOxdKt4YDfwk8+p6oNLWXMgGtsuurzVBl+Xc4f6pqJDp5g1/eIOaqhh1/a9o93OtZKWpgR/2OahuezprUNw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=nHzBpkMp; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="nHzBpkMp" Received: from pendragon.ideasonboard.com (81-175-209-231.bb.dnainternet.fi [81.175.209.231]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id EE9192EC; Thu, 19 Jun 2025 23:02:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1750366962; bh=cMcgUkKcU4XsVXe3puMc1IqvW3rgKBUEbIiiJLipLQI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nHzBpkMpW+52bQS9MZNB33ymQm5kq4+JmXeNbxNXzA99jYVDEyEzQxuNgb231G0vw p9w1Q2rETQcwko4GJ8gIE6Fky1RgWDPPfJ3wYVTN6SdwEkcjARLPrpURRXbzR2YeF8 dGpVql/nGJTd4hl4rsPmDL4igkyFSI1zJgZjmn38= Date: Fri, 20 Jun 2025 00:02:37 +0300 From: Laurent Pinchart To: Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Adam Ford , Frank Li , Isaac Scott , Rui Miguel Silva , Martin Kepplinger , Mauro Carvalho Chehab , Shawn Guo , Sascha Hauer , Fabio Estevam , linux-media@vger.kernel.org, devicetree@vger.kernel.org, imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org, Purism Kernel Team , Pengutronix Kernel Team Subject: Re: [PATCH 6/8] dt-bindings: media: nxp,imx-mipi-csi2: Add fsl,num-channels property Message-ID: <20250619210237.GA21935@pendragon.ideasonboard.com> References: <20250608235840.23871-1-laurent.pinchart@ideasonboard.com> <20250608235840.23871-7-laurent.pinchart@ideasonboard.com> <20250609182033.GA11428@pendragon.ideasonboard.com> <20250610081829.GC11428@pendragon.ideasonboard.com> Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20250610081829.GC11428@pendragon.ideasonboard.com> On Tue, Jun 10, 2025 at 11:18:29AM +0300, Laurent Pinchart wrote: > On Mon, Jun 09, 2025 at 03:08:39PM -0400, Frank Li wrote: > > On Mon, Jun 09, 2025 at 09:20:33PM +0300, Laurent Pinchart wrote: > > > On Mon, Jun 09, 2025 at 12:53:48PM -0500, Adam Ford wrote: > > > > On Mon, Jun 9, 2025 at 10:32 AM Frank Li wrote: > > > > > On Mon, Jun 09, 2025 at 02:58:38AM +0300, Laurent Pinchart wrote: > > > > > > The CSI-2 receiver can be instantiated with up to four output channels. > > > > > > This is an integration-specific property, specify the number of > > > > > > instantiated channels through a new fsl,num-channels property. The > > > > > > property is optional, and defaults to 1 as only one channel is currently > > > > > > supported by drivers. > > > > > > > > > > > > The only known SoC to have more than one channel is the i.MX8MP. As the > > > > > > binding examples do not cover that SoC, don't update them. > > > > > > > > > > > > Signed-off-by: Laurent Pinchart > > > > > > --- > > > > > > .../devicetree/bindings/media/nxp,imx-mipi-csi2.yaml | 7 +++++++ > > > > > > 1 file changed, 7 insertions(+) > > > > > > > > > > > > diff --git a/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml > > > > > > index db4889bf881e..41ad5b84eaeb 100644 > > > > > > --- a/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml > > > > > > +++ b/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml > > > > > > @@ -68,6 +68,13 @@ properties: > > > > > > default: 166000000 > > > > > > deprecated: true > > > > > > > > > > > > + fsl,num-channels: > > > > > > + $ref: /schemas/types.yaml#/definitions/uint32 > > > > > > + description: Number of output channels > > > > > > + minimum: 1 > > > > > > + maximum: 4 > > > > > > + default: 1 > > > > > > + > > > > > > > > > > Look like it is fixed value for each compabiable string, So it is not > > > > > suitable for adding new property. It should be in driver data of each > > > > > compatible strings. > > > > > > > > > > I met similar case before. DT team generally don't agree on add such > > > > > property, unless there are two instances in the same chip, which have > > > > > difference channel number. > > > > > > > > If the DT changes are rejected, can the number of channels be added to > > > > the data structure inside mipi_csis_of_match? We have compatibles for > > > > 8mm and imx7. If we add an imx8mp compatible we could add a reference > > > > to the number of channels. > > > > > > I thought about it, and decided to add a new property because the number > > > of channels is really a synthesis time configuration parameter, and > > > could differ between different CSIS instances in the same SoC. > > > > Need add such information at binding doc's commit message, > > I'll update the commit message. The commit message in v2 will state dt-bindings: media: nxp,imx-mipi-csi2: Add fsl,num-channels property The CSI-2 receiver can be instantiated with up to four output channels. This is an integration-specific property, specify the number of instantiated channels through a new fsl,num-channels property. The property is optional, and defaults to 1 as only one channel is currently supported by drivers. Using the compatible string to infer the number of channels has been considered, but multiple instances of the same CSIS in the same SoC could conceptually be synthesized with a different number of channels. An explicit property is therefore more appropriate. The only known SoC to have more than one channel is the i.MX8MP. As the binding examples do not cover that SoC, don't update them. Rob, Krzysztof, Conor, are you fine with adding this property ? > > ideally provide an example for it. > > That I can't provide because the few SoCs I'm working with do not > integrate multiple CSIS instances with different parameters. > > > > > > > ports: > > > > > > $ref: /schemas/graph.yaml#/properties/ports > > > > > > -- Regards, Laurent Pinchart