As far as I understand, the CPU type is an option when ordering. Here's what it says on the manufacturer's website: CPU: STMicroelectronics STM32MP151AAC3 microprocessor (STM32MP153AAC3 and STM32MP157AAC3 are compatible and can be customized). It's not a problem for me to make one type of CPU in the bindings, I just wanted the bindings file to be more flexible. #include "stm32mp151.dtsi" in this case we can transfer to MYD, as we don't really need MYC to be compiled separately. > On 30/08/2023 15:42, Alexander Shiyan wrote: > > The initial thought in the file name was that the modules could be > > equipped with a CPU > > other than STM32MP151, i.e. 153 or 157. The development board, as far > > i understand, > > equipped with a STM32MP151 only, so can we leave the current name for > > the module (15x) > > as is and change it only in the file name (and in compatible property) > > for the development > > board only? > > Depends. I do not see SoM here. You called it "MYIR MYC-YA15XC-T", so it > looks like end product for me. Can the same product have different SoC > module? How would your DTSI look like? You include there 151.dtsi, so it > could not have... > > Yes, you also need to adjust compatibles to reflect real names, not > wildcards.
