From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Frank Wang <frank.wang@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
Shresth Prasad <shresthprasad7@gmail.com>,
Chukun Pan <amadeus@jmu.edu.cn>, Jonas Karlman <jonas@kwiboo.se>,
Yao Zi <ziyao@disroot.org>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v5 0/6] Support RK3528 variant of Rockchip naneng-combphy
Date: Tue, 12 Aug 2025 22:11:39 +0530 [thread overview]
Message-ID: <175501689991.633310.3061565953624951232.b4-ty@kernel.org> (raw)
In-Reply-To: <20250728102947.38984-2-ziyao@disroot.org>
On Mon, 28 Jul 2025 10:29:42 +0000, Yao Zi wrote:
> Rockchip RK3528 ships a naneng-combphy that operates in either PCIe or
> USB 3.0 mode. It has a similar control logic to previous generations of
> naneng-combphy but an apparently different register layout.
>
> This series prepares phy-rockchip-naneng-combphy.c for variants with a
> different register layout and add RK3528 support.
>
> [...]
Applied, thanks!
[1/6] dt-bindings: soc: rockchip: Add RK3528 pipe-phy GRF syscon
commit: d7122636eca216ea2876baae45483d17e40a55f6
[2/6] dt-bindings: phy: rockchip: naneng-combphy: Add power-domains property
commit: 19bb2bfdfa5dc4a912e7e5e3432290204e998ac9
[3/6] dt-bindings: phy: rockchip: naneng-combphy: Add RK3528 variant
commit: d9e0fd60d8d44b2cabd41f5e370e9d41edffe6e9
[4/6] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions
commit: 11f1896e60f61ca1948cb7920585a79ce5254c0c
[5/6] phy: rockchip: naneng-combphy: Add RK3528 support
commit: aee07ee1b97d9a3825e8db609a1c76157218cc59
Best regards,
--
~Vinod
next prev parent reply other threads:[~2025-08-12 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 10:29 [PATCH v5 0/6] Support RK3528 variant of Rockchip naneng-combphy Yao Zi
2025-07-28 10:29 ` [PATCH v5 1/6] dt-bindings: soc: rockchip: Add RK3528 pipe-phy GRF syscon Yao Zi
2025-07-28 10:29 ` [PATCH v5 2/6] dt-bindings: phy: rockchip: naneng-combphy: Add power-domains property Yao Zi
2025-07-28 10:29 ` [PATCH v5 3/6] dt-bindings: phy: rockchip: naneng-combphy: Add RK3528 variant Yao Zi
2025-07-28 10:29 ` [PATCH v5 4/6] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions Yao Zi
2025-07-28 10:29 ` [PATCH v5 5/6] phy: rockchip: naneng-combphy: Add RK3528 support Yao Zi
2025-08-07 6:30 ` Chukun Pan
2025-08-07 7:42 ` Yao Zi
2025-07-28 10:29 ` [PATCH v5 6/6] arm64: dts: rockchip: Add naneng-combphy for RK3528 Yao Zi
2025-08-12 16:41 ` Vinod Koul [this message]
2025-08-22 15:06 ` (subset) [PATCH v5 0/6] Support RK3528 variant of Rockchip naneng-combphy Heiko Stuebner
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=175501689991.633310.3061565953624951232.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=ziyao@disroot.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