From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
Frank Rowand <frowand.list@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES"
<linux-samsung-soc@vger.kernel.org>,
Sylwester Nawrocki <snawrocki@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Gregory Clement <gregory.clement@bootlin.com>,
Krzysztof Kozlowski <krzk@kernel.org>, arm-soc <arm@kernel.org>,
DTML <devicetree@vger.kernel.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
Arnd Bergmann <arnd@arndb.de>, Maxime Ripard <mripard@kernel.org>,
SoC Team <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [GIT PULL 2/3] ARM: dts: samsung: DTS for v5.12
Date: Mon, 8 Feb 2021 12:21:22 -0600 [thread overview]
Message-ID: <YCGBIvRfoP0BeyrP@builder.lan> (raw)
In-Reply-To: <CAMuHMdWZ8QmiQCmiW9AvCpviNZeuaxThSo_4Xb2DGEs9hMTKMQ@mail.gmail.com>
On Sat 06 Feb 13:47 CST 2021, Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Sat, Feb 6, 2021 at 3:36 PM Arnd Bergmann <arnd@kernel.org> wrote:
> > That said, I'm still not happy about the patch we discussed in the
> > other email thread[1] and I'd like to handle it a little more strictly in
> > the future, but I agree this wasn't obvious and we have been rather
> > inconsistent about it in the past, with some platform maintainers
> > handling it way more strictly than others.
> >
> > I've added the devicetree maintainers and a few other platform
> > maintainers to Cc here, maybe they can provide some further
> > opinions on the topic so we can come to an approach that
> > works for everyone.
> >
> > My summary of the thread in [1] is there was a driver bug that
> > required a DT binding change. Krzysztof and the other involved
> > parties made sure the driver handles it in a backward-compatible
> > way (an old dtb file will still run into the bug but keep working
> > with new kernels), but decided that they did not need to worry
> > about the opposite case (running an old kernel with an updated
> > dtb). I noticed the compatibility break and said that I would
> > prefer this to be done in a way that is compatible both ways,
> > or at the minimum be alerted about the binding break in the
> > pull request, with an explanation about why this had to be done,
> > even when we don't think anyone is going to be affected.
> >
> > What do others think about this? Should we generally assume
> > that breaking old kernels with new dtbs is acceptable, or should
> > we try to avoid it if possible, the same way we try to avoid
> > breaking new kernels with old dtbs? Should this be a platform
> > specific policy or should we try to handle all platforms the same
> > way?
>
> For Renesas SoCs, we typically only consider compatibility of new
> kernels with old DTBs, not the other way around.
> However, most DTB updates are due to new hardware support, so using the
> new DTB with an old kernel usually just means no newly documented
> hardware, or new feature, is being used by the old kernel.
>
This is the case for the Qualcomm tree as well, it's expected that a new
kernel should work with older DT. But, while we don't actively try to
break it, there are plenty of examples where we don't/can't give the
promise in the other direction.
These examples ranges from advancements in power management
(implementation and binding) to DT validation forcing deprecation and
adoption of new bindings.
Regards,
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-08 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 19:12 [GIT PULL 0/3] Samsung for v5.12 Krzysztof Kozlowski
2021-01-25 19:12 ` [GIT PULL 1/3] soc: samsung: drivers " Krzysztof Kozlowski
2021-01-30 11:28 ` Arnd Bergmann
2021-01-25 19:12 ` [GIT PULL 2/3] ARM: dts: samsung: DTS " Krzysztof Kozlowski
2021-02-06 13:45 ` Krzysztof Kozlowski
2021-02-06 14:35 ` Arnd Bergmann
2021-02-06 15:06 ` Krzysztof Kozlowski
2021-02-06 19:47 ` Geert Uytterhoeven
2021-02-08 8:40 ` Tony Lindgren
2021-02-08 18:21 ` Bjorn Andersson [this message]
2021-02-08 18:42 ` Krzysztof Kozlowski
2021-02-08 19:52 ` Arnd Bergmann
2021-02-08 21:35 ` Alexandre Belloni
2021-02-08 22:14 ` Arnd Bergmann
2021-02-08 23:10 ` Alexandre Belloni
2021-02-09 8:25 ` Geert Uytterhoeven
2021-02-09 14:27 ` Rob Herring
2021-02-09 17:11 ` Bjorn Andersson
2021-02-09 19:19 ` Frank Rowand
2021-02-09 23:06 ` Arnd Bergmann
2021-01-25 19:12 ` [GIT PULL 3/3] arm64: " Krzysztof Kozlowski
2021-01-30 11:34 ` Arnd Bergmann
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=YCGBIvRfoP0BeyrP@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@st.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gregory.clement@bootlin.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mripard@kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=snawrocki@kernel.org \
--cc=soc@kernel.org \
--cc=tony@atomide.com \
/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).