From: Patrick Leis <venture@google.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Corey Minyard" <cminyard@mvista.com>,
"Titus Rwantare" <titusr@google.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: standardizing i2c device ids
Date: Fri, 21 Jun 2024 10:22:45 -0700 [thread overview]
Message-ID: <CAO=notxkpV3cchJ4LycrOnUXkCRbtJaMroe0urLHBg5OQX1U_A@mail.gmail.com> (raw)
In-Reply-To: <6297a086-7e59-4299-aabd-68cf14fc42bd@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Thu, Jun 20, 2024 at 11:26 PM Philippe Mathieu-Daudé <philmd@linaro.org>
wrote:
> Hi Patrick,
>
> On 21/6/24 00:03, Patrick Leis wrote:
> > Corey and Peter,
> >
> > My team builds lots of configurations for Qemu boards, and one pain
> > point has been that the qom path for a device depends on the device
> > insertion order, child[0], child[1] and the like. I noticed that the
> > qdev paths for devices also exist by their device id property. By
> > default, this ends up being the device type name. I was wondering if it
> > made sense to override this with the device type plus the smbus
> > address? I did something similar with the i2c mux device, to resolve
> > part of this issue.
>
> Including Markus since we discussed this with him last year, but
> I don't remember correctly what was agreed / decided :S
>
Thanks :)
I'd really like to be able to access devices with paths that specify the
device I want specifically :)
>
> Regards,
>
> Phil.
>
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
next prev parent reply other threads:[~2024-06-21 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 22:03 standardizing i2c device ids Patrick Leis
2024-06-21 6:26 ` Philippe Mathieu-Daudé
2024-06-21 17:22 ` Patrick Leis [this message]
2024-06-22 8:43 ` Markus Armbruster
2024-06-27 22:20 ` Patrick Leis
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=notxkpV3cchJ4LycrOnUXkCRbtJaMroe0urLHBg5OQX1U_A@mail.gmail.com' \
--to=venture@google.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=cminyard@mvista.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@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).