All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Inbaraj E" <inbaraj.e@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
	<mturquette@baylibre.com>, <sboyd@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<s.nawrocki@samsung.com>, <s.hauer@pengutronix.de>,
	<shawnguo@kernel.org>, <cw00.choi@samsung.com>,
	<rmfrfs@gmail.com>, <laurent.pinchart@ideasonboard.com>,
	<martink@posteo.de>, <mchehab@kernel.org>, <linux-fsd@tesla.com>,
	<will@kernel.org>, <catalin.marinas@arm.com>,
	<pankaj.dubey@samsung.com>, <shradha.t@samsung.com>,
	<ravi.patel@samsung.com>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <alim.akhtar@samsung.com>,
	<linux-samsung-soc@vger.kernel.org>, <kernel@puri.sm>,
	<kernel@pengutronix.de>, <festevam@gmail.com>,
	<linux-media@vger.kernel.org>, <imx@lists.linux.dev>,
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v2 03/12] dt-bindings: media: nxp: Add support for FSD SoC
Date: Fri, 22 Aug 2025 19:09:36 +0530	[thread overview]
Message-ID: <00d001dc136a$36ad7230$a4085690$@samsung.com> (raw)
In-Reply-To: <ac9769af-9ab6-4b48-9890-ec3bcda3b180@kernel.org>


Hi Krzysztof,

Thanks for the review.

> 
> Explain the hardware.

I'll explain in the next patchset.

> 
> >
> > Signed-off-by: Inbaraj E <inbaraj.e@samsung.com>
> > ---
> >  .../bindings/media/nxp,imx-mipi-csi2.yaml     | 88 ++++++++++++++-----
> >  1 file changed, 68 insertions(+), 20 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml
> > b/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml
> > index 03a23a26c4f3..802fb1bd150d 100644
> > --- a/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml
> > +++ b/Documentation/devicetree/bindings/media/nxp,imx-mipi-csi2.yaml
> > @@ -14,7 +14,7 @@ description: |-
> >    The NXP i.MX7 and i.MX8 families contain SoCs that include a MIPI CSI-2
> >    receiver IP core named CSIS. The IP core originates from Samsung, and
> may be
> >    compatible with some of the Exynos4 and S5P SoCs. i.MX7 SoCs use
> > CSIS version
> > -  3.3, and i.MX8 SoCs use CSIS version 3.6.3.
> > +  3.3, i.MX8 SoCs use CSIS version 3.6.3 and FSD SoC uses CSIS version 4.3.
> >
> >    While the CSI-2 receiver is separate from the MIPI D-PHY IP core, the PHY
> is
> >    completely wrapped by the CSIS and doesn't expose a control
> > interface of its @@ -26,6 +26,7 @@ properties:
> >        - enum:
> >            - fsl,imx7-mipi-csi2
> >            - fsl,imx8mm-mipi-csi2
> > +          - tesla,fsd-mipi-csi2
> 
> 
> Isn't this Samsung CSI IP? 

Yes, it is Samsung CSI IP.

Why are you adding it to NXP?

Samsung CSIS IP core present in Exynos(samsung/exynos4-is/mipi-csis.c) series is
completely different from the one in the Tesla FSD SoC. However, it is compatible
with the samsung CSIS IP used in the NXP SoC. For better code reusability, I am
integrating it with the NXP imx-mipi-csis driver.

 
> Nothing in commit, msg helps me to understand that.

I'll explain the same in commit description as well.

> 

> >        - items:
> >            - enum:
> >                - fsl,imx8mp-mipi-csi2
> > @@ -38,24 +39,21 @@ properties:
> >      maxItems: 1
> >
> >    clocks:
> > -    minItems: 3
> > -    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
> > +    minItems: 2
> > +    maxItems: 4
> >
> >    clock-names:
> > -    minItems: 3
> > -    items:
> > -      - const: pclk
> > -      - const: wrap
> > -      - const: phy
> > -      - const: axi
> > +    minItems: 2
> > +    maxItems: 4
> >
> >    power-domains:
> >      maxItems: 1
> >
> > +  samsung,syscon-csis:
> 
> samsung, so not nxp. Even more confusing.
> 

I used samsung,syscon-csis because the system controller on Tesla FSD
follows Samsung's sysreg design.

> 
> Best regards,
> Krzysztof

