[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aFWqB8YRtYlC0vGG@geday>
Date: Fri, 20 Jun 2025 15:35:51 -0300
From: Geraldo Nascimento <geraldogabriel@...il.com>
To: Robin Murphy <robin.murphy@....com>
Cc: linux-rockchip@...ts.infradead.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: [RFC PATCH v5 4/4] phy: rockchip-pcie: Adjust read mask and write
On Fri, Jun 20, 2025 at 03:19:06PM +0100, Robin Murphy wrote:
> Which write mask? Certainly not PHY_CFG_WR_MASK... However as this
> definition is unused since 64cdc0360811 ("phy: rockchip-pcie: remove
> unused phy_rd_cfg function"), I don't see much point in touching it
> other than to remove it entirely. If it is the case that only the
> address field is significant for whatever a "read" operation actually
> means, well then that's just another job for ADDR_MASK (which I guess is
> what the open-coded business with PHY_CFG_PLL_LOCK is actually doing...)
Just for the sake of posterity, Robin is right here, PHY_CFG_WR_MASK is
just hardcoded to 1, and PHY_CFG_RD_MASK should have been the same
as PHY_CFG_ADDR_MASK as Robin correctly pointed out.
Moot point since I already agreed with Bjorn and Robin to drop the read
define, and Robin was kind enough to track the exact commit where the
corresponding read function was removed. I re-injected that function
from BSP into mainline for my own debugging though, that's why I caught
the typo.
Thanks,
Geraldo Nascimento
>
> Thanks,
> Robin.
Powered by blists - more mailing lists