Open soburi opened 1 month ago
Hello @soburi, Thank you for your creating for this issue. I have one comment and one concern.
Comment: "R7FA4M1AB" isn't enough to identify for the SoC on the board. The package type is also necessary. Actually, in FSP, when use with the actual board, we also specify the correct part number of MCU which used in the board. It is configured via e2studio. So, we cannot shorten the SoC name in Kconfig.
Concern: as we referred the guide in https://docs.zephyrproject.org/latest/hardware/porting/soc_porting.html
We understood that the SoC name must be same with the name is used on the board. I wonder that my understanding is still correct or not?
The name in Kconfig of Renesas RA series SoC currently uses the non-abbreviated name. e. g. r7fa4m1ab3cfm
Actually, the full name contains the temperature variation identifier and more; it is a bit lengthy. FSP uses a short name such as "R7FA4M1AB". It is enough from a software viewpoint.
It is good to align the policy with FSP.