From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH] sunxi: dts: arm/arm64: update devicetree files from Linux-v6.10
Date: Sat, 20 Jul 2024 11:14:15 -0600 [thread overview]
Message-ID: <20240720171415.GG561963@bill-the-cat> (raw)
In-Reply-To: <191A0F66-E2AE-4D1B-ACBE-E411E135BB61@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Fri, Jul 19, 2024 at 11:21:54PM +0100, Andre Przywara wrote:
> Hi Tom,
> Sorry for top posting, am on the road.
>
> First: The Allwinner drivers in U-Boot work with mainline kernel DTs for ages, so there are no code changes required.
> We manually sync the DTs from the kernel for years, but I always do one change:
>
> In kernel v5.13 the Allwinner IRQ controller (not the GIC) DT binding and DTs changed in an incompatible way, and some critical devices now route their IRQ through that controller instead of to the GIC. If an older kernel sees such a new DT, some critical devices fail to probe due to that, and the kernel does not boot. Using the old DT routing fixes that, at the expense of losing some advanced power saving features.
> So in the interest of better compatibility with older kernels and $fdtcontroladdr (default for UEFI boot), I always kept the old way during the U-Boot sync. This affects all devices with the popular H3, A64 and H6 SoCs, among others. A20 and older or H616s are not affected.
>
> So my plan was to migrate the latter group ASAP (after the v6.10 sync), and then maybe the others in the next cycle, which means pulling the plug on original Debian Buster kernels, for instance. 5.13 is three years old by now, so I guess this might be fine now.
>
> Does that make sense?
Yes, that sounds reasonable, thanks for explaining.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2024-07-20 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 14:34 [PATCH] sunxi: dts: arm/arm64: update devicetree files from Linux-v6.10 Andre Przywara
2024-07-17 17:51 ` Tom Rini
[not found] ` <191A0F66-E2AE-4D1B-ACBE-E411E135BB61@arm.com>
2024-07-20 17:14 ` Tom Rini [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=20240720171415.GG561963@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=u-boot@lists.denx.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