Re: [PATCH v5 6/8] hw/i2c: parent slaves created with i2c_slave_create_simple
| Newsgroups | org.nongnu.qemu-arm,org.nongnu.qemu-devel |
|---|---|
| Message-ID | <[email protected]> |
> If you want the bus hierarchy, we have that; it's not the same > thing as the QOM ownership hierarchy. This means that the ownership of a standalone device should either be the board or the machine. We end up with a very flat and wide list of devices. It is more correct in term of ownership, but harder to pinpoint a device either from an API or even browsing it with info qom-tree, except if we can define more or less canonical way to name it. I do not think there is an API to traverse multiple buses and devices at once to reach a device though. Is there an alternative to locate a device from a (string) description on how/where it is connected, if QOM path is not the right idiom to use?