[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 6/8] hw/arm/aspeed: Describe each PCA9552 device
|
From: |
Philippe Mathieu-Daudé |
|
Subject: |
Re: [PATCH v4 6/8] hw/arm/aspeed: Describe each PCA9552 device |
|
Date: |
Wed, 24 Jun 2020 18:54:29 +0200 |
Hi Cédric,
On Mon, Jun 22, 2020 at 10:35 AM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> On 6/22/20 8:49 AM, Cédric Le Goater wrote:
> > On 6/21/20 12:58 AM, Philippe Mathieu-Daudé wrote:
> >> We have 2 distinct PCA9552 devices. Set their description
> >> to distinguish them when looking at the trace events.
> >
> > It's nice and usefull but couldn't we do the same with a QOM object name ?
>
> qdev inherits QOM and overloads it with the qdev_ API.
> Since we have a qdev object, isn't it better to use the qdev_ API?
>
> I'd keep the QOM API for bare QOM objects.(I find confusing to use
> different APIs).
FYI you can get an idea of the QOM -> qdev -> sysbus -> ... tree here:
https://observablehq.com/@philmd/qemu-aarch64-softmmu-qom-tree
[PATCH v4 7/8] hw/misc/pca9552: Trace GPIO change events, Philippe Mathieu-Daudé, 2020/06/20
[PATCH v4 8/8] hw/misc/pca9552: Model qdev output GPIOs, Philippe Mathieu-Daudé, 2020/06/20