On 19/6/25 11:23, Cédric Le Goater wrote:
Hi,

This is a follow up of a private discussion with Patrick.

Aspeed modeling started nearly 10y ago with the palmetto-bmc machine.
We now have 5 SoCs and 25 machines which are mostly defined in
in a single aspeed.c file. Multi SoC machines, fby35 and ast2700fc,
are defined in fby35.c and aspeed_ast27x0-fc.c respectively.

Since we started separating the SoCs :

   hw/arm/aspeed_ast10x0.c
   hw/arm/aspeed_ast2400.c
   hw/arm/aspeed_ast2600.c
   hw/arm/aspeed_ast27x0.c
   hw/arm/aspeed_ast27x0-ssp.c
   hw/arm/aspeed_ast27x0-tsp.c

We could do the same for the machines keeping an 'aspeed_ast<rev>'
prefix (and maybe avoid the 'bmc' suffix). I think this would ease
introduction of new machines. We would be able to get rid of
aspeed_eeprom.[ch] and move machine custom data in the machine source
file. Which seems cleaner.

Timing is about right for code reshuffling, still 3w before soft
freeze, no important changes inflight, but if we start doing this
conversion, we should do it for all. See the list below for the brave.

Comments ?

Good idea, but please split ASPEED_SOC in Kconfig accordingly.

Regards,

Phil.

Reply via email to