From: Markus Armbruster <armbru@redhat.com>
To: Mark Cave-Ayland <mark.caveayland@nutanix.com>
Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
milesg@linux.ibm.com, qemu-ppc@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH 2/8] hw/gpio/pca9554: Move most code from .h to .c
Date: Mon, 09 Nov 2026 10:40:19 +0100 [thread overview]
Message-ID: <878q32737g.fsf@pond.sub.org> (raw)
In-Reply-To: <792a4d16-8318-4a06-b5b6-0122dbf4d19d@nutanix.com> (Mark Cave-Ayland's message of "Mon, 9 Nov 2026 08:55:14 +0000")
Mark Cave-Ayland <mark.caveayland@nutanix.com> writes:
> On 06/11/2026 11:04, Markus Armbruster wrote:
>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> include/hw/gpio/pca9554.h | 25 -------------------------
>> hw/gpio/pca9554.c | 24 ++++++++++++++++++++++++
>> 2 files changed, 24 insertions(+), 25 deletions(-)
>> diff --git a/include/hw/gpio/pca9554.h b/include/hw/gpio/pca9554.h
>> index ac835371aa..1b33a8a752 100644
>> --- a/include/hw/gpio/pca9554.h
>> +++ b/include/hw/gpio/pca9554.h
>> @@ -8,32 +8,7 @@
>> #ifndef PCA9554_H
>> #define PCA9554_H
>> -#include "hw/i2c/i2c.h"
>> -#include "qom/object.h"
>> -
>> #define TYPE_PCA9554 "pca9554"
>> #define TYPE_PCA9536 "pca9536"
>> -typedef struct PCA9554State PCA9554State;
>> -DECLARE_INSTANCE_CHECKER(PCA9554State, PCA9554,
>> - TYPE_PCA9554)
>> -
>> -#define PCA9554_NR_REGS 4
>> -#define PCA9554_PIN_COUNT 8
>> -#define PCA9536_PIN_COUNT 4
>> -
>> -struct PCA9554State {
>> - /*< private >*/
>> - I2CSlave i2c;
>> - /*< public >*/
>> -
>> - uint8_t len;
>> - uint8_t pointer;
>> -
>> - uint8_t regs[PCA9554_NR_REGS];
>> - qemu_irq gpio_out[PCA9554_PIN_COUNT];
>> - uint8_t ext_state[PCA9554_PIN_COUNT];
>> - char *description; /* For debugging purpose only */
>> - bool hw_dir; /* Honor pin direction */
>> -};
>> #endif
>
> Is there anything left in pca9554.h at this point?
Same as pca9552.h: just the #define TYPE_... Visible above if you
squint :)
[...]
> Otherwise:
>
> Reviewed-by: Mark Cave-Ayland <mark.caveayland@nutanix.com>
Thank you!
next prev parent reply other threads:[~2026-11-09 9:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 11:04 [PATCH 0/8] hw/gpio/pca955x: Improvements around props "pin" and "led" Markus Armbruster
2026-11-06 11:04 ` [PATCH 1/8] hw/gpio/pca9552: Convert pin and led properties to class properties Markus Armbruster
2026-11-06 20:17 ` Miles Glenn
2026-11-09 8:51 ` Mark Cave-Ayland
2026-11-06 11:04 ` [PATCH 2/8] hw/gpio/pca9554: Move most code from .h to .c Markus Armbruster
2026-11-06 20:18 ` Miles Glenn
2026-11-09 8:55 ` Mark Cave-Ayland
2026-11-09 9:40 ` Markus Armbruster [this message]
2026-11-06 11:04 ` [PATCH 3/8] hw/gpio/pca9554: Simplify QOM type creation Markus Armbruster
2026-11-06 20:19 ` Miles Glenn
2026-11-09 8:56 ` Mark Cave-Ayland
2026-11-06 11:04 ` [PATCH 4/8] hw/gpio/pca9554: New abstract base "pca9554-base" Markus Armbruster
2026-11-06 20:19 ` Miles Glenn
2026-11-09 9:02 ` Mark Cave-Ayland
2026-11-09 10:17 ` Mark Cave-Ayland
2026-11-09 11:56 ` Markus Armbruster
2026-11-09 14:20 ` Mark Cave-Ayland
2026-11-09 14:44 ` Markus Armbruster
2026-11-09 10:24 ` Markus Armbruster
2026-11-09 13:52 ` BALATON Zoltan
2026-11-09 14:17 ` Markus Armbruster
2026-11-06 11:04 ` [PATCH 5/8] hw/gpio/pca9554: Convert pin properties to class properties Markus Armbruster
2026-11-06 20:20 ` Miles Glenn
2026-11-09 9:03 ` Mark Cave-Ayland
2026-11-06 11:04 ` [PATCH 6/8] hw/gpio/pca955x: use QAPI enums for led and pin properties Markus Armbruster
2026-11-06 20:20 ` Miles Glenn
2026-11-09 9:05 ` Mark Cave-Ayland
2026-11-09 10:20 ` Markus Armbruster
2026-11-06 11:04 ` [PATCH 7/8] hw/gpio/pca955x: Improve @qapi-type reported by qom-list etc Markus Armbruster
2026-11-06 20:21 ` Miles Glenn
2026-11-09 9:06 ` Mark Cave-Ayland
2026-11-06 11:04 ` [PATCH 8/8] hw/gpio/pca955x: Simplify pin and led getters and setters Markus Armbruster
2026-11-06 20:21 ` Miles Glenn
2026-11-09 9:09 ` Mark Cave-Ayland
2026-11-09 10:19 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878q32737g.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.caveayland@nutanix.com \
--cc=milesg@linux.ibm.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.