From: "Rob Herring (Arm)" <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, shawnguo@kernel.org,
imx@lists.linux.dev, conor+dt@kernel.org,
Fabio Estevam <festevam@denx.de>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
krzk+dt@kernel.org, a.fatoum@pengutronix.de,
dri-devel@lists.freedesktop.org, andreas@kemnade.info,
marex@denx.de
Subject: Re: [PATCH v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback
Date: Mon, 4 Nov 2024 09:42:38 -0600 [thread overview]
Message-ID: <173073495749.210192.9138587910771237679.robh@kernel.org> (raw)
In-Reply-To: <20241101135406.47836-1-festevam@gmail.com>
On Fri, 01 Nov 2024 10:54:04 -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> imx6sx.dtsi has the following lcdif entries:
>
> compatible = "fsl,imx6sx-lcdif", "fsl,imx28-lcdif";
>
> This causes the following dt-schema warning:
>
> ['fsl,imx6sx-lcdif', 'fsl,imx28-lcdif'] is too long
>
> To keep DT compatibility, document 'fsl,imx28-lcdif' as a possible
> 'fsl,imx6sx-lcdif' fallback.
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Changes since v3:
> - Also update the example.
>
> Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-11-04 15:42 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 ` [PATCH v4 2/3] dt-bindings: lcdif: Expand the imx6sl/imx6sll fallbacks Fabio Estevam
2024-11-04 15:43 ` 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 ` Rob Herring (Arm) [this message]
2024-12-17 13:20 ` [PATCH v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback 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=173073495749.210192.9138587910771237679.robh@kernel.org \
--to=robh@kernel.org \
--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=festevam@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox