From: "Inbaraj E" <inbaraj.e@samsung.com>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <rmfrfs@gmail.com>, <laurent.pinchart@ideasonboard.com>,
<martink@posteo.de>, <kernel@puri.sm>, <mchehab@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<shawnguo@kernel.org>, <s.hauer@pengutronix.de>,
<kernel@pengutronix.de>, <festevam@gmail.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<imx@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>, <pankaj.dubey@samsung.com>,
<ravi.patel@samsung.com>, <shradha.t@samsung.com>
Subject: RE: [PATCH v3 1/7] dt-bindings: media: nxp: Add support for FSD SoC
Date: Wed, 17 Sep 2025 17:39:35 +0530 [thread overview]
Message-ID: <024f01dc27cb$f167d370$d4377a50$@samsung.com> (raw)
In-Reply-To: <20250829174638.GA1054721-robh@kernel.org>
Hi Rob,
Thanks for the review
> > + description:
> > + Syscon used to hold and release the reset of MIPI D-PHY
>
> Reset? Sounds like you should be using the reset binding.
The Tesla FSD Soc does not have a dedicated reset controller. Instead, we
are using the
system controller which is MMIO Space handled by syscon driver, to assert or
de-assert the D-PHY
reset. So, I prefer to use syscon.
>
> > +
> > phy-supply:
> > description: The MIPI D-PHY digital power supply
> >
> > @@ -93,7 +91,8 @@ properties:
> > properties:
> > data-lanes:
> > description:
> > - Note that 'fsl,imx7-mipi-csi2' only supports up to 2
data lines.
> > + Note that 'fsl,imx7-mipi-csi2' only supports up to 2
data
> > + lines.
>
> Reformatting should be a separate patch.
Sure, I'll add new patch in next patchset.
>
> > minItems: 1
> > items:
> > - const: 1
> > @@ -115,7 +114,6 @@ required:
> > - interrupts
> > - clocks
> > - clock-names
> > - - power-domains
> > - ports
> >
> > additionalProperties: false
> > @@ -124,20 +122,73 @@ allOf:
> > - if:
> > properties:
> > compatible:
> > - contains:
> > - const: fsl,imx7-mipi-csi2
> > + const: fsl,imx7-mipi-csi2
>
> 'contains' was correct. It is more future proof when there is another SoC
that
> is backwards compatible with imx7.
Sure, I'll add new patch in next patchset.
>
> > then:
> > + properties:
> > + clocks:
> > + items:
> > + - description: The peripheral clock (a.k.a. APB clock)
> > + - description: The external clock (optionally used as the
pixel
> > + clock)
> > + - description: The MIPI D-PHY clock
> > + clock-names:
> > + items:
> > + - const: pclk
> > + - const: wrap
> > + - const: phy
> > + tesla,syscon-csis: false
> > + fsl,num-channels: false
>
> blank line
Will remove in nextpatchset.
>
> > required:
> > + - power-domains
> > - phy-supply
> > - resets
> > - else:
> > +
> > + - if:
> > + properties:
> > + compatible:
> > + const: fsl,imx8mm-mipi-csi2
> > + then:
> > properties:
> > clocks:
> > - minItems: 4
> > + items:
> > + - description: The peripheral clock (a.k.a. APB clock)
> > + - description: The external clock (optionally used as the
pixel
> > + clock)
> > + - description: The MIPI D-PHY clock
> > + - description: The AXI clock
> > clock-names:
> > - minItems: 4
> > + items:
> > + - const: pclk
> > + - const: wrap
> > + - const: phy
> > + - const: axi
> > + tesla,syscon-csis: false
> > + fsl,num-channels: false
> > phy-supply: false
> > resets: false
>
> blank line
>
> > + required:
> > + - power-domains
> > +
> > + - if:
> > + properties:
> > + compatible:
> > + const: tesla,fsd-mipi-csi2
> > + then:
> > + properties:
> > + clocks:
> > + items:
> > + - description: The peripheral clock (a.k.a. APB clock)
> > + - description: The DMA clock
>
> Wouldn't this be the same as the "AXI clock"?
According to v4.3 manual it is DMA clock.
>
> > + clocks-names:
> > + items:
> > + - const: pclk
> > + - const: aclk
> > + phy-supply: false
> > + resets: false
> > + power-domains: false
>
> blank line
Sure will remove in next patchset.
>
> > + required:
> > + - tesla,syscon-csis
> > + - fsl,num-channels
> >
> > examples:
> > - |
> > --
> > 2.49.0
> >
Regards,
Inbaraj E
next prev parent reply other threads:[~2025-09-17 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250828085921epcas5p44f9371fb004fe0aa8bf68d1230e01861@epcas5p4.samsung.com>
2025-08-28 8:59 ` [PATCH v3 0/7] Add FSD CSIS support Inbaraj E
2025-08-28 8:59 ` [PATCH v3 1/7] dt-bindings: media: nxp: Add support for FSD SoC Inbaraj E
2025-08-29 17:46 ` Rob Herring
2025-09-17 12:09 ` Inbaraj E [this message]
2025-09-18 0:01 ` Krzysztof Kozlowski
2025-08-28 8:59 ` [PATCH v3 2/7] dt-bindings: media: fsd: Add CSIS video capture interface Inbaraj E
2025-09-01 4:55 ` Krzysztof Kozlowski
2025-09-17 12:13 ` Inbaraj E
2025-09-18 0:01 ` Krzysztof Kozlowski
2025-08-28 8:59 ` [PATCH v3 3/7] media: imx-mipi-csis: Move clk to mipi_csis_info structure Inbaraj E
2025-08-28 8:59 ` [PATCH v3 4/7] media: imx-mipi-csis: Move irq flag and handler " Inbaraj E
2025-08-28 8:59 ` [PATCH v3 5/7] media: imx-mipi-csis: Add support for dynamic VC selection Inbaraj E
2025-08-28 8:59 ` [PATCH v3 6/7] media: imx-mipi-csis: Add support for Telsa FSD CSIS Inbaraj E
2025-08-28 8:59 ` [PATCH v3 7/7] media: fsd-csis: Add FSD CSIS video capture interface support Inbaraj E
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='024f01dc27cb$f167d370$d4377a50$@samsung.com' \
--to=inbaraj.e@samsung.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=kernel@puri.sm \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=rmfrfs@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shradha.t@samsung.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;
as well as URLs for NNTP newsgroup(s).