From: neil.armstrong@linaro.org
To: Yao Zi <ziyao@disroot.org>,
Diederik de Haas <didi.debian@cknow.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 09:24:36 +0200 [thread overview]
Message-ID: <ab2692a5-e428-40bf-8071-cad6ae96dc3b@linaro.org> (raw)
In-Reply-To: <aCv8vRu8gjrvK8wr@pie.lan>
On 20/05/2025 05:53, Yao Zi wrote:
> On Mon, May 19, 2025 at 09:26:05PM +0200, Diederik de Haas wrote:
>> On Mon May 19, 2025 at 6:16 PM CEST, Yao Zi wrote:
>>> All supported variants of naneng-combphy follow a register layout
>>> similar to the RK3568 variant with some exceptions of SoC-specific
>>> registers.
>>>
>>> Add RK3568 prefix for the common set of registers and the corresponding
>>> SoC prefix for SoC-specific registers, making usage of definitions clear
>>> and preparing for future COMBPHY variants with a different register
>>> layout.
>>>
>>> Signed-off-by: Yao Zi <ziyao@disroot.org>
>>> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>>> ---
>>> .../rockchip/phy-rockchip-naneng-combphy.c | 560 +++++++++---------
>>> 1 file changed, 288 insertions(+), 272 deletions(-)
>>>
>>> diff --git a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
>>> index ce91fb1d5167..1d1c7723584b 100644
>>> --- a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
>>> +++ b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
>>> @@ -21,78 +21,80 @@
>>> #define REF_CLOCK_100MHz (100 * HZ_PER_MHZ)
>>>
>>> /* COMBO PHY REG */
>>> <snip>
>>> -#define PHYREG33_PLL_KVCO_VALUE_RK3576 4
>>> +#define RK3568_PHYREG6 0x14
>>> +#define RK3568_PHYREG6_PLL_DIV_MASK GENMASK(7, 6)
>>> +#define RK3568_PHYREG6_PLL_DIV_SHIFT 6
>>> +#define RK3568_PHYREG6_PLL_DIV_2 1
>>> +
>>> +#define RK3568_PHYREG7 0x18
>>> +#define RK3568_PHYREG7_TX_RTERM_MASK GENMASK(7, 4)
>>> +#define RK3568_PHYREG7_TX_RTERM_SHIFT 4
>>> +#define RK3568_PHYREG7_TX_RTERM_50OHM 8
>>> +#define RK3568_PHYREG7_RX_RTERM_MASK GENMASK(3, 0)
>>> +#define RK3568_PHYREG7_RX_RTERM_SHIFT 0
>>> +#define RK3568_PHYREG7_RX_RTERM_44OHM 15
>>> +
>>> +#define RK3568_PHYREG8 0x1C
>>> +#define RK3568_PHYREG8_SSC_EN BIT(4)
>>> +
>>> +#define RK3568_PHYREG11 0x28
>>> +#define RK3568_PHYREG11_SU_TRIM_0_7 0xF0
>>> +
>>> +#define RK3568_PHYREG12 0x2C
>>> +#define RK3568_PHYREG12_PLL_LPF_ADJ_VALUE 4
>>> +
>>> +#define RK3568_PHYREG13 0x30
>>> +#define RK3568_PHYREG13_RESISTER_MASK GENMASK(5, 4)
>>> +#define RK3568_PHYREG13_RESISTER_SHIFT 0x4
>>> +#define RK3568_PHYREG13_RESISTER_HIGH_Z 3
>>> +#define RK3568_PHYREG13_CKRCV_AMP0 BIT(7)
>>> +
>>> +#define RK3568_PHYREG14 0x34
>>> +#define RK3568_PHYREG14_CKRCV_AMP1 BIT(0)
>>> +
>>> +#define RK3568_PHYREG15 0x38
>>> +#define RK3568_PHYREG15_CTLE_EN BIT(0)
>>> +#define RK3568_PHYREG15_SSC_CNT_MASK GENMASK(7, 6)
>>> +#define RK3568_PHYREG15_SSC_CNT_SHIFT 6
>>> +#define RK3568_PHYREG15_SSC_CNT_VALUE 1
>>> +
>>> +#define RK3568_PHYREG16 0x3C
>>> +#define RK3568_PHYREG16_SSC_CNT_VALUE 0x5f
>>> +
>>> +#define RK3568_PHYREG18 0x44
>>> +#define RK3568_PHYREG18_PLL_LOOP 0x32
>>> +
>>> +#define RK3568_PHYREG32 0x7C
>>> +#define RK3568_PHYREG32_SSC_MASK GENMASK(7, 4)
>>> +#define RK3568_PHYREG32_SSC_DIR_MASK GENMASK(5, 4)
>>> +#define RK3568_PHYREG32_SSC_DIR_SHIFT 4
>>> +#define RK3568_PHYREG32_SSC_UPWARD 0
>>> +#define RK3568_PHYREG32_SSC_DOWNWARD 1
>>> +#define RK3568_PHYREG32_SSC_OFFSET_MASK GENMASK(7, 6)
>>> +#define RK3568_PHYREG32_SSC_OFFSET_SHIFT 6
>>> +#define RK3568_PHYREG32_SSC_OFFSET_500PPM 1
>>> +
>>> +#define RK3568_PHYREG33 0x80
>>> +#define RK3568_PHYREG33_PLL_KVCO_MASK GENMASK(4, 2)
>>> +#define RK3568_PHYREG33_PLL_KVCO_SHIFT 2
>>> +#define RK3568_PHYREG33_PLL_KVCO_VALUE 2
>>> +#define RK3576_PHYREG33_PLL_KVCO_VALUE 4
>>> +
>>> +/* RK3588 COMBO PHY registers */
>>> +#define RK3588_PHYREG27 0x6C
>>> +#define RK3588_PHYREG27_RX_TRIM 0x4C
>>
>> Would it be better if RK3588_PHYREG* comes after RK3576_PHYREG*?
>>
>> Cheers,
>> Diederik
>
> It's intended to keep RK3576 definitions below RK3588 ones. The RK3576
> driver makes use of a register introduced for RK3588 variant
> (RK3588_PHYREG27). Since similar reusing doesn't happen reversely, I
> consider the design of RK3576 a superset of the RK3588 one, and put
> RK3576 definitions later in the file.
Sound logic, RK3576 was announced after RK3588, thus the order makes sense.
Add my:
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
>
>>> +
>>> +/* RK3576 COMBO PHY registers */
>>> +#define RK3576_PHYREG10 0x24
>>> +#define RK3576_PHYREG10_SSC_PCM_MASK GENMASK(3, 0)
>>> +#define RK3576_PHYREG10_SSC_PCM_3500PPM 7
>>> +
>>> +#define RK3576_PHYREG17 0x40
>>> +
>>> +#define RK3576_PHYREG21 0x50
>>> +#define RK3576_PHYREG21_RX_SQUELCH_VAL 0x0D
>>> +
>>> +#define RK3576_PHYREG30 0x74
>>>
>>> struct rockchip_combphy_priv;
>>> <snip>
>
>
> Thanks,
> Yao Zi
>
next prev parent reply other threads:[~2025-05-20 7:27 UTC|newest]
Thread overview: 16+ 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 ` [PATCH v3 1/5] dt-bindings: soc: rockchip: Add RK3528 pipe-phy GRF syscon 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: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 19:26 ` Diederik de Haas
2025-05-20 3:53 ` Yao Zi
2025-05-20 7:24 ` neil.armstrong [this message]
2025-05-20 8:37 ` Diederik de Haas
2025-05-20 11:12 ` Yao Zi
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-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-20 17:51 ` Jonas Karlman
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=ab2692a5-e428-40bf-8071-cad6ae96dc3b@linaro.org \
--to=neil.armstrong@linaro.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=didi.debian@cknow.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 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).