From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
Andre Przywara <andre.przywara@arm.com>
Cc: linux-sunxi@lists.linux.dev, Chen-Yu Tsai <wens@kernel.org>
Subject: Re: [PATCH 2/4] sunxi: switch Allwinner A80 boards to OF_UPSTREAM
Date: Sun, 26 Oct 2025 07:06:03 +0100 [thread overview]
Message-ID: <6203838.lOV4Wx5bFT@jernej-laptop> (raw)
In-Reply-To: <20251026012357.16773-3-andre.przywara@arm.com>
Dne nedelja, 26. oktober 2025 ob 02:23:54 Srednjeevropski standardni čas je Andre Przywara napisal(a):
> In contrast to some other Allwinner SoCs, there is no difference between
> the DTs for the Allwinner A80 SoCs (sun9i) between the U-Boot and the
> Linux kernel repository.
>
> Remove the old copies of the A80 related .dts and .dtsi files, and switch
> most of sun9i boards over to use OF_UPSTREAM.
>
> There is the Sunchip CX-A99 (family of) board(s) for which we don't have
> a DT in the kernel tree. Keep the .dts file in the legacy U-Boot DT
> directory, and let the board's defconfig opt out of OF_UPSTREAM.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Same comment as previous patch.
I'm not sure keeping Sunchip CX-A99 makes much sense. This means that
there were never enough interest in it to at least upstream DT file to
Linux.
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
next prev parent reply other threads:[~2025-10-26 6:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 1:23 [PATCH 0/4] sunxi: dts: update devicetree files Andre Przywara
2025-10-26 1:23 ` [PATCH 1/4] sunxi: switch the Allwinner T113 SoC to OF_UPSTREAM Andre Przywara
2025-10-26 5:59 ` Jernej Škrabec
2025-10-26 1:23 ` [PATCH 2/4] sunxi: switch Allwinner A80 boards " Andre Przywara
2025-10-26 6:06 ` Jernej Škrabec [this message]
2025-10-26 1:23 ` [PATCH 3/4] sunxi: dts: arm64: update devicetree files from Linux kernel tree Andre Przywara
2025-10-26 1:23 ` [PATCH 4/4] sunxi: dts: arm: " Andre Przywara
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=6203838.lOV4Wx5bFT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wens@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