From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: Patrick Venture <venture@google.com>
Cc: Corey Minyard <cminyard@mvista.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Hao Wu <wuhaotsh@google.com>
Subject: Re: [PATCH] hw/i2c: flatten pca954x mux device
Date: Wed, 2 Feb 2022 18:30:53 +0100 [thread overview]
Message-ID: <f10cbf13-ac56-cbe0-02f8-1d96a687700e@amsat.org> (raw)
In-Reply-To: <CAO=notzLfum_zkXhP+xQ9RTxcpG3oNxwFMPYWz+o1vYdF8ynQg@mail.gmail.com>
On 2/2/22 17:40, Patrick Venture wrote:
> Philippe,
>
> I0202 08:29:45.380384 6641 stream.go:31] qemu: child buses at
> "pca9546": "channel[*]", "channel[*]", "channel[*]", "channel[*]"
>
> Ok, so that's interesting. In one system (using qom-list) it's
> correct, but then when using it to do path assignment
> (qdev-monitor), it fails...
>
> I'm not as fond of the name i2c-bus.%d, since they're referred to as
> channels in the datasheet. If I do the manual name creation, can I
> keep the name channel or should I pivot over?
>
> Thanks
>
>
> -- >8 --
> diff --git a/hw/i2c/i2c_mux_pca954x.c b/hw/i2c/i2c_mux_pca954x.c
> index f9ce633b3a..a9517b612a 100644
> --- a/hw/i2c/i2c_mux_pca954x.c
> +++ b/hw/i2c/i2c_mux_pca954x.c
> @@ -189,9 +189,11 @@ static void pca954x_init(Object *obj)
>
> /* SMBus modules. Cannot fail. */
> for (i = 0; i < c->nchans; i++) {
> + g_autofree gchar *bus_name =
> g_strdup_printf("i2c.%d", i);
> +
> /* start all channels as disabled. */
> s->enabled[i] = false;
> - s->bus[i] = i2c_init_bus(DEVICE(s), "channel[*]");
> + s->bus[i] = i2c_init_bus(DEVICE(s), bus_name);
> }
> }
>
> ---
>
> (look at HMP 'info qtree' output).
>
> > }
> > }
>
> With the change:
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org
> <mailto:f4bug@amsat.org>>
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org
> <mailto:f4bug@amsat.org>>
>
>
> Just saw your reply, and found a bunch of other non-spam in my spam
> folder. I sent the message to the anti-spam team, hopefully that'll
> resolve this for myself and presumably others.
Thanks. I suppose the problem is the amsat.org domain.
> I definitely see the same result with the qdev-monitor, but was really
> surprised that the qom-list worked. I'll explicitly set the name, and
> i2c.%d is fine. The detail that they're channels is not really
> important to the end user presumably.
I agree it is better to follow datasheets, thus I am fine if you
change and use channel. How would it look like? "channel.0"?
FYI qdev busses are described in docs/qdev-device-use.txt.
We should be able to plug a device using some command line
such "-device i2c_test_dev,bus=channel.0,addr=0x55".
I wonder how to select the base PCA9548 ...
Maybe we need to pass the PCA ID to pca954x_init(), so we can
name "channel.2.0" for the 1st channel on the 2nd PCA?
Regards,
Phil.
next prev parent reply other threads:[~2022-02-02 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 16:30 [PATCH] hw/i2c: flatten pca954x mux device Patrick Venture
2022-02-01 19:02 ` Philippe Mathieu-Daudé via
2022-02-01 20:54 ` Patrick Venture
2022-02-02 16:20 ` Philippe Mathieu-Daudé via
2022-02-02 16:34 ` Patrick Venture
2022-02-02 16:40 ` Patrick Venture
2022-02-02 17:30 ` Philippe Mathieu-Daudé via [this message]
2022-02-02 21:30 ` Patrick Venture
2022-02-02 19:01 ` Peter Maydell
2022-02-02 19:53 ` 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=f10cbf13-ac56-cbe0-02f8-1d96a687700e@amsat.org \
--to=qemu-devel@nongnu.org \
--cc=cminyard@mvista.com \
--cc=f4bug@amsat.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).