[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79ecad6e-d9c9-c798-0933-43da4dff9dd6@canonical.com>
Date: Mon, 14 Feb 2022 17:54:01 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Mark Brown <broonie@...nel.org>
Cc: Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
Sebastian Reichel <sre@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH v2 3/4] regulator: dt-bindings: maxim,max14577: convert to
dtschema
On 14/02/2022 17:43, Mark Brown wrote:
> On Tue, Jan 11, 2022 at 06:43:36PM +0100, Krzysztof Kozlowski wrote:
>
>> + required:
>> + - regulator-name
>
> Why is regulator-name required? While it's a good idea for users to
> document names for supplies on their boards it shouldn't be a
> requirement or something that a driver would care about.
Indeed, there is no need for requiring the name. I guess I copied it
from other schemas.
I think this was not applied yet, so I'll send a v3.
Best regards,
Krzysztof
Powered by blists - more mailing lists