devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Ying <victor.liu@nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: marex@denx.de, stefan@agner.ch, airlied@gmail.com,
	simona@ffwll.ch, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, tzimmermann@suse.de, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	shawnguo@kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH RESEND v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback
Date: Tue, 21 Oct 2025 10:52:20 +0800	[thread overview]
Message-ID: <37b8d968-a725-404e-8fd4-84c2a0bb464c@nxp.com> (raw)
In-Reply-To: <CAOMZO5AGRejEwNvkH0Di0HVi8QPduTeCSud+_GqOkD4tqEcsdA@mail.gmail.com>

On 10/20/2025, Fabio Estevam wrote:
> Hi Liu,

Hi Fabio,

> 
> On Tue, Oct 14, 2025 at 1:12 AM Liu Ying <victor.liu@nxp.com> wrote:
> 
>> Strictly speaking, I don't think i.MX6SX LCDIF is compatible with i.MX28 LCDIF
>> because at least i.MX28 LCDIF has the version and debug{0,1,2} registers(at
>> 0x1c0, 0x1d0, 0x1e0 and 0x1f0) while i.MX6SX LCDIF hasn't.
> 
> There are some DT users, such as Barebox that matches against
> fsl,imx28-lcdif, so we cannot remove it.

Hmmm, it looks like software projects like Barebox don't really follow this DT
binding.  Is it possible to fix Barebox to avoid changing this DT binding by
this patch?  I'm assuming that Uboot has already been fixed.

> 
> In my first attempt,  I tried removing it:
> 
> https://lore.kernel.org/linux-devicetree/20241028180844.154349-2-festevam@gmail.com/
> 
> but this was rejected due to potential dtb compatibility breakage:
> 
> https://lore.kernel.org/linux-devicetree/4addc413-dd13-4867-8c49-45539af7b45b@pengutronix.de/


-- 
Regards,
Liu Ying

  reply	other threads:[~2025-10-21  2:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 20:51 [PATCH RESEND v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback Fabio Estevam
2025-10-13 20:51 ` [PATCH RESEND v4 2/3] dt-bindings: lcdif: Expand the imx6sl/imx6sll fallbacks Fabio Estevam
2025-10-14  3:55   ` Liu Ying
2025-10-13 20:51 ` [PATCH RESEND v4 3/3] ARM: dts: imx6sl: Provide a more specific lcdif compatible Fabio Estevam
2025-10-14  4:12 ` [PATCH RESEND v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback Liu Ying
2025-10-20 17:24   ` Fabio Estevam
2025-10-21  2:52     ` Liu Ying [this message]
2025-11-04 20:44       ` Fabio Estevam
2025-11-07 21:05         ` Ahmad Fatoum
2025-11-10  9:14           ` Liu Ying
  -- strict thread matches above, loose matches on Subject: below --
2025-09-10  2:05 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=37b8d968-a725-404e-8fd4-84c2a0bb464c@nxp.com \
    --to=victor.liu@nxp.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marex@denx.de \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=stefan@agner.ch \
    --cc=tzimmermann@suse.de \
    /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).