[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <453ecc3d-c585-4665-bda1-b12ffa8d6967@linaro.org>
Date: Tue, 2 Apr 2024 14:07:12 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Andrei.Simion@...rochip.com, robh@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...on.dev, Mihai.Sain@...rochip.com
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] ARM: boot: dts: microchip: at91-sama7g5ek: Replace
regulator-suspend-voltage with the valid property
On 02/04/2024 13:27, Andrei.Simion@...rochip.com wrote:
> On 02.04.2024 13:39, Krzysztof Kozlowski wrote:
>> [You don't often get email from krzysztof.kozlowski@...aro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>>
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 02/04/2024 11:12, Andrei Simion wrote:
>>> Replace regulator-suspend-voltage with regulator-suspend-microvolt.
>>
>> Why?
>>
>
> at91-sama7g5ek.dtb: mcp16502@5b: regulators:VDD_(CORE|OTHER)|LDO[1-2]:
> regulator-state-standby 'regulator-suspend-voltage' does not match any of
> the regexes 'pinctrl-[0-9]+' from schema
> $id: http://devicetree.org/schemas/regulator/microchip,mcp16502.yaml#
>
> no property named regulator-suspend-voltage in
> https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/regulator/regulator.yaml
> so if it is using this property there will be no effect as it was expected in
> https://github.com/torvalds/linux/commit/85b1304b9daa06367139b471789c7ddb76250b9f
>
>> Please explain what is the bug and how it manifests itself. Is one
>> property incorrect and other correct?
>>
> The main reason is explained in the cover-letter but if you ask me to explain in each commit I will do it in next version.
Cover letter does not go to commit history. Each commit should explain
why you are doing it. Usually piece of the warning is quite
self-explanatory, thus one easy way to achieve the point - answer why.
Best regards,
Krzysztof
Powered by blists - more mailing lists