From: Liu Ying <victor.liu@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: marex@denx.de, stefan@agner.ch, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
krzysztof.kozlowski@linaro.org, LW@karo-electronics.de
Subject: Re: [PATCH v3 1/6] dt-bindings: lcdif: Add i.MX93 LCDIF support
Date: Wed, 15 Feb 2023 15:49:56 +0800 [thread overview]
Message-ID: <41bc30ac7af4b0ce3ff608b604fb6ea762428680.camel@nxp.com> (raw)
In-Reply-To: <2551514.Lt9SDvczpP@steina-w>
On Wed, 2023-02-15 at 08:26 +0100, Alexander Stein wrote:
> Hi Liu,
Hi Alexander,
>
> thanks for the update.
Thanks for the review.
>
> Am Montag, 13. Februar 2023, 09:56:07 CET schrieb Liu Ying:
> > There is one LCDIF embedded in i.MX93 SoC to connect with
> > MIPI DSI controller through LCDIF cross line pattern(controlled
> > by mediamix blk-ctrl) or connect with LVDS display bridge(LDB)
> > directly or connect with a parallel display through parallel
> > display format(also controlled by mediamix blk-ctrl). i.MX93
> > LCDIF IP is essentially the same to i.MX8MP LCDIF IP. Add device
> > tree binding for i.MX93 LCDIF.
> >
> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Reviewed-by: Marek Vasut <marex@denx.de>
> > Signed-off-by: Liu Ying <victor.liu@nxp.com>
> > ---
> > v2->v3:
> > * No change.
> >
> > v1->v2:
> > * Add Krzysztof's A-b and Marek's R-b tags on patch 1/6.
> >
> > Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 7
> > ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml index
> > 75b4efd70ba8..fc11ab5fc465 100644
> > --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > @@ -21,6 +21,7 @@ properties:
> > - fsl,imx28-lcdif
> > - fsl,imx6sx-lcdif
> > - fsl,imx8mp-lcdif
> > + - fsl,imx93-lcdif
> > - items:
> > - enum:
> > - fsl,imx6sl-lcdif
> > @@ -88,7 +89,9 @@ allOf:
> > properties:
> > compatible:
> > contains:
> > - const: fsl,imx8mp-lcdif
> > + enum:
> > + - fsl,imx8mp-lcdif
> > + - fsl,imx93-lcdif
> > then:
> > properties:
> > clocks:
> > @@ -107,6 +110,7 @@ allOf:
> > enum:
> > - fsl,imx6sx-lcdif
> > - fsl,imx8mp-lcdif
> > + - fsl,imx93-lcdif
> > then:
> > properties:
> > clocks:
> > @@ -123,6 +127,7 @@ allOf:
> > - fsl,imx8mm-lcdif
> > - fsl,imx8mn-lcdif
> > - fsl,imx8mp-lcdif
> > + - fsl,imx93-lcdif
> > then:
> > required:
> > - power-domains
>
> I would have expected that fsl,imx93-lcdif supports up to 3 endpoints
> (MIPI
> DSI, LVDS, and parallel) in a 'ports' subnode. But this binding only
> supports
> a single 'port' sub-node. Also an example for this case might be very
> helpful.
The port node allows multiple endpoints(See graph.yaml[1]). It's
enough to use the existing port node instead of using ports node.
For i.MX93 LCDIF, the port node will be something like this:
--------------------8<--------------------------
port {
#address-cells = <1>;
#size-cells = <0>;
lcdif_to_pdfc: endpoint@0 {
reg = <0>;
};
lcdif_to_ldb: endpoint@1 {
reg = <1>;
};
lcdif_to_cross_line_pattern: endpoint@2 {
reg = <2>;
};
};
--------------------8<--------------------------
Looks like it's not necessary to add a specifc example for i.MX93
LCDIF.
[1]
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/graph.yaml#L48
Regards,
Liu Ying
next prev parent reply other threads:[~2023-02-15 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 8:56 [PATCH v3 0/6] drm: lcdif: Add i.MX93 LCDIF support Liu Ying
2023-02-13 8:56 ` [PATCH v3 1/6] dt-bindings: " Liu Ying
2023-02-15 7:26 ` Alexander Stein
2023-02-15 7:49 ` Liu Ying [this message]
2023-02-15 8:44 ` Alexander Stein
2023-02-13 8:56 ` [PATCH v3 2/6] drm: lcdif: Drop unnecessary NULL pointer check on lcdif->bridge Liu Ying
2023-02-14 13:42 ` Alexander Stein
2023-02-13 8:56 ` [PATCH v3 3/6] drm: lcdif: Determine bus format and flags in ->atomic_check() Liu Ying
2023-02-14 14:12 ` Alexander Stein
2023-02-14 14:16 ` Ville Syrjälä
2023-02-15 3:44 ` Liu Ying
2023-02-15 8:27 ` Alexander Stein
2023-02-13 8:56 ` [PATCH v3 4/6] drm: lcdif: Check consistent bus format and flags across first bridges Liu Ying
2023-02-15 7:55 ` Alexander Stein
2023-02-15 8:40 ` Liu Ying
2023-02-13 8:56 ` [PATCH v3 5/6] drm: lcdif: Add multiple encoders and first bridges support Liu Ying
2023-02-15 7:54 ` Alexander Stein
2023-02-15 8:52 ` Liu Ying
2023-02-13 8:56 ` [PATCH v3 6/6] drm: lcdif: Add i.MX93 LCDIF compatible string Liu Ying
2023-02-15 7:55 ` Alexander Stein
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=41bc30ac7af4b0ce3ff608b604fb6ea762428680.camel@nxp.com \
--to=victor.liu@nxp.com \
--cc=LW@karo-electronics.de \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).