From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Yao Zi" <ziyao@disroot.org>, "Vinod Koul" <vkoul@kernel.org>,
"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>
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: [PATCH v3 3/5] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions
Date: Tue, 20 May 2025 13:39:18 +0200 [thread overview]
Message-ID: <DA0YJ89890ND.3NKPS3RWC012P@cknow.org> (raw)
In-Reply-To: <aCxjqDr3VivDCrBx@pie.lan>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Tue May 20, 2025 at 1:12 PM CEST, Yao Zi wrote:
> If putting RK3528 at first really confuses you, I'd like to add some
> extra comments to explicitly split these two kinds of register layouts
> apart and claim they aren't compatible. Although to me it's somehow
> obvious, as most definitions are prefixed with either RK3528 or RK3568.
No need. This is just another PEBKAC issue.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Yao Zi" <ziyao@disroot.org>, "Vinod Koul" <vkoul@kernel.org>,
"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>
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: [PATCH v3 3/5] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions
Date: Tue, 20 May 2025 13:39:18 +0200 [thread overview]
Message-ID: <DA0YJ89890ND.3NKPS3RWC012P@cknow.org> (raw)
In-Reply-To: <aCxjqDr3VivDCrBx@pie.lan>
[-- Attachment #1.1: Type: text/plain, Size: 414 bytes --]
On Tue May 20, 2025 at 1:12 PM CEST, Yao Zi wrote:
> If putting RK3528 at first really confuses you, I'd like to add some
> extra comments to explicitly split these two kinds of register layouts
> apart and claim they aren't compatible. Although to me it's somehow
> obvious, as most definitions are prefixed with either RK3528 or RK3568.
No need. This is just another PEBKAC issue.
Cheers,
Diederik
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 112 bytes --]
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Yao Zi" <ziyao@disroot.org>, "Vinod Koul" <vkoul@kernel.org>,
"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>
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: [PATCH v3 3/5] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions
Date: Tue, 20 May 2025 13:39:18 +0200 [thread overview]
Message-ID: <DA0YJ89890ND.3NKPS3RWC012P@cknow.org> (raw)
In-Reply-To: <aCxjqDr3VivDCrBx@pie.lan>
[-- Attachment #1.1: Type: text/plain, Size: 414 bytes --]
On Tue May 20, 2025 at 1:12 PM CEST, Yao Zi wrote:
> If putting RK3528 at first really confuses you, I'd like to add some
> extra comments to explicitly split these two kinds of register layouts
> apart and claim they aren't compatible. Although to me it's somehow
> obvious, as most definitions are prefixed with either RK3528 or RK3568.
No need. This is just another PEBKAC issue.
Cheers,
Diederik
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-20 11:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 16:16 [PATCH v3 0/5] Support RK3528 variant of Rockchip naneng-combphy Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` [PATCH v3 1/5] dt-bindings: soc: rockchip: Add RK3528 pipe-phy GRF syscon Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` [PATCH v3 2/5] dt-bindings: phy: rockchip: naneng-combphy: Add RK3528 variant Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:39 ` Conor Dooley
2025-05-19 16:39 ` Conor Dooley
2025-05-19 16:39 ` Conor Dooley
2025-05-19 16:16 ` [PATCH v3 3/5] phy: rockchip: naneng-combphy: Add SoC prefix to register definitions Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 19:26 ` Diederik de Haas
2025-05-19 19:26 ` Diederik de Haas
2025-05-19 19:26 ` Diederik de Haas
2025-05-20 3:53 ` Yao Zi
2025-05-20 3:53 ` Yao Zi
2025-05-20 3:53 ` Yao Zi
2025-05-20 7:24 ` neil.armstrong
2025-05-20 7:24 ` neil.armstrong
2025-05-20 7:24 ` neil.armstrong
2025-05-20 8:37 ` Diederik de Haas
2025-05-20 8:37 ` Diederik de Haas
2025-05-20 8:37 ` Diederik de Haas
2025-05-20 11:12 ` Yao Zi
2025-05-20 11:12 ` Yao Zi
2025-05-20 11:12 ` Yao Zi
2025-05-20 11:39 ` Diederik de Haas [this message]
2025-05-20 11:39 ` Diederik de Haas
2025-05-20 11:39 ` Diederik de Haas
2025-05-19 16:16 ` [PATCH v3 4/5] phy: rockchip: naneng-combphy: Add RK3528 support Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-20 7:22 ` neil.armstrong
2025-05-20 7:22 ` neil.armstrong
2025-05-20 7:22 ` neil.armstrong
2025-05-19 16:16 ` [PATCH v3 5/5] arm64: dts: rockchip: Add naneng-combphy for RK3528 Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-19 16:16 ` Yao Zi
2025-05-20 17:51 ` Jonas Karlman
2025-05-20 17:51 ` Jonas Karlman
2025-05-20 17:51 ` Jonas Karlman
2025-05-21 2:27 ` Yao Zi
2025-05-21 2:27 ` Yao Zi
2025-05-21 2:27 ` Yao Zi
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=DA0YJ89890ND.3NKPS3RWC012P@cknow.org \
--to=didi.debian@cknow.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.