From: Frank Li <Frank.li@nxp.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
"open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)"
<linux-media@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<imx@lists.linux.dev>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] dt-bindings: media: convert imx.txt to yaml format
Date: Wed, 16 Apr 2025 11:31:41 -0400 [thread overview]
Message-ID: <Z//NXcEB6UkEDRxe@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <14f2bfcd4604c5cf8b92a7d0dfc685e1f56b768b.camel@pengutronix.de>
On Wed, Apr 16, 2025 at 05:26:19PM +0200, Philipp Zabel wrote:
> On Mi, 2025-04-16 at 11:17 -0400, Frank Li wrote:
> > On Wed, Apr 16, 2025 at 07:42:26AM -0500, Rob Herring wrote:
> > > On Mon, Apr 14, 2025 at 05:07:18PM -0400, Frank Li wrote:
> > > > Convert binding doc imx.txt to yaml format. Create two yaml files:
> > > > fsl,imx6-mipi-csi2.yaml and fsl,imx-capture-subsystem.yaml.
> > > >
> > > > Additional changes:
> > > > - add example for fsl,imx6-mipi-csi2
> > > >
> > > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > > ---
> > > > .../media/fsl,imx-capture-subsystem.yaml | 38 ++++++
> > > > .../bindings/media/fsl,imx6-mipi-csi2.yaml | 126 ++++++++++++++++++
> > > > .../devicetree/bindings/media/imx.txt | 53 --------
> > > > 3 files changed, 164 insertions(+), 53 deletions(-)
> > > > create mode 100644 Documentation/devicetree/bindings/media/fsl,imx-capture-subsystem.yaml
> > > > create mode 100644 Documentation/devicetree/bindings/media/fsl,imx6-mipi-csi2.yaml
> > > > delete mode 100644 Documentation/devicetree/bindings/media/imx.txt
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/media/fsl,imx-capture-subsystem.yaml b/Documentation/devicetree/bindings/media/fsl,imx-capture-subsystem.yaml
> > > > new file mode 100644
> > > > index 0000000000000..77be3c1f37c5b
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/media/fsl,imx-capture-subsystem.yaml
> > > > @@ -0,0 +1,38 @@
> > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > > +%YAML 1.2
> > > > +---
> > > > +$id: http://devicetree.org/schemas/media/fsl,imx-capture-subsystem.yaml#
> > > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > > +
> > > > +title: Freescale i.MX Media Video Device
> > > > +
> > ...
> > > > + reg = <0x021dc000 0x4000>;
> > > > + #address-cells = <1>;
> > > > + #size-cells = <0>;
> > > > + clocks = <&clks IMX6QDL_CLK_HSI_TX>,
> > > > + <&clks IMX6QDL_CLK_VIDEO_27M>,
> > > > + <&clks IMX6QDL_CLK_EIM_PODF>;
> > > > + clock-names = "dphy", "ref", "pix";
> > > > +
> > > > + port@0 {
> > > > + reg = <0>;
> > > > +
> > > > + endpoint {
> > > > + remote-endpoint = <&ov5640_to_mipi_csi2>;
> > > > + clock-lanes = <0>;
> > > > + data-lanes = <1 2>;
> > > > + };
> > > > + };
> > >
> > > I would think at least 1 output port is required?
> >
> > I checked dts file, only input port. I think old csi2 only need get data
> > from camera. csi's dma should save to memory.
>
> There are no ports in imx6qdl.dtsi, but there's a &mipi_csi with four
> output ports in imx6q.dtsi and imx6dl.dtsi each, because whether data
> flows through a mux or directly into the IPU CSI ports differs between
> the two platforms.
Thank you very much!
Frank
>
> regards
> Philipp
>
prev parent reply other threads:[~2025-04-16 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 21:07 [PATCH 1/1] dt-bindings: media: convert imx.txt to yaml format Frank Li
2025-04-15 21:27 ` kernel test robot
2025-04-16 12:42 ` Rob Herring
2025-04-16 15:17 ` Frank Li
2025-04-16 15:26 ` Philipp Zabel
2025-04-16 15:31 ` Frank Li [this message]
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=Z//NXcEB6UkEDRxe@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox