[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8476196b-3e15-40e9-8481-69e4548899eb@roeck-us.net>
Date: Fri, 2 Aug 2024 12:40:21 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Walleij <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 6.11-rc1
On 8/2/24 10:35, Linus Walleij wrote:
> On Mon, Jul 29, 2024 at 5:29 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
>> Failed tests:
>> arm:versatilepb:versatile_defconfig:aeabi:pci:scsi:mem128:net=default:versatile-pb:ext2
>> arm:versatilepb:versatile_defconfig:aeabi:pci:flash64:mem128:net=default:versatile-pb:ext2
>> arm:versatilepb:versatile_defconfig:aeabi:pci:mem128:net=default:versatile-pb:initrd
>> arm:versatileab:versatile_defconfig:mem128:net=default:versatile-ab:initrd
>
> I traced these fails down to:
> commit 04f08ef291d4b8d76f8d198bf2929ad43b96eecf
> "arm/arm64: dts: arm: Use generic clock and regulator nodenames"
>
> The following oneliner fixes it:
>
> diff --git a/arch/arm/boot/dts/arm/versatile-ab.dts
> b/arch/arm/boot/dts/arm/versatile-ab.dts
> index 6fe6b49f5d8e..289c3d093579 100644
> --- a/arch/arm/boot/dts/arm/versatile-ab.dts
> +++ b/arch/arm/boot/dts/arm/versatile-ab.dts
> @@ -157,7 +157,7 @@ timclk: clock-1000000 {
> clocks = <&xtal24mhz>;
> };
>
> - pclk: clock-24000000 {
> + pclk: pclk@24M {
> #clock-cells = <0>;
> compatible = "fixed-factor-clock";
> clock-div = <1>;
>
> (versatile-ab is included by versatile-pb hence it regresses)
>
> The problem is: I don't know why.
>
> Rob: any ideas? (Perhaps some uglyhack of mine, I don't know.)
>
Rob already sent a patch fixing the problem.
https://lore.kernel.org/r/20240730210030.2150467-2-robh@kernel.org
Guenter
Powered by blists - more mailing lists