[Linux-stm32] [PATCH 00/11] Rework and fix STM32MP15x PHYTEC dts

[Alexandre TORGUE]

Hi Christophe

On 2/27/25 12:35, Christophe Parant wrote:
> Hi Alexandre,
> 
> Le jeudi 27 février 2025 à 09:52 +0100, Alexandre TORGUE a écrit :
>> Hi Christophe
>>
>> On 1/10/25 16:02, Christophe Parant wrote:
>>> This patch series rename and reorganize the STM32MP15x PHYTEC
>>> baseboard (phyBOARD-Sargas) and SoM (phyCORE-STM32MP15x) device
>>> tree
>>> files.
>>> Indeed, the current device tree naming and organization is not
>>> really
>>> consistent as it does not align with others STM32MP boards (use
>>> common
>>> dtsi file as much as possible, use one dtsi for SoM and one dtsi
>>> for
>>> baseboard).
>>>
>>> The series also fixes some important pinctrl issues and minor one
>>> (coding
>>> style). Additional pinctrl is also added for the optionnal
>>> interfaces
>>> that are not enabled by default (FMC, LTDC, DCMI, PWM).
>>>
>>> Christophe Parant (11):
>>>     ARM: dts: stm32mp15: phycore: Rename device tree files
>>>     ARM: dts: stm32mp15: phyboard-sargas: Introduce SoM device tree
>>>     dt-bindings: arm: stm32: Rename STM32MP15x Phytec board and SoM
>>>     ARM: dts: stm32mp15: Add new pinmux groups for phycore and
>>> phyboard
>>>     ARM: dts: stm32mp15: phyboard-sargas: Fix uart4 and sai2 pinctrl
>>>     ARM: dts: stm32mp15: phycore: qspi: Fix memory map and pinctrl
>>>     ARM: dts: stm32mp15: phycore: Add dummy memory-node
>>>     ARM: dts: stm32mp15: phyboard-sargas: Move aliases from dts to
>>> dtsi
>>>     ARM: dts: stm32mp15: phycore: Disable optional SoM peripherals
>>>     ARM: dts: stm32mp15: phycore and phyboard: Fix coding style
>>> issues
>>>     ARM: dts: stm32mp15: phycore and phyboard: Add optional
>>> interfaces
>>>
>>>    .../devicetree/bindings/arm/stm32/stm32.yaml  |   7 +-
>>>    arch/arm/boot/dts/st/Makefile                 |   2 +-
>>>    arch/arm/boot/dts/st/stm32mp15-pinctrl.dtsi   | 164 +++++++++
>>>    .../st/stm32mp157c-phyboard-sargas-rdk.dts    |  42 +++
>>>    .../dts/st/stm32mp157c-phycore-stm32mp1-3.dts |  60 ---
>>>    .../dts/st/stm32mp15xx-phyboard-sargas.dtsi   | 286
>>> +++++++++++++++
>>>    ...-som.dtsi => stm32mp15xx-phycore-som.dtsi} | 344 ++++---------
>>> -----
>>>    7 files changed, 564 insertions(+), 341 deletions(-)
>>>    create mode 100644 arch/arm/boot/dts/st/stm32mp157c-phyboard-
>>> sargas-rdk.dts
>>>    delete mode 100644 arch/arm/boot/dts/st/stm32mp157c-phycore-
>>> stm32mp1-3.dts
>>>    create mode 100644 arch/arm/boot/dts/st/stm32mp15xx-phyboard-
>>> sargas.dtsi
>>>    rename arch/arm/boot/dts/st/{stm32mp157c-phycore-stm32mp15-
>>> som.dtsi => stm32mp15xx-phycore-som.dtsi} (53%)
>>>
>>
>> Using b4 to get your series, I just see that there no mailing list
>> and
>> Dt maintainer in CC of your series. Did you use "get_maintainer.pl"
>> script ?
>>
> No, I only relied on reading the MAINTAINER file. But thanks, I now
> know that I have to use the "get_maintainer.pl" script.
> 
>> Can you please resend adding correct CC and TO list ?
> Yes sure. Should I continue taging the series as v2 ?
> I will made a new tiny coding style fix detected by checkpath.pl (tool
> that I havn't run before). So it would be a v3 in this case.

Either you continue with V3 adding new people in CC/TO but it could be a 
bit strange for them as they didn't get the V1 and V2.
Or you restart your series from scratch as only linux-stm32 subscribers 
and Phytec guys were aware of this series. In this case you could mark 
the current series as "abandoned"


>>
>> Note: ARM: dts: stm32mp15: --> ARM: dts: stm32
> Ok I will correct that. As PHYTEC provides phycore for both MP15x and
> MP13x stm32 SoC, I wanted to use this syntax to make distinction. I was
> not sure this was allowed.
> 
> Regards,
> Christophe
>>
>> thanks
>> Alex