On 16/01/2023 09:27, Ahmad Fatoum wrote:
> Hello Krzysztof,
>
> On 16.01.23 09:20, Krzysztof Kozlowski wrote:
>> On 13/01/2023 18:32, Bastian Krause wrote:
>>> The actual syscon-reboot-mode child node can be added by a board
>>> device-tree or fixed up by the bootloader. For the child node to be
>>> probed, the compatible needs to include simple-mfd. The binding now
>>> specifies this, so have the SoC dtsi adhere to it.
>>>
>>> Suggested-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
>>> Signed-off-by: Bastian Krause <bst@xxxxxxxxxxxxxx>
>>> ---
>>> arch/arm/boot/dts/imx6qdl.dtsi | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
>>> index ff1e0173b39be..b16be39458aa6 100644
>>> --- a/arch/arm/boot/dts/imx6qdl.dtsi
>>> +++ b/arch/arm/boot/dts/imx6qdl.dtsi
>>> @@ -865,7 +865,8 @@ epit2: epit@20d4000 { /* EPIT2 */
>>> };
>>>
>>> src: reset-controller@20d8000 {
>>> - compatible = "fsl,imx6q-src", "fsl,imx51-src";
>>> + compatible = "fsl,imx6q-src", "fsl,imx51-src",
>>> + "syscon", "simple-mfd";
>>
>> You need children here. Otherwise simple-mfd does not make sense. If you
>> expect something else to add children (I don't understand why, usually
>> reboot capability is fixed per SoC and only sometimes extended with some
>> other means), then this "else" will also change compatible.
>
> It's about syscon-reboot-mode, not syscon-reboot. Such modes are board-
> not soc-specific.
syscon-reboot-mode is also mostly SoC specific. What exactly would
differ on different boards? Register offsets of SoC component? Register
values used by SoC power management unit?
Anyway, the binding is then not correct - it does not allow
syscon-reboot-mode child. I'll comment there.
Best regards,
Krzysztof
