From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH] sunxi: dts: arm/arm64: update devicetree files from Linux-v6.10
Date: Wed, 17 Jul 2024 11:51:53 -0600 [thread overview]
Message-ID: <20240717175153.GR561963@bill-the-cat> (raw)
In-Reply-To: <20240717143415.343827-1-andre.przywara@arm.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Wed, Jul 17, 2024 at 03:34:15PM +0100, Andre Przywara wrote:
> Sync the devicetree files from the official Linux kernel tree, v6.10.
> This is covering Allwinner SoCs with 32-bit and 64-bit ARM cores.
>
> Besides mostly cosmectic changes, this adds cpufreq support to H616
> boards, Nothing that U-Boot needs for itself, but helpful to pass on
> to kernels. We also get the .dts files for the Tanix TX1 TV box and
> three Anbernic handheld gaming devices.
>
> As before, this omits the non-backwards compatible changes to the R_INTC
> controller, to remain compatible with older kernels.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
This reminded me I needed to see that v6.10-dts is tagged upstream now.
So, for the record, when can we move sunxi to OF_UPSTREAM? Or what's
blocking it? Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-07-17 17:51 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 [this message]
[not found] ` <191A0F66-E2AE-4D1B-ACBE-E411E135BB61@arm.com>
2024-07-20 17:14 ` Tom Rini
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=20240717175153.GR561963@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