[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176094293138.11548.16893576609668956400.b4-ty@kernel.org>
Date: Mon, 20 Oct 2025 12:18:51 +0530
From: Manivannan Sadhasivam <mani@...nel.org>
To: linux-pci@...r.kernel.org, Nicolas Saenz Julienne <nsaenz@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, bcm-kernel-feedback-list@...adcom.com,
jim2101024@...il.com, Lorenzo Pieralisi <lpieralisi@...nel.org>,
Jim Quinlan <james.quinlan@...adcom.com>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Rob Herring <robh@...nel.org>, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI: brcmstb: Fix use of incorrect constant
On Fri, 03 Oct 2025 13:04:36 -0400, Jim Quinlan wrote:
> The driver was using the PCIE_LINK_STATE_L1 constant as a field mask for
> setting the private PCI_EXP_LNKCAP register, but this constant is
> Linux-created and has nothing to do with the PCIe spec. Serendipitously,
> the value of this constant was correct for its usage until after 6.1, when
> its value changed from BIT(1) to BIT(2);
>
> In addition, the driver was assuming that the HW is ASPM L1 capable when it
> should not be telling the HW what it is capable of.
>
> [...]
Applied, thanks!
[1/1] PCI: brcmstb: Fix use of incorrect constant
commit: ad6014f77f6b66e862a912b5aa4571d00ab30405
Best regards,
--
Manivannan Sadhasivam <mani@...nel.org>
Powered by blists - more mailing lists