From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, David Jander <david@protonic.nl>
Subject: Re: [PATCH 0/8] Add Rockchip RK3576 support
Date: Wed, 13 Aug 2025 07:28:56 +0200 [thread overview]
Message-ID: <175506293615.3439396.13253783696389984645.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250811064026.753776-1-david@protonic.nl>
On Mon, 11 Aug 2025 08:40:18 +0200, David Jander wrote:
> This set of patches adds basic support for Rockchip RK3576 SoCs.
> Peripheral support is added for aiodev (SARADC) and GPIO.
>
> David Jander (8):
> clk: rockchip: clk-pll.c: Fix macro name confusion
> clk: rockchip: Introduce rockchip_grf_type enum from kernel driver
> ARM: Initial support for Rockchip RK3576
> arm: dts: Add barebox specific RK3576.dtsi
> aiodev: rockchip_saradc.c: Add support for RK3576
> gpio: gpio-rockchip.c: Add support for GPIO_TYPE_V2_2
> arm: dts: rk3576.dtsi: Add gpio aliases
> phy: phy-rockchip-inno-usb2.c: Fix crash if phyclk isn't found
>
> [...]
Applied, thanks!
[1/8] clk: rockchip: clk-pll.c: Fix macro name confusion
https://git.pengutronix.de/cgit/barebox/commit/?id=6890455f539d (link may not be stable)
[2/8] clk: rockchip: Introduce rockchip_grf_type enum from kernel driver
https://git.pengutronix.de/cgit/barebox/commit/?id=1c5e15007526 (link may not be stable)
[3/8] ARM: Initial support for Rockchip RK3576
https://git.pengutronix.de/cgit/barebox/commit/?id=81b2c56c7e9d (link may not be stable)
[4/8] arm: dts: Add barebox specific RK3576.dtsi
https://git.pengutronix.de/cgit/barebox/commit/?id=9360ce1f212d (link may not be stable)
[5/8] aiodev: rockchip_saradc.c: Add support for RK3576
https://git.pengutronix.de/cgit/barebox/commit/?id=73cf74c81619 (link may not be stable)
[6/8] gpio: gpio-rockchip.c: Add support for GPIO_TYPE_V2_2
https://git.pengutronix.de/cgit/barebox/commit/?id=319857a87b56 (link may not be stable)
[7/8] arm: dts: rk3576.dtsi: Add gpio aliases
https://git.pengutronix.de/cgit/barebox/commit/?id=a53bd9e76548 (link may not be stable)
[8/8] phy: phy-rockchip-inno-usb2.c: Fix crash if phyclk isn't found
https://git.pengutronix.de/cgit/barebox/commit/?id=22cf8296b5b0 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next prev parent reply other threads:[~2025-08-13 5:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 6:40 David Jander
2025-08-11 6:40 ` [PATCH 1/8] clk: rockchip: clk-pll.c: Fix macro name confusion David Jander
2025-08-11 6:40 ` [PATCH 2/8] clk: rockchip: Introduce rockchip_grf_type enum from kernel driver David Jander
2025-08-11 6:40 ` [PATCH 3/8] ARM: Initial support for Rockchip RK3576 David Jander
2025-08-11 6:40 ` [PATCH 4/8] arm: dts: Add barebox specific RK3576.dtsi David Jander
2025-08-11 6:40 ` [PATCH 5/8] aiodev: rockchip_saradc.c: Add support for RK3576 David Jander
2025-08-11 6:40 ` [PATCH 6/8] gpio: gpio-rockchip.c: Add support for GPIO_TYPE_V2_2 David Jander
2025-08-11 6:40 ` [PATCH 7/8] arm: dts: rk3576.dtsi: Add gpio aliases David Jander
2025-08-11 6:40 ` [PATCH 8/8] phy: phy-rockchip-inno-usb2.c: Fix crash if phyclk isn't found David Jander
2025-08-13 5:28 ` Sascha Hauer [this message]
2025-08-13 5:32 ` [PATCH 0/8] Add Rockchip RK3576 support Sascha Hauer
2025-08-13 6:51 ` David Jander
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=175506293615.3439396.13253783696389984645.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
/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