On 19/11/2026 09:49, Mohammad Odeh wrote:
Would it make sense to rename the shared model to |stm32l4_soc| and make L4x5 and L496 sibling variants under it?

After thinking more about it, I'd rather not go as far as stm32l4: the L4 family also includes other "families", such as the RM0394 (L41x–L46x), which differ significantly while this model follows RM0351 which covers both L4x5 and L4x6. Updating the header/description to say so (as for stm32f2xx_* being used by the F405) is probably enough. If a rename is still preferred, a separate mechanical patch before this one would make review easier, but it might be seen as gratuitous churn.

The abstract stm32l4x5-soc type already lets L496 be a sibling of the L4x5 variants. What seems more important to me is to make the variant-specific features class parameters: the SRAM2 alias at 0x2004_0000 that I talked about, GPIO port I, and the number of IRQs/EXTI lines.

  Sam

Reply via email to