From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>
Subject: Re: Pull request: u-boot-sunxi/master for v2025.07
Date: Mon, 28 Apr 2025 13:05:30 -0600 [thread overview]
Message-ID: <20250428190530.GF5495@bill-the-cat> (raw)
In-Reply-To: <20250428150907.206134-1-andre.przywara@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2521 bytes --]
On Mon, Apr 28, 2025 at 04:09:07PM +0100, Andre Przywara wrote:
> Hi Tom,
>
> please pull the sunxi/master branch, containing changes for the second
> part of this cycle's sunxi updates.
>
> We have improvements to the reliability of H6 and H616 DRAM
> initialisation, hopefully avoiding those occasional size misdetections
> many people reported before.
> Also there is some modernisation of the USB PHY code, to use DT provided
> regulators and GPIOs, instead of relying on this being badly duplicated
> in Kconfig. This also happens to fix broken USB operations for older
> boards (using the A20 SoCs, for instance), which were clashing over
> grabbing some GPIOs, leading to a driver bailout.
> There is also some rework of the H6/H616 SPL clock code, to prepare it
> for being reused by the upcoming Allwinner A523 support. This drops the
> usage of C structs to model MMIO register frames, and replaces them by
> using an addition of the base address with a macro defined offset.
> Also in preparation for A523 there is one fix and one addition for the
> FEL code, to prepare for the GICv3 interrupt controller that the new SoC
> uses. And since this is a simple fix, and was ready, there is also the
> watchdog driver for that new SoC. Finally tossing in an easy fix to some
> H616 defconfig files to enable eMMC.
>
> I also use the opportunity to enable proper page table protection
> (observing read-only and no-execute attributes), support for which the
> arm64 port recently gained. I didn't spot any issues on my arm64 board
> tests, but it can be easily disabled or backed out again in case any
> issues arise.
>
> Full support for the two new SoC series (A133 and A523) we are working
> on is not quite ready yet, but might follow still a bit later if
> progress permits.
>
> CI passed, and boot-tested on at least one board with a H616, H6, A64,
> H3, A20, T113s.
>
> Thanks,
> Andre
>
> =================================
> The following changes since commit 5a0a93a768487e55ebe50a34cc90d751bf99cc56:
>
> Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-riscv (2025-04-25 13:13:17 -0600)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-sunxi.git master
>
> for you to fetch changes up to d5837bbed841889428379ffff3cc19c9dca4cb6d:
>
> sunxi: clock: H6: remove struct sunxi_prcm_reg (2025-04-28 15:03:28 +0100)
>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2025-04-28 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 15:09 Pull request: u-boot-sunxi/master for v2025.07 Andre Przywara
2025-04-28 19:05 ` 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=20250428190530.GF5495@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--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