[Linux-stm32] [PATCH v3 2/3] dt-bindings: arm: stm32: allow TAMP nvram child node for syscon

Patrice CHOTARD patrice.chotard at foss.st.com
Thu Nov 5 11:31:07 CET 2026



On 11/5/26 09:17, Krzysztof Kozlowski wrote:
> On 04/11/2026 14:43, Patrice CHOTARD wrote:
>>
>>
>> On 10/17/26 19:52, Krzysztof Kozlowski wrote:
>>> On Fri, Oct 16, 2026 at 05:26:04PM +0200, Patrice Chotard wrote:
>>>> The STM32 TAMP node (compatible "st,stm32-tamp", "syscon", "simple-mfd")
>>>> exposes its backup registers through an nvram child node described by
>>>> nvmem/st,stm32-tamp-nvram.yaml. That requires the TAMP node to carry
>>>> "#address-cells", "#size-cells", "ranges" and an "nvram at ..." child.
>>>>
>>>> st,stm32-syscon.yaml uses "additionalProperties: false" and only allowed
>>>> reg/clocks/#clock-cells, so wiring the nvram provider into the DTSI made
>>>> "make dtbs_check" fail on every STM32MP TAMP node:
>>>>
>>>>   tamp at 5c00a000 (st,stm32-tamp): '#address-cells', '#size-cells',
>>>>   'nvram at 5c00a100', 'ranges' do not match any of the regexes:
>>>>   '^pinctrl-[0-9]+$'
>>>
>>> There are no children of tamp at 5c00a000 in
>>> arch/arm/boot/dts/st/stm32mp151.dtsi. How is it possible to reproduce
>>> this warning?
>>>
>>> Are you using some other patches bugs as a reason of change in bindings?
>>
>> Hi Krzysztof
>>
>> yes, in this patch [1] arch/arm/boot/dts/st/stm32mp151.dtsi is updated
>> that's why bindings need this change.
> 
> You cannot use future code as a bug being fixed.

Ok, so i will merge this series with https://patchwork.kernel.org/series/1176665/

Thanks
Patrice

> 
> 
> Best regards,
> Krzysztof



More information about the Linux-stm32 mailing list