On 25/02/2025 16:51, Clement LE GOFFIC wrote: > On 2/25/25 14:04, Krzysztof Kozlowski wrote: >> On 25/02/2025 09:48, Clément Le Goffic wrote: >>> + >>> +maintainers: >>> + - Clément LE GOFFIC <clement.legoffic@xxxxxxxxxxx> >>> + >>> +description: | >> >> >> Do not need '|' unless you need to preserve formatting. > > Ok > >>> + STMicroelectronics's STM32 MPUs integrate a Hardware Debug Port (HDP). >>> + It allows to output internal signals on SoC's GPIO. >>> + >>> +properties: >>> + compatible: >>> + const: st,stm32mp-hdp >> >> There is a mess in STM SoCs. Sometimes you call SoC stm32, sometimes >> stm32mp and sometimes stm32mpXX. >> >> Define for all your STM contributions what is the actual SoC. This >> feedback was already given to ST. >> >>> + >>> + reg: >>> + maxItems: 1 >>> + >>> + clocks: >>> + maxItems: 1 >>> + >>> +patternProperties: >>> + '-pins$': >>> + type: object >>> + $ref: pinmux-node.yaml# >>> + >>> + properties: >>> + function: >>> + enum: [ "0", "1", "2", "3", "4", "5", "6", "7", >>> + "8", "9", "10", "11", "12", "13", "14", >>> + "15" ] >> >> Function which has a number is not really useful. What does it even express? > > As said in my previous answer, function names are very different from > one platform to another. Numbers were used as string to be generic. > I'll consider it in a V2. What does it mean "one platform to another"? This is one platform! Is this some sort of continuation of SoC compatible mess? What are the exact functions written in datasheet? Best regards, Krzysztof
