From: Corey Minyard <cminyard@mvista.com>
To: Patrick Venture <venture@google.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
"Hao Wu" <wuhaotsh@google.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH RESEND] hw/i2c: Enable an id for the pca954x devices
Date: Tue, 21 Mar 2023 20:41:22 -0500 [thread overview]
Message-ID: <ZBpcwnsttm5NSbTc@minyard.net> (raw)
In-Reply-To: <20230321182744.2814034-1-venture@google.com>
[-- Attachment #1: Type: text/plain, Size: 3049 bytes --]
On Tue, Mar 21, 2023 at 11:27:44AM -0700, Patrick Venture wrote:
> This allows the devices to be more readily found and specified.
> Without setting the id field, they can only be found by device type
> name, which doesn't let you specify the second of the same device type
> behind a bus.
So basically, this helps you find a specific device if you have more
than one of them. Yeah, probably a good idea in this case.
>
> Tested: Verified that by default the device was findable with the id
> 'pca954x[77]', for an instance attached at that address.
>
> Signed-off-by: Patrick Venture <venture@google.com>
> Reviewed-by: Hao Wu <wuhaotsh@google.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> hw/i2c/i2c_mux_pca954x.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/hw/i2c/i2c_mux_pca954x.c b/hw/i2c/i2c_mux_pca954x.c
> index a9517b612a..4f8c2d6ae1 100644
> --- a/hw/i2c/i2c_mux_pca954x.c
> +++ b/hw/i2c/i2c_mux_pca954x.c
> @@ -20,6 +20,7 @@
> #include "hw/i2c/i2c_mux_pca954x.h"
> #include "hw/i2c/smbus_slave.h"
> #include "hw/qdev-core.h"
> +#include "hw/qdev-properties.h"
> #include "hw/sysbus.h"
> #include "qemu/log.h"
> #include "qemu/module.h"
> @@ -43,6 +44,8 @@ typedef struct Pca954xState {
>
> bool enabled[PCA9548_CHANNEL_COUNT];
> I2CBus *bus[PCA9548_CHANNEL_COUNT];
> +
> + char *id;
> } Pca954xState;
>
> /*
> @@ -181,6 +184,17 @@ static void pca9548_class_init(ObjectClass *klass, void *data)
> s->nchans = PCA9548_CHANNEL_COUNT;
> }
>
> +static void pca954x_realize(DeviceState *dev, Error **errp)
> +{
> + Pca954xState *s = PCA954X(dev);
> + DeviceState *d = DEVICE(s);
> + if (s->id) {
> + d->id = g_strdup(s->id);
> + } else {
> + d->id = g_strdup_printf("pca954x[%x]", s->parent.i2c.address);
> + }
> +}
> +
> static void pca954x_init(Object *obj)
> {
> Pca954xState *s = PCA954X(obj);
> @@ -197,6 +211,11 @@ static void pca954x_init(Object *obj)
> }
> }
>
> +static Property pca954x_props[] = {
> + DEFINE_PROP_STRING("id", Pca954xState, id),
> + DEFINE_PROP_END_OF_LIST()
> +};
There is already an "id=" thing in qemu for doing links between front
ends and back ends. That's probably not the best name to use. Several
devices, like network devices, use "name" for identification in the
monitor.
-corey
> +
> static void pca954x_class_init(ObjectClass *klass, void *data)
> {
> I2CSlaveClass *sc = I2C_SLAVE_CLASS(klass);
> @@ -209,9 +228,12 @@ static void pca954x_class_init(ObjectClass *klass, void *data)
> rc->phases.enter = pca954x_enter_reset;
>
> dc->desc = "Pca954x i2c-mux";
> + dc->realize = pca954x_realize;
>
> k->write_data = pca954x_write_data;
> k->receive_byte = pca954x_read_byte;
> +
> + device_class_set_props(dc, pca954x_props);
> }
>
> static const TypeInfo pca954x_info[] = {
> --
> 2.35.1.894.gb6a874cedc-goog
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3426 bytes --]
next prev parent reply other threads:[~2023-03-22 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 18:27 [PATCH RESEND] hw/i2c: Enable an id for the pca954x devices Patrick Venture
2023-03-22 1:41 ` Corey Minyard [this message]
2023-03-22 17:03 ` Patrick Venture
2023-03-22 18:35 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2022-10-11 15:46 Patrick Venture
2022-10-18 10:36 ` Philippe Mathieu-Daudé
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=ZBpcwnsttm5NSbTc@minyard.net \
--to=cminyard@mvista.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.com \
--cc=wuhaotsh@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).