[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d08f6f17-f90c-4d71-a203-1d5365b5598a@linaro.org>
Date: Mon, 25 Sep 2023 08:57:49 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Patrice CHOTARD <patrice.chotard@...s.st.com>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH v2 4/4] ARM: dts: st: stih407: drop max-duty-cycle
On 25/09/2023 08:50, Patrice CHOTARD wrote:
>
>
> On 9/24/23 20:53, Krzysztof Kozlowski wrote:
>> On 16/08/2023 08:54, Patrice CHOTARD wrote:
>>>
>>>
>>> On 7/30/23 19:49, Krzysztof Kozlowski wrote:
>>>> "max-duty-cycle" property was removed in the commit f747a1fe7848
>>>> ("regulator: pwm-regulator: Remove obsoleted property"):
>>>>
>>>> stih418-b2199.dtb: pwm-regulator: Unevaluated properties are not allowed ('max-duty-cycle' was unexpected)
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>>>
>>>> ---
>>>>
>>>> Changes in v2:
>>>> 1. Correct subject prefix: AMR->ARM
>>>> ---
>>>> arch/arm/boot/dts/st/stih407-family.dtsi | 1 -
>>>> 1 file changed, 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm/boot/dts/st/stih407-family.dtsi b/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> index 3f58383a7b59..29302e74aa1d 100644
>>>> --- a/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> +++ b/arch/arm/boot/dts/st/stih407-family.dtsi
>>>> @@ -111,7 +111,6 @@ pwm_regulator: pwm-regulator {
>>>> regulator-min-microvolt = <784000>;
>>>> regulator-max-microvolt = <1299000>;
>>>> regulator-always-on;
>>>> - max-duty-cycle = <255>;
>>>> status = "okay";
>>>> };
>>>>
>>>
>>>
>>> Applied on sti-next
>>
>> This is still not in linux-next (one month later!).
>
> Hi Krzysztof
>
> Yes i saw that, i submitted my pull request to ML but it hasn't be merged.
> I just notice i forgot to add soc@...nel.org in the sender list, my bad :-(
> I expect to resubmit it for v6.7.
So if you have them in your tree, why they are not in linux-next? Soc
has nothing to do with it.
Best regards,
Krzysztof
Powered by blists - more mailing lists