From: Lucas Stach <l.stach@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: marex@denx.de, devicetree@vger.kernel.org, conor+dt@kernel.org,
Fabio Estevam <festevam@denx.de>,
kernel@puri.sm, dri-devel@lists.freedesktop.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
martink@posteo.de
Subject: Re: [PATCH 1/3] drm/mxsfb: Add an entry for "fsl,imx8mq-lcdif"
Date: Wed, 13 Dec 2023 10:02:51 +0100 [thread overview]
Message-ID: <a8188accccc12b524de0e479a1780f8447fb45dd.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5D0rxTmxGZX1Obfm9+t46gW6XpGWDcHDzocQd6p5OokBg@mail.gmail.com>
Hi Fabio,
Am Dienstag, dem 12.12.2023 um 15:28 -0300 schrieb Fabio Estevam:
> Hi Lucas,
>
> On Tue, Dec 12, 2023 at 3:19 PM Lucas Stach <l.stach@pengutronix.de> wrote:
>
> > I don't really like this series. While we don't make any strong
> > guarantees in this way, it breaks booting older kernels with a new DT.
>
> I thought we needed only to guarantee that old DTs still run with
> newer kernels, not the other way around.
>
That's right. At least in the i.MX world we never made a strong
guarantee in that way.
Still we should not break it deliberately if there isn't a good reason
to do so. And I _feel_ that "DT schema isn't able to express the SoC
integration" isn't a good enough reason to break things.
But maybe there is a way to describe this in the DT schema, that we
aren't aware of yet. I'm not quite up-to-date with all the DT schema
stuff...
Regards,
Lucas
prev parent reply other threads:[~2023-12-13 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 20:41 [PATCH 1/3] drm/mxsfb: Add an entry for "fsl,imx8mq-lcdif" Fabio Estevam
2023-12-11 20:41 ` [PATCH 2/3] dt-bindings: lcdif: Decouple imx8mq from imx6sx Fabio Estevam
2023-12-12 16:52 ` Conor Dooley
2023-12-11 20:41 ` [PATCH 3/3] arm64: dts: imx8mq: Exclude "fsl,imx6sx-lcdif" Fabio Estevam
2023-12-12 18:19 ` [PATCH 1/3] drm/mxsfb: Add an entry for "fsl,imx8mq-lcdif" Lucas Stach
2023-12-12 18:28 ` Fabio Estevam
2023-12-13 9:02 ` Lucas Stach [this message]
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=a8188accccc12b524de0e479a1780f8447fb45dd.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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=kernel@puri.sm \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=marex@denx.de \
--cc=martink@posteo.de \
--cc=robh+dt@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