[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aH5UHPAtAVb2snSK@geday>
Date: Mon, 21 Jul 2025 11:52:12 -0300
From: Geraldo Nascimento <geraldogabriel@...il.com>
To: Robin Murphy <robin.murphy@....com>
Cc: linux-rockchip@...ts.infradead.org,
Neil Armstrong <neil.armstrong@...aro.org>,
Shawn Lin <shawn.lin@...k-chips.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kw@...ux.com>,
Manivannan Sadhasivam <mani@...nel.org>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
Heiko Stuebner <heiko@...ech.de>, Vinod Koul <vkoul@...nel.org>,
Kishon Vijay Abraham I <kishon@...nel.org>,
Rick wertenbroek <rick.wertenbroek@...il.com>,
linux-phy@...ts.infradead.org, linux-pci@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 3/4] phy: rockchip-pcie: Enable all four lanes if
required
On Mon, Jun 30, 2025 at 02:48:25PM +0100, Robin Murphy wrote:
> On 29/06/2025 9:58 pm, Geraldo Nascimento wrote:
> > Current code enables only Lane 0 because pwr_cnt will be incremented on
> > first call to the function. Let's reorder the enablement code to enable
> > all 4 lanes through GRF.
>
> As usual the TRM isn't very clear, but the way it describes the
> GRF_SOC_CON_5_PCIE bits does suggest they're driving external input
> signals of the phy block, so it seems reasonable that it could be OK to
> update the register itself without worrying about releasing the phy from
> reset first. In that case I'd agree this seems the cleanest fix, and if
> it works empirically then I think I'm now sufficiently convinced too;
>
> Reviewed-by: Robin Murphy <robin.murphy@....com>
Hi everyone,
Patches 1 and 2 of this series were merged thhrough pci git but patches
3 and 4 of present series got R-b's but were completely ignored by phy
maintainers.
Do you think it's fair if I resend these ones with a new, phy only, cover
letter but keep the R-b tags?
Thank you,
Geraldo Nascimento
Powered by blists - more mailing lists