From: Patrick Venture <venture@google.com>
To: Corey Minyard <minyard@acm.org>
Cc: "Corey Minyard" <cminyard@mvista.com>,
"Hao Wu" <wuhaotsh@google.com>,
"Havard Skinnemoen" <hskinnemoen@google.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 0/4] hw/i2c: Adds pca954x i2c mux switch device
Date: Thu, 15 Apr 2021 10:14:24 -0700 [thread overview]
Message-ID: <CAO=notz+EMXqv+5ndHCGgcwUwGfGMNYt3NCVfx87R9HEutwf2w@mail.gmail.com> (raw)
In-Reply-To: <20210415121257.GD5612@minyard.net>
On Thu, Apr 15, 2021 at 5:13 AM Corey Minyard <minyard@acm.org> wrote:
>
> On Mon, Apr 12, 2021 at 12:45:18PM -0700, Patrick Venture wrote:
> > The i2c mux device pca954x implements two devices:
> > - the pca9546 and pca9548.
>
> This looks good, I have pulled it into my queue. 6.0 is about to be
> released, I'll try to remember to request a pull after that.
>
> Thanks,
>
> -corey
Thanks, after I see the pull I'll send out a small stack I have of bmc
boards that can now use this device.
Patrick
>
> >
> > v4:
> > - Fixed up bug where the i2c_scan_bus wasn't parameterizing the
> > current_devs list.
> > - Minor consistency changes in the i2c mux pca954x.
> >
> > v3:
> > - fixup comment with missing end parenthesis.
> > - removed superfluous object cast.
> >
> > v2:
> > - the core i2c bus now calls a match method on each i2c child, which
> > by default will only check for a match against itself.
> > - the pca954x device overrides the i2c device match method to search
> > the children for each of its buses that are active.
> > - the pca954x device now owns an i2c bus for each channel, allowing
> > the normal device model to attach devices to the channels.
> >
> > Patrick Venture (4):
> > hw/i2c: name I2CNode list in I2CBus
> > hw/i2c: add match method for device search
> > hw/i2c: move search to i2c_scan_bus method
> > hw/i2c: add pca954x i2c-mux switch
> >
> > MAINTAINERS | 6 +
> > hw/i2c/Kconfig | 4 +
> > hw/i2c/core.c | 55 ++++--
> > hw/i2c/i2c_mux_pca954x.c | 290 +++++++++++++++++++++++++++++++
> > hw/i2c/meson.build | 1 +
> > hw/i2c/trace-events | 5 +
> > include/hw/i2c/i2c.h | 17 +-
> > include/hw/i2c/i2c_mux_pca954x.h | 19 ++
> > 8 files changed, 383 insertions(+), 14 deletions(-)
> > create mode 100644 hw/i2c/i2c_mux_pca954x.c
> > create mode 100644 include/hw/i2c/i2c_mux_pca954x.h
> >
> > --
> > 2.31.1.295.g9ea45b61b8-goog
> >
> >
prev parent reply other threads:[~2021-04-15 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 19:45 [PATCH v4 0/4] hw/i2c: Adds pca954x i2c mux switch device Patrick Venture
2021-04-12 19:45 ` [PATCH v4 1/4] hw/i2c: name I2CNode list in I2CBus Patrick Venture
2021-04-12 19:45 ` [PATCH v4 2/4] hw/i2c: add match method for device search Patrick Venture
2021-04-12 19:45 ` [PATCH v4 3/4] hw/i2c: move search to i2c_scan_bus method Patrick Venture
2021-04-12 19:45 ` [PATCH v4 4/4] hw/i2c: add pca954x i2c-mux switch Patrick Venture
2021-04-15 12:12 ` [PATCH v4 0/4] hw/i2c: Adds pca954x i2c mux switch device Corey Minyard
2021-04-15 17:14 ` Patrick Venture [this message]
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=notz+EMXqv+5ndHCGgcwUwGfGMNYt3NCVfx87R9HEutwf2w@mail.gmail.com' \
--to=venture@google.com \
--cc=cminyard@mvista.com \
--cc=f4bug@amsat.org \
--cc=hskinnemoen@google.com \
--cc=minyard@acm.org \
--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).