linux-kernel - Re: [PATCH] arm64: dts: rockchip: rk3399-gru: Fix PCI node addresses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <170173468936.501889.14178301756278206830.b4-ty@sntech.de>
Date:   Tue,  5 Dec 2023 01:06:00 +0100
From:   Heiko Stuebner <heiko@...ech.de>
To:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc:     Heiko Stuebner <heiko@...ech.de>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: rk3399-gru: Fix PCI node addresses

On Thu, 30 Nov 2023 13:18:29 -0600, Rob Herring wrote:
> The rk3399-gru PCI node addresses are wrong.
> 
> In rk3399-gru-scarlet, the bus number in the address should be 0. This is
> because bus number assignment is dynamic and not known up front. For FDT,
> the bus number is simply ignored.
> 
> In rk3399-gru-chromebook, the addresses are simply invalid. The first
> "reg" entry must be the configuration space for the device. The entry
> should be all 0s except for device/slot and function numbers. The existing
> 64-bit memory space (0x83000000) entries are not valid because they must
> have the BAR address in the lower byte of the first cell.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: rockchip: rk3399-gru: Fix PCI node addresses
      commit: c13c823a78b77ea0e5f1f73112d910e259911101

Best regards,
-- 
Heiko Stuebner <heiko@...ech.de>