[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174853867693.3632160.17627654159190851191.b4-ty@baylibre.com>
Date: Thu, 29 May 2025 10:11:16 -0700
From: Kevin Hilman <khilman@...libre.com>
To: s-vadapalli@...com, Frank Li <Frank.Li@....com>
Cc: bhelgaas@...gle.com, conor+dt@...nel.org, devicetree@...r.kernel.org,
krzk+dt@...nel.org, kw@...ux.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
linux-pci@...r.kernel.org, lpieralisi@...nel.org,
manivannan.sadhasivam@...aro.org, robh@...nel.org, tony@...mide.com,
vigneshr@...com
Subject: Re: [PATCH v2 1/1] Revert "ARM: dts: Update pcie ranges for dra7"
On Fri, 11 Apr 2025 11:34:54 -0400, Frank Li wrote:
> This reverts commit c761028ef5e27f477fe14d2b134164c584fc21ee.
>
> The commit being reverted updated the "ranges" property for the sake of
> readability. However, this change is no longer appropriate due to the
> following reasons:
>
> - On many SoCs, the PCIe parent bus translates CPU addresses to different
> values before passing them to the PCIe controller.
> - The reverted commit introduced a fake address translation, which violates
> the fundamental DTS principle: the device tree should reflect actual
> hardware behavior.
>
> [...]
Applied, thanks!
[1/1] Revert "ARM: dts: Update pcie ranges for dra7"
commit: 8c178057e734188eeeceaec33848eaca2766ca07
Best regards,
--
Kevin Hilman <khilman@...libre.com>
Powered by blists - more mailing lists