Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Alexey Charkov <alchark@flipper.net>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	linux-rockchip@lists.infradead.org,
	linux-phy@lists.infradead.org, Heiko Stuebner <heiko@sntech.de>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v3] phy: rockchip: naneng-combphy: Consolidate SSC configuration
Date: Tue, 14 Jul 2026 19:12:35 +0530	[thread overview]
Message-ID: <alY8y15JA0T5hoaY@vaman> (raw)
In-Reply-To: <CAKTNdwH_ZMQa-97h+tqdsWqXKtorkFF9wHAMn60-8ZGKuze_Mg@mail.gmail.com>

On 14-07-26, 16:58, Alexey Charkov wrote:
> On Tue, May 19, 2026 at 2:48 PM Vinod Koul <vkoul@kernel.org> wrote:
> >
> >
> > On Mon, 27 Apr 2026 08:57:13 +0800, Shawn Lin wrote:
> > > The PCIe SSC configuration for the RK3588 and RK3576 SoCs required
> > > additional tuning which is missing. When adding these same SSC
> > > configurations for both of these two SoCs, as well as upcoming
> > > platforms, it's obvious the SSC setup code was largely duplicated
> > > across the platform-specific configuration functions. This becomes
> > > harder to maintain as more platforms are added.
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/1] phy: rockchip: naneng-combphy: Consolidate SSC configuration
> >       commit: 0b31f297557fff0941769e8257198151a0fbe8bf
> 
> This commit breaks USB3 operation on RK3576 (at least in host mode),
> causing an endless flood of messages like this every second in dmesg:
> 
> usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
> 
> USB 2.0 part enumerates, but USB 3.0 doesn't. Tested on two different
> devices having a CoreChips SL6341 USB 2.0/USB 3.0 hub onboard
> connected to &usb_drd1_dwc3, bisected to this commit.
> 
> Has this been reported yet, or shall I investigate further which part
> of the patch causes the breakage?

First I heard, would be good to investigate.
I can revert if we dont find a fix soon...

> 
> Best regards,
> Alexey
> ---
> 0b31f297557fff0941769e8257198151a0fbe8bf is the first bad commit
> commit 0b31f297557fff0941769e8257198151a0fbe8bf
> Author: Shawn Lin <shawn.lin@rock-chips.com>
> Date:   Mon Apr 27 08:57:13 2026 +0800
> 
>     phy: rockchip: naneng-combphy: Consolidate SSC configuration
> 
>     The PCIe SSC configuration for the RK3588 and RK3576 SoCs required
>     additional tuning which is missing. When adding these same SSC
>     configurations for both of these two SoCs, as well as upcoming
>     platforms, it's obvious the SSC setup code was largely duplicated
>     across the platform-specific configuration functions. This becomes
>     harder to maintain as more platforms are added.
> 
>     So extract the common SSC logic into a shared helper function,
>     rk_combphy_common_cfg_ssc(). This cleans up the per-platform drivers
>     and centralizes the standard configuration as possible.
> 
>     Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
>     Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>     Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>     Link: https://patch.msgid.link/1777251433-110466-1-git-send-email-shawn.lin@rock-chips.com
>     Signed-off-by: Vinod Koul <vkoul@kernel.org>
> 
>  drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 173
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------------------------
>  1 file changed, 73 insertions(+), 100 deletions(-)

-- 
~Vinod

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-07-14 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  0:57 [PATCH v3] phy: rockchip: naneng-combphy: Consolidate SSC configuration Shawn Lin
2026-05-10 11:01 ` Vinod Koul
2026-05-19 10:48 ` Vinod Koul
2026-07-14 12:58   ` Alexey Charkov
2026-07-14 13:42     ` Vinod Koul [this message]
2026-07-14 13:52       ` Alexey Charkov

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=alY8y15JA0T5hoaY@vaman \
    --to=vkoul@kernel.org \
    --cc=alchark@flipper.net \
    --cc=heiko@sntech.de \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=shawn.lin@rock-chips.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