From: Andreas Kemnade <andreas@kemnade.info>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, 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,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH 2/2] ARM: dts: imx6sx: Remove fsl,imx6sx-lcdif fallback
Date: Mon, 28 Oct 2024 19:47:28 +0100 [thread overview]
Message-ID: <20241028194728.0655edd3@akair> (raw)
In-Reply-To: <20241028180844.154349-2-festevam@gmail.com>
Hi,
Am Mon, 28 Oct 2024 15:08:44 -0300
schrieb Fabio Estevam <festevam@gmail.com>:
> From: Fabio Estevam <festevam@denx.de>
>
> According to fsl,lcdif.yaml, "fsl,imx6sx-lcdif" does not have any
> fallback.
>
> Change it accordingly to fix the following dt-schema warnings:
>
> ['fsl,imx6sx-lcdif', 'fsl,imx28-lcdif'] is too long
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
As the devicetree might also be used with other software (e.g. u-boot),
this might break something. So if u-boot (or any other software) does
work with fsl,imx28-lcdif because it only uses a subset of features of
fsl,imx6sx, it might be worth changing the binding instead.
Same for Patch 1. But I cannot test that and do not have a strong
opinion here.
But thanks for touching this annoying warning.
Regards,
Andreas
next prev parent reply other threads:[~2024-10-28 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 18:08 [PATCH 1/2] ARM: dts: imx6sl: Fix lcdif compatible fallback Fabio Estevam
2024-10-28 18:08 ` [PATCH 2/2] ARM: dts: imx6sx: Remove fsl,imx6sx-lcdif fallback Fabio Estevam
2024-10-28 18:47 ` Andreas Kemnade [this message]
2024-10-28 19:48 ` Fabio Estevam
2024-10-29 9:50 ` Ahmad Fatoum
2024-10-29 11:17 ` Fabio Estevam
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=20241028194728.0655edd3@akair \
--to=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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).