From: Heiko Stuebner <heiko@sntech.de>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, FUKAUMI Naoki <naoki@radxa.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: (subset) [PATCH v2 0/5] arm64: dts: rockchip: add ROCK 5B+ support
Date: Fri, 9 May 2025 22:00:22 +0200 [thread overview]
Message-ID: <174682074870.2029046.8482000655658409755.b4-ty@sntech.de> (raw)
In-Reply-To: <20250508-rock5bp-for-upstream-v2-0-677033cc1ac2@kernel.org>
On Thu, 08 May 2025 19:48:49 +0200, Sebastian Reichel wrote:
> This series adds support for the ROCK 5B+, which (as the name suggests)
> is an improved version of the ROCK 5B. It also adds initial USB-C
> support for both the ROCK 5B and the 5B+.
>
> Changes in PATCHv2:
> - Link to v1: https://lore.kernel.org/r/20250324-rock5bp-for-upstream-v1-0-6217edf15b19@kernel.org
> - Replaced DT binding patch with the version from NAOKI
> - Dropped unused pinctrl for vcc5v0_host_en from the shared DT
> - Moved USB-C SBU DC pins to board specific files, since they differ
> between Rock 5B and Rock 5B+
> - Added pinmux for SBU DC pins
> - Rebased to latest version of Heiko's for-next branch
> - Disable USB-C on Rock 5B for now
>
> [...]
Applied, thanks!
[1/5] arm64: dts: rockchip: move rock 5b to include file
commit: aadfbdcf7e1e7f3892e0e4bdcc3c9c7c9adfb723
[2/5] arm64: dts: rockchip: move rock 5b to include file
commit: aadfbdcf7e1e7f3892e0e4bdcc3c9c7c9adfb723
The two above squashed together as intended and talked about
on IRC.
[3/5] dt-bindings: arm: rockchip: Add Radxa ROCK 5B+
commit: 874c1117621d441e0ef4a609665f228a4b8a1932
[4/5] arm64: dts: rockchip: add Rock 5B+
commit: 376cb9696298df2028afb620a9dc6c4b10a18605
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2025-05-09 20:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 17:48 Sebastian Reichel
2025-05-08 17:48 ` [PATCH v2 1/5] arm64: dts: rockchip: move rock 5b to include file Sebastian Reichel
2025-05-08 17:48 ` [PATCH v2 2/5] " Sebastian Reichel
2025-05-09 12:44 ` Diederik de Haas
2025-05-09 12:54 ` Heiko Stübner
2025-05-09 13:08 ` Sebastian Reichel
2025-05-09 13:14 ` Diederik de Haas
2025-05-08 17:48 ` [PATCH v2 3/5] dt-bindings: arm: rockchip: Add Radxa ROCK 5B+ Sebastian Reichel
2025-05-08 17:48 ` [PATCH v2 4/5] arm64: dts: rockchip: add Rock 5B+ Sebastian Reichel
2025-05-08 17:48 ` [PATCH v2 5/5] arm64: dts: rockchip: add USB-C support for ROCK 5B+ Sebastian Reichel
2025-05-09 13:18 ` Diederik de Haas
2025-05-09 14:17 ` Sebastian Reichel
2025-05-09 14:17 ` [PATCH v2 0/5] arm64: dts: rockchip: add ROCK 5B+ support Rob Herring (Arm)
2025-05-09 15:12 ` Heiko Stübner
2025-05-09 17:50 ` Sebastian Reichel
2025-05-09 20:00 ` Heiko Stuebner [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=174682074870.2029046.8482000655658409755.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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
all inboxes | Powered by JetHome®