Re: [PATCH v1 0/1] hw/i2c/aspeed: Introduce 'bus-label' to customize bus naming

[Markus Armbruster <armbru@redhat.com>]

Cédric Le Goater <clg@kaod.org> writes:

> On 1/15/26 20:47, Philippe Mathieu-Daudé wrote:
>> Hi,
>> Cc'ing Markus.
>> On 12/1/26 09:30, Kane Chen via qemu development wrote:
>>> From: Kane-Chen-AS <kane_chen@aspeedtech.com>
>>>
>>> Currently, the Aspeed I2C controller uses a static naming convention
>>> for its buses (e.g., "aspeed.i2c.bus.0"). This approach leads to
>>> object name conflicts in machine models that incorporate multiple I2C
>>> controllers, such as an Aspeed SoC paired with an external IO expander
>>> or a co-processor like the AST1700.
>>>
>> Is this a side-effect of Problem 4: 'The /machine/unattached/ orphanage'
>> described here?
>> https://lore.kernel.org/qemu-devel/87o7d1i7ky.fsf@pond.sub.org/
>> This problem isn't specific to I2C nor Aspeed.
>
>
> See the discussion here :
>
>   https://lore.kernel.org/qemu-devel/006fa26f-6b84-4e82-b6e1-7d1353579441@kaod.org/
>
> The Aspeed SoC has 3*16 I2C buses attached on 3 different I2C
> controllers plus the I2C/I3C buses. We need to find a way to
> distinguish these groups at the QEMU machine level to be able
> to add devices on the right bus when using the command line.
>
> Suggestions welcome !

Please show me how to start a QEMU with the 48 I2C mentioned above,
complete with output of "info qtree".