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@xxxxxxxxxx>
>>>
>>> ---
>>>
>>> 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@xxxxxxxxxx in the sender list, my bad :-(
I expect to resubmit it for v6.7.
Patrice
>
> I don't know what happened here, maybe patch got lost (thus let me know
> if I am expect to apply it, which should not be the norm, but meh...).
> If it is not the case and for example your tree is not in next, then
> maybe this will be of use:
> https://social.kernel.org/notice/Aa2Gbxj4cyyuUb0P8S
> https://lpc.events/event/17/contributions/1498/
>
> :)
>
> Best regards,
> Krzysztof
>
