From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: marex@denx.de, a.fatoum@pengutronix.de, andreas@kemnade.info,
kernel@pengutronix.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v4 2/3] dt-bindings: lcdif: Expand the imx6sl/imx6sll fallbacks
Date: Fri, 1 Nov 2024 10:54:05 -0300 [thread overview]
Message-ID: <20241101135406.47836-2-festevam@gmail.com> (raw)
In-Reply-To: <20241101135406.47836-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
mx6sl.dtsi and imx6sll.dtsi have the following lcdif entries:
compatible = "fsl,imx6sl-lcdif", "fsl,imx28-lcdif";
This causes dt-schema warnings as the current binding only
allow 'fsl,imx6sx-lcdif' as fallback.
['fsl,imx6sl-lcdif', 'fsl,imx28-lcdif'] is too long
['fsl,imx6sll-lcdif', 'fsl,imx28-lcdif'] is too long
The imx6sx-lcdif programming model has more advanced features, such
as overlay plane and the CRC32 support than the imx28-lcdif IP.
Expand the imx6sl/imx6sll lcdif fallbacks to accept a less specific
fsl,imx28-lcdif fallback:
compatible = "fsl,imx6sl-lcdif", "fsl,imx6sx-lcdif", "fsl,imx28-lcdif";
This helps keeping DT compatibility as well as using the more advanced
lcdif features found on imx6sl and imx6sll.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v3:
- None.
Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
index ad0cca562463..72e509bc975b 100644
--- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
+++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
@@ -23,14 +23,18 @@ properties:
- fsl,imx93-lcdif
- items:
- enum:
- - fsl,imx6sl-lcdif
- - fsl,imx6sll-lcdif
- fsl,imx6ul-lcdif
- fsl,imx7d-lcdif
- fsl,imx8mm-lcdif
- fsl,imx8mn-lcdif
- fsl,imx8mq-lcdif
- const: fsl,imx6sx-lcdif
+ - items:
+ - enum:
+ - fsl,imx6sl-lcdif
+ - fsl,imx6sll-lcdif
+ - const: fsl,imx6sx-lcdif
+ - const: fsl,imx28-lcdif
- items:
- enum:
- fsl,imx6sx-lcdif
--
2.34.1
next prev parent reply other threads:[~2024-11-01 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:54 [PATCH v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback Fabio Estevam
2024-11-01 13:54 ` Fabio Estevam [this message]
2024-11-04 15:43 ` [PATCH v4 2/3] dt-bindings: lcdif: Expand the imx6sl/imx6sll fallbacks Rob Herring (Arm)
2024-11-04 15:45 ` Ahmad Fatoum
2024-11-01 13:54 ` [PATCH v4 3/3] ARM: dts: imx6sl: Provide a more specific lcdif compatible Fabio Estevam
2024-11-04 15:46 ` Ahmad Fatoum
2024-11-04 15:42 ` [PATCH v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback Rob Herring (Arm)
2024-12-17 13:20 ` Fabio Estevam
2025-02-19 12:40 ` Fabio Estevam
2024-11-04 15:46 ` Ahmad Fatoum
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=20241101135406.47836-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@denx.de \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marex@denx.de \
--cc=robh@kernel.org \
--cc=shawnguo@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.