[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <171691641513.1016774.9157485411952411160.robh@kernel.org>
Date: Tue, 28 May 2024 12:14:44 -0500
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Saravana Kannan <saravanak@...gle.com>,
Anup Patel <apatel@...tanamicro.com>
Subject: Re: [PATCH] of: property: Fix fw_devlink handling of interrupt-map
On Tue, 28 May 2024 17:41:32 +0100, Marc Zyngier wrote:
> Commit d976c6f4b32c ("of: property: Add fw_devlink support for
> interrupt-map property") tried to do what it says on the tin,
> but failed on a couple of points:
>
> - it confuses bytes and cells. Not a huge deal, except when it
> comes to pointer arithmetic
>
> - it doesn't really handle anything but interrupt-maps that have
> their parent #address-cells set to 0
>
> The combinations of the two leads to some serious fun on my M1
> box, with plenty of WARN-ON() firing all over the shop, and
> amusing values being generated for interrupt specifiers.
>
> Address both issues so that I can boot my machines again.
>
> Fixes: d976c6f4b32c ("of: property: Add fw_devlink support for interrupt-map property")
> Signed-off-by: Marc Zyngier <maz@...nel.org>
> Cc: Anup Patel <apatel@...tanamicro.com>
> Cc: Saravana Kannan <saravanak@...gle.com>
> Cc: Rob Herring (Arm) <robh@...nel.org>
> ---
> drivers/of/property.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
Applied, thanks!
Powered by blists - more mailing lists