From: Chukun Pan <amadeus@jmu.edu.cn>
To: ziyao@disroot.org
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
cristian.ciocaltea@collabora.com, detlev.casanova@collabora.com,
devicetree@vger.kernel.org, heiko@sntech.de, jonas@kwiboo.se,
kishon@kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, neil.armstrong@linaro.org,
shresthprasad7@gmail.com, vkoul@kernel.org
Subject: Re: [PATCH v5 5/6] phy: rockchip: naneng-combphy: Add RK3528 support
Date: Thu, 7 Aug 2025 14:30:36 +0800 [thread overview]
Message-ID: <20250807063036.480766-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <20250728102947.38984-7-ziyao@disroot.org>
Hi,
> Rockchip RK3528 integrates one naneng-combphy that is able to operate in
> PCIe and USB3 mode. The control logic is similar to previous variants of
> naneng-combphy but the register layout is apperantly different from the
> RK3568 one.
Is this a typo? apperantly -> apparently
Thanks,
Chukun
--
2.25.1
next prev parent reply other threads:[~2025-08-07 6:35 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 [this message]
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 ` (subset) [PATCH v5 0/6] Support RK3528 variant of Rockchip naneng-combphy Vinod Koul
2025-08-22 15:06 ` 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=20250807063036.480766-1-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--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=neil.armstrong@linaro.org \
--cc=shresthprasad7@gmail.com \
--cc=vkoul@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).