Re: [PATCH 1/1] Revert "ARM: dts: Update pcie ranges for dra7"

[Siddharth Vadapalli]

On Wed, Apr 09, 2025 at 11:35:18AM -0400, Frank Li wrote:

Hello Frank,

> This reverts commit c761028ef5e27f477fe14d2b134164c584fc21ee.
> 
> The previous device tree correctly reflects the hardware behavior.
> The reverted commit introduced a fake address translation at pcie's parent
> bus node.

More details are required in the commit message. The commit being
reverted states:

"The range for 0 is typically used for child devices as the offset from the
module base. In the following patches, we will update pcie to probe with
ti-sysc, and the patches become a bit confusing to read compared to other
similar modules unless we update the ranges first. So let's just use the
full addresses for ranges for the 0x20000000 and 0x30000000 ranges."

The commit message in this patch should probably indicate something
along the lines of:
The commit being reverted updated the "ranges" property for the sake of
readability but that is no longer required because <your reason here>.

Tony Lindgren is the author of the commit being reverted. Tony could
clarify if the purpose of the commit was more than just improving
readability.

> 
> Reverting this change prepares for the cleanup of the driver's
> cpu_addr_fixup() hook.
> 
> Signed-off-by: Frank Li <Frank.Li@xxxxxxx>
> ---
> Previous disscusion at
> https://lore.kernel.org/linux-pci/20250314064642.fyf3jqylmc6meft7@uda0492258/
> ---
>  arch/arm/boot/dts/ti/omap/dra7.dtsi | 29 +++++++++++------------------
>  1 file changed, 11 insertions(+), 18 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/ti/omap/dra7.dtsi b/arch/arm/boot/dts/ti/omap/dra7.dtsi
> index b709703f6c0d4..711ce4c31bb1f 100644
> --- a/arch/arm/boot/dts/ti/omap/dra7.dtsi
> +++ b/arch/arm/boot/dts/ti/omap/dra7.dtsi
> @@ -195,24 +195,22 @@ axi0: target-module@51000000 {
>  			clock-names = "fck", "phy-clk", "phy-clk-div";
>  			#size-cells = <1>;
>  			#address-cells = <1>;
> -			ranges = <0x51000000 0x51000000 0x3000>,
> -				 <0x20000000 0x20000000 0x10000000>;
> +			ranges = <0x51000000 0x51000000 0x3000
> +				  0x0	     0x20000000 0x10000000>;
>  			dma-ranges;

[...]

Regards,
Siddharth.