From: Patrick Venture <venture@google.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Corey Minyard <cminyard@mvista.com>, Hao Wu <wuhaotsh@google.com>,
Havard Skinnemoen <hskinnemoen@google.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 4/4] hw/i2c: add pca954x i2c-mux switch
Date: Fri, 9 Apr 2021 10:21:12 -0700 [thread overview]
Message-ID: <CAO=notxOYxSyVDA9J-uOBio7d0PByvGLgn40GHbU-yQRpic1Jw@mail.gmail.com> (raw)
In-Reply-To: <01f6f4c7-9f08-45f5-3e0c-b692c77dc4a5@amsat.org>
On Fri, Apr 9, 2021 at 9:51 AM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> Hi Patrick,
>
> On 4/9/21 6:25 PM, Patrick Venture wrote:
> > The pca954x is an i2c mux, and this adds support for two variants of
> > this device: the pca9546 and pca9548.
> >
> > This device is very common on BMCs to route a different channel to each
> > PCIe i2c bus downstream from the BMC.
> >
> > Signed-off-by: Patrick Venture <venture@google.com>
> > Reviewed-by: Hao Wu <wuhaotsh@google.com>
> > Reviewed-by: Havard Skinnemoen <hskinnemoen@google.com>
> > ---
> > MAINTAINERS | 6 +
> > hw/i2c/Kconfig | 4 +
> > hw/i2c/i2c_mux_pca954x.c | 290 +++++++++++++++++++++++++++++++
> > hw/i2c/meson.build | 1 +
> > hw/i2c/trace-events | 5 +
> > include/hw/i2c/i2c_mux_pca954x.h | 19 ++
> > 6 files changed, 325 insertions(+)
> > create mode 100644 hw/i2c/i2c_mux_pca954x.c
> > create mode 100644 include/hw/i2c/i2c_mux_pca954x.h
>
> > diff --git a/hw/i2c/Kconfig b/hw/i2c/Kconfig
> > index 09642a6dcb..8d120a25d5 100644
> > --- a/hw/i2c/Kconfig
> > +++ b/hw/i2c/Kconfig
> > @@ -28,3 +28,7 @@ config IMX_I2C
> > config MPC_I2C
> > bool
> > select I2C
> > +
> > +config PCA954X
> > + bool
> > + select I2C
>
> Do you have a circular dependency when also using:
>
> depends on I2C
>
> ?
I'm somewhat new to qemu -- I don't know what you mean, since I2C
doesn't depend on pca954x, I don't imagine there could be a circular
dependency.
>
> > +static void pca954x_realize(DeviceState *dev, Error **errp)
> > +{
> > + Pca954xState *s = PCA954X(dev);
> > + Pca954xClass *c = PCA954X_GET_CLASS(s);
> > + int i;
> > +
> > + /* SMBus modules. Cannot fail. */
> > + for (i = 0; i < c->nchans; i++) {
> > + Object *obj = OBJECT(&s->channel[i]);
> > + sysbus_realize(SYS_BUS_DEVICE(obj), &error_abort);
>
> No need to cast to Object:
>
> sysbus_realize(SYS_BUS_DEVICE(&s->channel[i]), &error_abort);
>
Ack, will fix in v3.
> > + }
> > +}
next prev parent reply other threads:[~2021-04-09 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 16:25 [PATCH v2 0/4] hw/i2c: Adds pca954x i2c mux switch device Patrick Venture
2021-04-09 16:25 ` [PATCH v2 1/4] hw/i2c: name I2CNode list in I2CBus Patrick Venture
2021-04-09 16:36 ` Philippe Mathieu-Daudé
2021-04-09 16:25 ` [PATCH v2 2/4] hw/i2c: add match method for device search Patrick Venture
2021-04-09 16:25 ` [PATCH v2 3/4] hw/i2c: move search to i2c_scan_bus method Patrick Venture
2021-04-09 16:25 ` [PATCH v2 4/4] hw/i2c: add pca954x i2c-mux switch Patrick Venture
2021-04-09 16:51 ` Philippe Mathieu-Daudé
2021-04-09 17:21 ` Patrick Venture [this message]
2021-04-09 21:20 ` Philippe Mathieu-Daudé
2021-04-09 21:32 ` Patrick Venture
2021-04-09 18:34 ` Corey Minyard
2021-04-09 19:30 ` Patrick Venture
2021-04-09 18:31 ` [PATCH v2 0/4] hw/i2c: Adds pca954x i2c mux switch device Corey Minyard
2021-04-09 19:33 ` Patrick Venture
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='CAO=notxOYxSyVDA9J-uOBio7d0PByvGLgn40GHbU-yQRpic1Jw@mail.gmail.com' \
--to=venture@google.com \
--cc=cminyard@mvista.com \
--cc=f4bug@amsat.org \
--cc=hskinnemoen@google.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).