[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJNgxLgvB502Bk=5aMeP2rY6KVL_FykeSyN1tsDRXi9cA@mail.gmail.com>
Date: Tue, 14 Jan 2025 13:19:16 -0600
From: Rob Herring <robh@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, Len Brown <lenb@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Danilo Krummrich <dakr@...nel.org>,
Saravana Kannan <saravanak@...gle.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH 2/2] of: Warn when of_property_read_bool() is used on
non-boolean properties
On Tue, Jan 14, 2025 at 12:35 PM Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
>
> Hi Rob,
>
> On Thu, Jan 9, 2025 at 8:42 PM Rob Herring (Arm) <robh@...nel.org> wrote:
> > The use of of_property_read_bool() for non-boolean properties is
> > deprecated. The primary use of it was to test property presence, but
> > that has been replaced in favor of of_property_present(). With those
> > uses now fixed, add a warning to discourage new ones.
> >
> > Signed-off-by: Rob Herring (Arm) <robh@...nel.org>
>
> Thanks for your patch, which is now commit c141ecc3cecd7647 ("of:
> Warn when of_property_read_bool() is used on non-boolean properties")
> in dt-rh/for-next.
>
> I have bisected a failure in secondary CPU bring-up on R-Car H1 (quad
> Cortex-A9 MPCore) to this commit:
>
> Detected Renesas R-Car Gen1 r8a7779 ES1.0
> smp: Bringing up secondary CPUs ...
> -CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
> -CPU1: Spectre v2: using BPIALL workaround
> -CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
> -CPU2: Spectre v2: using BPIALL workaround
> -CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
> -CPU3: Spectre v2: using BPIALL workaround
> -smp: Brought up 1 node, 4 CPUs
> -SMP: Total of 4 processors activated (2000.00 BogoMIPS).
> +CPU1: failed to come online
> +CPU2: failed to come online
> +CPU3: failed to come online
> +smp: Brought up 1 node, 1 CPU
> +SMP: Total of 1 processors activated (500.00 BogoMIPS).
> CPU: All CPU(s) started in SVC mode.
>
> Reverting this commit on top of my work tree fixes the issue, too.
> However, I do not see how this commit could impact CPU bring-up?
Strange. Perhaps the of_property_read_bool was inlined into some
special section before?
Rob
Powered by blists - more mailing lists