devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>,
	Andreas Kemnade <andreas@kemnade.info>
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>, Marek Vasut <marex@denx.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 2/2] ARM: dts: imx6sx: Remove fsl,imx6sx-lcdif fallback
Date: Tue, 29 Oct 2024 10:50:51 +0100	[thread overview]
Message-ID: <4addc413-dd13-4867-8c49-45539af7b45b@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5APJM57_ixBiRFZSZex3AiawA=mtqMszdGezVoajaXYhA@mail.gmail.com>

Hi,

[Cc += Marek, who maintains the Linux driver]

On 28.10.24 20:48, Fabio Estevam wrote:
> Hi Andreas,
> 
> On Mon, Oct 28, 2024 at 3:47 PM Andreas Kemnade <andreas@kemnade.info> wrote:
> 
>> 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.

Thanks for raising this point, Andreas. I think it's important to adjust
the binding's compatible list binding if need be to avoid breaking DT
consumers.

>> Same for Patch 1. But I cannot test that and do not have a strong
>> opinion here.
> 
> U-Boot would not be broken after these series:
> 
> https://source.denx.de/u-boot/u-boot/-/blob/master/drivers/video/mxsfb.c?ref_type=heads#L388

The barebox driver only matches against fsl,imx23-lcdif and fsl,imx28-lcdif:
https://elixir.bootlin.com/barebox/v2024.10.0/source/drivers/video/stm.c#L579

The MXSFB IP appears to be completely backwards compatible. Otherwise the
i.MX6SL/i.MX6SLL integration of it wouldn't have worked as it used to match
against imx28-lcdif so far. Checking the Linux driver, the differences to
the i.MX6SX also look like they are not backwards incompatible.

On the other hand, Linux users may start to make use of the new features
that aren't available without having imx6sx-lcdif in the compatible list,
like the overlay plane and the CRC32 functionality.

With an eye towards improving device tree stability, I think it's more
appropriate to adjust the binding to have three compatibles instead.

Thanks,
Ahmad

> 
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-10-29  9:51 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
2024-10-28 19:48     ` Fabio Estevam
2024-10-29  9:50       ` Ahmad Fatoum [this message]
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=4addc413-dd13-4867-8c49-45539af7b45b@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=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=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 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).