From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Marek Vasut <marex@denx.de> Cc: dri-devel@lists.freedesktop.org, Alexander Stein <alexander.stein@ew.tq-group.com>, Lucas Stach <l.stach@pengutronix.de>, Peng Fan <peng.fan@nxp.com>, Rob Herring <robh+dt@kernel.org>, Robby Cai <robby.cai@nxp.com>, Sam Ravnborg <sam@ravnborg.org>, Stefan Agner <stefan@agner.ch>, devicetree@vger.kernel.org Subject: Re: [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP Date: Mon, 28 Feb 2022 08:40:52 +0200 [thread overview] Message-ID: <YhxudFK69MYzmcRz@pendragon.ideasonboard.com> (raw) In-Reply-To: <20220228004605.367040-1-marex@denx.de> Hi Marek, Thank you for the patch. On Mon, Feb 28, 2022 at 01:45:57AM +0100, Marek Vasut wrote: > Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 > and is completely different from the LCDIFv3 found in i.MX23 in that it > has a completely scrambled register layout compared to all previous LCDIF > variants. The new LCDIFv3 also supports 36bit address space. However, > except for the complete bit reshuffling, this is still LCDIF and it still > works like one. > > Signed-off-by: Marek Vasut <marex@denx.de> > Cc: Alexander Stein <alexander.stein@ew.tq-group.com> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > Cc: Lucas Stach <l.stach@pengutronix.de> > Cc: Peng Fan <peng.fan@nxp.com> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Robby Cai <robby.cai@nxp.com> > Cc: Sam Ravnborg <sam@ravnborg.org> > Cc: Stefan Agner <stefan@agner.ch> > Cc: devicetree@vger.kernel.org > --- > Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > index 900a56cae80e6..9831ab53a053d 100644 > --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > @@ -28,6 +28,7 @@ properties: > - fsl,imx7d-lcdif > - fsl,imx8mm-lcdif > - fsl,imx8mn-lcdif > + - fsl,imx8mp-lcdif As the hardware isn't backward-compatible with any other version, I think the new compatible string should go in the previous enum block, not in this one. We don't want the imx6sx fallback. > - fsl,imx8mq-lcdif > - const: fsl,imx6sx-lcdif > -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Marek Vasut <marex@denx.de> Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>, Alexander Stein <alexander.stein@ew.tq-group.com>, dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>, Sam Ravnborg <sam@ravnborg.org>, Robby Cai <robby.cai@nxp.com> Subject: Re: [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP Date: Mon, 28 Feb 2022 08:40:52 +0200 [thread overview] Message-ID: <YhxudFK69MYzmcRz@pendragon.ideasonboard.com> (raw) In-Reply-To: <20220228004605.367040-1-marex@denx.de> Hi Marek, Thank you for the patch. On Mon, Feb 28, 2022 at 01:45:57AM +0100, Marek Vasut wrote: > Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 > and is completely different from the LCDIFv3 found in i.MX23 in that it > has a completely scrambled register layout compared to all previous LCDIF > variants. The new LCDIFv3 also supports 36bit address space. However, > except for the complete bit reshuffling, this is still LCDIF and it still > works like one. > > Signed-off-by: Marek Vasut <marex@denx.de> > Cc: Alexander Stein <alexander.stein@ew.tq-group.com> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > Cc: Lucas Stach <l.stach@pengutronix.de> > Cc: Peng Fan <peng.fan@nxp.com> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Robby Cai <robby.cai@nxp.com> > Cc: Sam Ravnborg <sam@ravnborg.org> > Cc: Stefan Agner <stefan@agner.ch> > Cc: devicetree@vger.kernel.org > --- > Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > index 900a56cae80e6..9831ab53a053d 100644 > --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml > @@ -28,6 +28,7 @@ properties: > - fsl,imx7d-lcdif > - fsl,imx8mm-lcdif > - fsl,imx8mn-lcdif > + - fsl,imx8mp-lcdif As the hardware isn't backward-compatible with any other version, I think the new compatible string should go in the previous enum block, not in this one. We don't want the imx6sx fallback. > - fsl,imx8mq-lcdif > - const: fsl,imx6sx-lcdif > -- Regards, Laurent Pinchart
next prev parent reply other threads:[~2022-02-28 6:41 UTC|newest] Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 0:45 [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP Marek Vasut 2022-02-28 0:45 ` Marek Vasut 2022-02-28 0:45 ` [PATCH 2/9] drm: mxsfb: Simplify LCDIF clock handling Marek Vasut 2022-02-28 0:45 ` [PATCH 3/9] drm: mxsfb: Simplify LCDIF IRQ handling Marek Vasut 2022-02-28 0:46 ` [PATCH 4/9] drm: mxsfb: Wrap FIFO reset and comments into mxsfb_reset_block() Marek Vasut 2022-02-28 0:46 ` [PATCH 5/9] drm: mxsfb: Move mxsfb_get_fb_paddr() away from register IO functions Marek Vasut 2022-02-28 0:46 ` [PATCH 6/9] drm: mxsfb: Factor out mxsfb_set_mode() Marek Vasut 2022-02-28 0:46 ` [PATCH 7/9] drm: mxsfb: Reorder mxsfb_crtc_mode_set_nofb() Marek Vasut 2022-02-28 0:46 ` [PATCH 8/9] drm: mxsfb: Factor out mxsfb_update_buffer() Marek Vasut 2022-02-28 0:46 ` [PATCH 9/9] drm: mxsfb: Add support for i.MX8MP LCDIF variant Marek Vasut 2022-02-28 3:48 ` kernel test robot 2022-02-28 3:48 ` kernel test robot 2022-02-28 6:37 ` [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP Liu Ying 2022-02-28 6:37 ` Liu Ying 2022-02-28 6:57 ` Marek Vasut 2022-02-28 6:57 ` Marek Vasut 2022-02-28 8:18 ` Liu Ying 2022-02-28 8:18 ` Liu Ying 2022-02-28 15:34 ` Marek Vasut 2022-02-28 15:34 ` Marek Vasut 2022-03-01 2:44 ` Liu Ying 2022-03-01 2:44 ` Liu Ying 2022-03-01 10:04 ` Lucas Stach 2022-03-01 10:19 ` Marek Vasut 2022-03-01 11:05 ` Lucas Stach 2022-03-01 13:03 ` Adam Ford 2022-03-01 13:03 ` Adam Ford 2022-03-01 13:18 ` Lucas Stach 2022-03-01 13:18 ` Lucas Stach 2022-03-01 13:37 ` [EXT] " Robby Cai 2022-03-01 13:37 ` Robby Cai 2022-03-02 2:49 ` Marek Vasut 2022-03-02 2:49 ` Marek Vasut 2022-03-02 13:14 ` Robby Cai 2022-03-02 13:14 ` Robby Cai 2022-03-03 3:16 ` Marek Vasut 2022-03-03 3:16 ` Marek Vasut 2022-03-02 2:54 ` Marek Vasut 2022-03-02 2:54 ` Marek Vasut 2022-03-02 9:23 ` Lucas Stach 2022-03-02 9:23 ` Lucas Stach 2022-03-02 9:41 ` Liu Ying 2022-03-02 9:41 ` Liu Ying 2022-03-02 11:57 ` Lucas Stach 2022-03-02 11:57 ` Lucas Stach 2022-03-03 2:54 ` Liu Ying 2022-03-03 2:54 ` Liu Ying 2022-03-03 4:14 ` Marek Vasut 2022-03-03 4:14 ` Marek Vasut 2022-03-03 8:19 ` Lucas Stach 2022-03-03 8:19 ` Lucas Stach 2022-03-03 9:14 ` Liu Ying 2022-03-03 9:14 ` Liu Ying 2022-03-03 3:14 ` Marek Vasut 2022-03-03 3:14 ` Marek Vasut 2022-03-03 8:21 ` Lucas Stach 2022-03-03 8:21 ` Lucas Stach 2022-03-04 4:50 ` Marek Vasut 2022-03-04 4:50 ` Marek Vasut 2022-02-28 6:40 ` Laurent Pinchart [this message] 2022-02-28 6:40 ` Laurent Pinchart
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=YhxudFK69MYzmcRz@pendragon.ideasonboard.com \ --to=laurent.pinchart@ideasonboard.com \ --cc=alexander.stein@ew.tq-group.com \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=l.stach@pengutronix.de \ --cc=marex@denx.de \ --cc=peng.fan@nxp.com \ --cc=robby.cai@nxp.com \ --cc=robh+dt@kernel.org \ --cc=sam@ravnborg.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: linkBe 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.