From: Frank Li <Frank.li@nxp.com>
To: Michael Riesch <michael.riesch@collabora.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Guoniu Zhou <guoniu.zhou@oss.nxp.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
imx@lists.linux.dev,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 5/6] media: dt-bindings: add NXP i.MX93 compatible string
Date: Mon, 16 Feb 2026 10:52:07 -0500 [thread overview]
Message-ID: <aZM9JyKn_5q8fTa_@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <e06feb9d-47cd-40e6-8c43-b24ff8a3e800@collabora.com>
On Mon, Feb 16, 2026 at 04:22:13PM +0100, Michael Riesch wrote:
> Hi Frank,
>
> On 2/16/26 09:31, Michael Riesch wrote:
> > Hi Frank,
> >
> > On 2/13/26 21:25, Frank Li wrote:
> >> The i.MX93 uses the DW CSI-2 RX controller, which is similar to the
> >> Rockchip RK3568 implementation.
> >>
> >> The i.MX93 variant provides one IRQ, two clocks, and no resets. Add the
> >> "fsl,imx93-mipi-csi2" compatible string and keep the same constraints for
> >> rk3568.
> >
> > RK3568.
> >
> >>
> >> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> >> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> >
> > With that cosmetic fix,
> >
> > Acked-by: Michael Riesch <michael.riesch@collabora.com>
>
> I just recalled a conversation with Heiko we had off-list a while ago,
> and back then we kind of decided against a snps binding document and
> compatible, since the integration in the respective SoC (family) varies.
> Thus, we went for a Rockchip document (which shall be extended with the
> RK3588 variant of this block, for example) and thought that any other
> variant (e.g., the one of the imx93) could be documented in a separate
> document fsl,somethingsomething.
>
> Seeing that interrupts, clocks, and resets are different, I would
> recommend that you add a new fsl,... document.
>
> What do you think?
It is depend on how much difference. Conside Krzysztof Kozlowski already
acked. we can split it when more soc will be added, if-else branch become
extremly complex and abstract more common property likes dwc usb at that
time.
Frank
>
> Best regards,
> Michael
>
>
> >
> > Best regards,
> > Michael
> >
> >
> >> ---
> >> .../bindings/media/rockchip,rk3568-mipi-csi2.yaml | 47 +++++++++++++++++++++-
> >> 1 file changed, 45 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml
> >> index 2c2bd87582eb8bfdd13720edd62a5f00dda958ba..4ac4a3b6f406408b9524c795e6cdeb117d3353da 100644
> >> --- a/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml
> >> +++ b/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml
> >> @@ -17,6 +17,7 @@ description:
> >> properties:
> >> compatible:
> >> enum:
> >> + - fsl,imx93-mipi-csi2
> >> - rockchip,rk3568-mipi-csi2
> >>
> >> reg:
> >> @@ -26,14 +27,23 @@ properties:
> >> items:
> >> - description: Interrupt that signals changes in CSI2HOST_ERR1.
> >> - description: Interrupt that signals changes in CSI2HOST_ERR2.
> >> + minItems: 1
> >>
> >> interrupt-names:
> >> items:
> >> - const: err1
> >> - const: err2
> >> + minItems: 1
> >>
> >> clocks:
> >> - maxItems: 1
> >> + minItems: 1
> >> + maxItems: 2
> >> +
> >> + clock-names:
> >> + items:
> >> + - const: per
> >> + - const: pixel
> >> + minItems: 1
> >>
> >> phys:
> >> maxItems: 1
> >> @@ -88,10 +98,43 @@ required:
> >> - phys
> >> - ports
> >> - power-domains
> >> - - resets
> >>
> >> additionalProperties: false
> >>
> >> +allOf:
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + const: rockchip,rk3568-mipi-csi2
> >> + then:
> >> + properties:
> >> + interrupts:
> >> + minItems: 2
> >> + interrupt-names:
> >> + minItems: 2
> >> + clocks:
> >> + maxItems: 1
> >> + clock-names:
> >> + maxItems: 1
> >> + required:
> >> + - resets
> >> +
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + const: fsl,imx93-mipi-csi2
> >> + then:
> >> + properties:
> >> + interrupts:
> >> + maxItems: 1
> >> + interrupt-names: false
> >> + clocks:
> >> + minItems: 2
> >> + clock-names:
> >> + minItems: 2
> >> +
> >> examples:
> >> - |
> >> #include <dt-bindings/clock/rk3568-cru.h>
> >>
> >
>
next prev parent reply other threads:[~2026-02-16 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 20:25 [PATCH v2 0/6] media: synopsys: Add imx93 support Frank Li
2026-02-13 20:25 ` [PATCH v2 1/6] media: synopsys: csi2rx: use devm_reset_control_get_optional_exclusive() Frank Li
2026-02-13 20:25 ` [PATCH v2 2/6] media: synopsys: csi2rx: only check errors from devm_clk_bulk_get_all() Frank Li
2026-02-13 20:25 ` [PATCH v2 3/6] media: synopsys: csi2rx: implement .get_frame_desc() callback Frank Li
2026-02-16 9:03 ` Michael Riesch
2026-02-13 20:25 ` [PATCH v2 4/6] media: synopsys: csi2rx: Use enum and u32 array for register offsets Frank Li
2026-02-16 8:11 ` Michael Riesch
2026-02-13 20:25 ` [PATCH v2 5/6] media: dt-bindings: add NXP i.MX93 compatible string Frank Li
2026-02-16 8:31 ` Michael Riesch
2026-02-16 15:22 ` Michael Riesch
2026-02-16 15:52 ` Frank Li [this message]
2026-02-13 20:25 ` [PATCH v2 6/6] media: synopsys: csi2rx: add i.MX93 support Frank Li
2026-02-16 8:29 ` Michael Riesch
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=aZM9JyKn_5q8fTa_@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoniu.zhou@oss.nxp.com \
--cc=heiko@sntech.de \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®