linux-kernel - Re: [PATCH] ARM: dts: broadcom: bcm2166x-common: Increase apps bus size to fit BCM21664 GIC

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <96dd8762-7cfa-4b9b-84ee-592fe0a59af1@broadcom.com>
Date: Tue, 20 Aug 2024 11:50:25 -0700
From: Florian Fainelli <florian.fainelli@...adcom.com>
To: Florian Fainelli <florian.fainelli@...adcom.com>,
 bcm-kernel-feedback-list@...adcom.com, Artur Weber
 <aweber.kernel@...il.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Ray Jui <rjui@...adcom.com>,
 Scott Branden <sbranden@...adcom.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH] ARM: dts: broadcom: bcm2166x-common: Increase apps bus
 size to fit BCM21664 GIC

On 8/20/24 11:49, Florian Fainelli wrote:
> From: Florian Fainelli <f.fainelli@...il.com>
> 
> On Tue, 20 Aug 2024 16:38:14 +0200, Artur Weber <aweber.kernel@...il.com> wrote:
>> The BCM21664 GIC sits at a higher address than the apps bus currently
>> allows. This is because the apps bus was inherited from the BCM23550
>> DTSI, where the GIC sits at an earlier address in memory, and the DTSI
>> wasn't updated to match.
>>
>> Increase the size of the apps bus to allow the BCM21664 GIC to work.
>>
>> Fixes: a5d0d4a7bab5 ("ARM: dts: bcm-mobile: Split out nodes used by both BCM21664 and BCM23550")
>> Signed-off-by: Artur Weber <aweber.kernel@...il.com>
>> ---
> 
> Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!

Since this was only a problem in linux-next, I just squashed your fixup 
within the original commit. Thanks!
-- 
Florian