From: ivaylo <ivo.ivanov.ivanov1@gmail.com>
To: Xu Yang <xu.yang_2@oss.nxp.com>,
vkoul@kernel.org, neil.armstrong@linaro.org, mani@kernel.org,
dmitry.baryshkov@oss.qualcomm.com
Cc: linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH] phy: phy-snps-eusb2: fix FSEL_48_MHZ_VAL definition
Date: Tue, 8 Sep 2026 16:17:57 +0400 [thread overview]
Message-ID: <aaf8a5ef-2abe-4269-804e-4d2dd1bc4d3e@gmail.com> (raw)
In-Reply-To: <20260908085953.3315953-1-xu.yang_2@oss.nxp.com>
On 8.09.26 12:59, Xu Yang wrote:
> From: Xu Yang <xu.yang_2@nxp.com>
>
> According to Synopsys eUSB2 PHY Databook, FSEL_48_MHZ_VAL should be 0x6
> for supported 48 MHz reference clock.
I don't see this as a justified change. Samsung's implementation of eUSB2
differs from the generic Synopsys interface, as is visible from the
differences
between QCOM's implementation and Samsung's.
From what I see for exynos2200, the FSEL value is 0x2 for both 24 MHz and
48 MHz. The differentiating part is that the upper PLL divider is 0x0
for 24 MHz
and 0x1 for 48 MHz. The current programming was taken from the samsung
vendor kernel driver, which is a reliable-ish reference for the
differences in register
interface implementation when we have no other public resource like a
manual.
..now that I look into it though, the 11_8 value should probably be
field_prep'd
instead of just directly passed as an argument of
snps_eusb2_hsphy_write_mask(),
because right now it's essentially 0x1 & 0xf00 = 0? I haven't tested
this path on
my hardware, so it might prove to be a regression in the future?
So:
snps_eusb2_hsphy_write_mask(phy->base, EXYNOS_USB_PHY_CFG_PLLCFG1,
EXYNOS_PHY_CFG_PLL_FB_DIV_11_8_MASK,
FIELD_PREP(EXYNOS_PHY_CFG_PLL_FB_DIV_11_8_MASK, config->div_11_8_val));
For this patch though, unless this change is tested on real hardware and
backed up
by a technical reference manual for this particular implementation,
CC-ing the
change to stable is unreasonable.
Best regards,
Ivaylo Ivanov
>
> Fixes: c4098f3e6134 ("phy: phy-snps-eusb2: add support for exynos2200")
> Cc: stable@vger.kernel.org
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> ---
> drivers/phy/phy-snps-eusb2.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/phy-snps-eusb2.c b/drivers/phy/phy-snps-eusb2.c
> index af4fa17ac6cb..3cb18d6ebc1d 100644
> --- a/drivers/phy/phy-snps-eusb2.c
> +++ b/drivers/phy/phy-snps-eusb2.c
> @@ -21,7 +21,7 @@
> #define FSEL_20_MHZ_VAL (0x1)
> #define FSEL_24_MHZ_VAL (0x2)
> #define FSEL_26_MHZ_VAL (0x3)
> -#define FSEL_48_MHZ_VAL (0x2)
> +#define FSEL_48_MHZ_VAL (0x6)
>
> #define EXYNOS_USB_PHY_CFG_PLLCFG0 (0x8)
> #define PHY_CFG_PLL_FB_DIV_19_8_MASK GENMASK(19, 8)
next prev parent reply other threads:[~2026-09-08 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 8:59 Xu Yang
2026-09-08 12:17 ` ivaylo [this message]
2026-09-09 2:49 ` Xu Yang
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=aaf8a5ef-2abe-4269-804e-4d2dd1bc4d3e@gmail.com \
--to=ivo.ivanov.ivanov1@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=vkoul@kernel.org \
--cc=xu.yang_2@oss.nxp.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®