All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: 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, 19 May 2026 16:18:40 +0530	[thread overview]
Message-ID: <177918772002.269794.4450351142089498526.b4-ty@kernel.org> (raw)
In-Reply-To: <1777251433-110466-1-git-send-email-shawn.lin@rock-chips.com>


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

Best regards,
-- 
~Vinod



-- 
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: Vinod Koul <vkoul@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: 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, 19 May 2026 16:18:40 +0530	[thread overview]
Message-ID: <177918772002.269794.4450351142089498526.b4-ty@kernel.org> (raw)
In-Reply-To: <1777251433-110466-1-git-send-email-shawn.lin@rock-chips.com>


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

Best regards,
-- 
~Vinod



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

  parent reply	other threads:[~2026-05-19 10:48 UTC|newest]

Thread overview: 12+ 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-04-27  0:57 ` Shawn Lin
2026-05-10 11:01 ` Vinod Koul
2026-05-10 11:01   ` Vinod Koul
2026-05-19 10:48 ` Vinod Koul [this message]
2026-05-19 10:48   ` Vinod Koul
2026-07-14 12:58   ` Alexey Charkov
2026-07-14 12:58     ` Alexey Charkov
2026-07-14 13:42     ` Vinod Koul
2026-07-14 13:42       ` Vinod Koul
2026-07-14 13:52       ` Alexey Charkov
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=177918772002.269794.4450351142089498526.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --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 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.