On 25/02/2025 17:09, Clement LE GOFFIC wrote:
> On 2/25/25 14:05, Krzysztof Kozlowski wrote:
>> On 25/02/2025 09:48, Clément Le Goffic wrote:
>>> Add the hdp devicetree node for stm32mp25 SoC family
>>>
>>> Signed-off-by: Clément Le Goffic <clement.legoffic@xxxxxxxxxxx>
>>> ---
>>> arch/arm64/boot/dts/st/stm32mp251.dtsi | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
>>> index f3c6cdfd7008..43aaed4fcf10 100644
>>> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
>>> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
>>> @@ -918,6 +918,13 @@ package_otp@1e8 {
>>> };
>>> };
>>>
>>> + hdp: pinctrl@44090000 {
>>> + compatible = "st,stm32mp-hdp";
>>
>> So here again - you have stm32mp251 SoC, but use entirely different
>> compatible.
>
> Ok so I will use "st,stm32mp15-hdp"
This means this is stm32mp15 SoC. I do not see such SoC on list of your
SoCs in bindings. What's more, there are no bindings for other SoC
components for stm32mp15!
Something is here not matching - this change, this DTSI, top level
bindings or all of your SoC device/blocks bindings.
Best regards,
Krzysztof
