[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJAQswTo2eWxLw62wqb-2i=_9W84_v_tW+TSW4kgNK3_A@mail.gmail.com>
Date: Tue, 12 Nov 2024 07:46:09 -0600
From: Rob Herring <robh@...nel.org>
To: Josua Mayer <josua@...id-run.com>
Cc: Saravana Kannan <saravanak@...gle.com>, Nishanth Menon <nm@...com>,
Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Geert Uytterhoeven <geert@...ux-m68k.org>, Jon Nettleton <jon@...id-run.com>,
Yazan Shhady <yazan.shhady@...id-run.com>, rabeeh@...id-run.com
Subject: Re: [PATCH 0/2] of: add support for value "false" to of_property_read_bool
On Tue, Nov 12, 2024 at 12:41 AM Josua Mayer <josua@...id-run.com> wrote:
>
> Boolean type properties are usually considered true if present and false
> when they do not exist. This works well for many in-tree board dts and
> existing drivers.
>
> When users need to overrride boolean values from included dts,
> /delete-property/ is recommend. This however does not work in overlays
> (addons).
As soon as someone needs to delete a non-boolean property, we're back
to the same problem. If you want to fix it, you need to fix it for any
property.
> Geert pointed out [1] that there are several invitations for using
> strings "true" and "false" on boolean properties: [1], [2], [3].
There's always bad examples...
> Add support for a string value "false" to be considered false on boolean
> properties by changing of_property_read_bool implementation.
Any existing s/w will treat 'foo = "false"' as true. It's an ABI.
Rob
Powered by blists - more mailing lists