Regards,
Inbaraj E


  reply	other threads:[~2025-08-22 13:39 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250814140956epcas5p480aa24441933523484da5c241a201d3c@epcas5p4.samsung.com>
2025-08-14 14:09 ` [PATCH v2 00/12] Add FSD CSI support Inbaraj E
2025-08-14 14:09   ` [PATCH v2 01/12] dt-bindings: clock: Add CAM_CSI clock macro for FSD Inbaraj E
2025-08-18  8:47     ` (subset) " Krzysztof Kozlowski
2025-08-14 14:09   ` [PATCH v2 02/12] clk: samsung: fsd: Add clk id for PCLK and PLL in CAM_CSI block Inbaraj E
2025-08-18  8:47     ` (subset) " Krzysztof Kozlowski
2025-08-14 14:09   ` [PATCH v2 03/12] dt-bindings: media: nxp: Add support for FSD SoC Inbaraj E
2025-08-18  8:24     ` Krzysztof Kozlowski
2025-08-22 13:39       ` Inbaraj E [this message]
2025-08-22 13:50         ` Krzysztof Kozlowski
2025-08-22 14:00           ` Inbaraj E
2025-08-23 15:37             ` Krzysztof Kozlowski
2025-08-25 12:50               ` Inbaraj E
2025-08-14 14:09   ` [PATCH v2 04/12] arm64: dts: fsd: Add CSI nodes Inbaraj E
2025-08-18  8:26     ` Krzysztof Kozlowski
2025-08-22 13:57       ` Inbaraj E
2025-08-23 15:39         ` Krzysztof Kozlowski
2025-08-25 13:05           ` Inbaraj E
2025-08-26  8:36             ` Krzysztof Kozlowski
2025-08-26 10:08               ` Inbaraj E
2025-08-26 11:43               ` Laurent Pinchart
2025-08-14 14:09   ` [PATCH v2 05/12] media: imx-mipi-csis: Move clk to mipi_csis_info structure Inbaraj E
2025-08-18  9:21     ` Laurent Pinchart
2025-08-23 13:11       ` Inbaraj E
2025-08-14 14:09   ` [PATCH v2 06/12] media: imx-mipi-csis: Move irq flag and handler " Inbaraj E
2025-08-14 14:09   ` [PATCH v2 07/12] media: imx-mipi-csis: Add support to configure specific vc Inbaraj E
2025-08-18  9:33     ` Laurent Pinchart
2025-08-23 13:29       ` Inbaraj E
2025-08-14 14:09   ` [PATCH v2 08/12] media: imx-mipi-csis: Add support to dump all vc regs Inbaraj E
2025-08-18  9:30     ` Laurent Pinchart
2025-08-23 13:15       ` Inbaraj E
2025-08-14 14:09   ` [PATCH v2 09/12] media: imx-mipi-csis: Add support for FSD CSI Rx Inbaraj E
2025-08-14 14:09   ` [PATCH v2 10/12] dt-bindings: media: fsd: Document CSIS DMA controller Inbaraj E
2025-08-18  8:29     ` Krzysztof Kozlowski
2025-08-23  1:54       ` Inbaraj E
2025-08-18  8:45     ` Krzysztof Kozlowski
2025-08-23  2:39       ` Inbaraj E
2025-08-23 15:32         ` Krzysztof Kozlowski
2025-08-25 12:01           ` Inbaraj E
2025-08-25 12:25             ` Krzysztof Kozlowski
2025-08-24 21:15       ` Laurent Pinchart
2025-08-25  7:34         ` Krzysztof Kozlowski
2025-08-14 14:09   ` [PATCH v2 11/12] arm64: defconfig: Enable FSD CSIS DMA driver Inbaraj E
2025-08-18  8:32     ` Krzysztof Kozlowski
2025-08-23  2:05       ` Inbaraj E
2025-08-23 15:31         ` Krzysztof Kozlowski
2025-08-25 11:54           ` Inbaraj E
2025-08-14 14:09   ` [PATCH v2 12/12] media: fsd-csis: Add support for FSD CSIS DMA Inbaraj E
2025-08-18  8:49     ` Krzysztof Kozlowski
2025-08-23 11:49       ` Inbaraj E
2025-08-23 15:34         ` Krzysztof Kozlowski
2025-08-25 12:46           ` Inbaraj E
2025-08-23 11:59       ` Inbaraj E
2025-08-18  8:22   ` [PATCH v2 00/12] Add FSD CSI support Krzysztof Kozlowski
2025-08-22 13:16     ` 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='00d001dc136a$36ad7230$a4085690$@samsung.com' \
    --to=inbaraj.e@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --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=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-fsd@tesla.com \
    --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=mturquette@baylibre.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=ravi.patel@samsung.com \
    --cc=rmfrfs@gmail.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=shradha.t@samsung.com \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.