From: Jie Deng <jie.deng@intel.com>
To: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, andriy.shevchenko@linux.intel.com,
conghui.chen@intel.com, arnd@arndb.de, kblaiech@mellanox.com,
jarkko.nikula@linux.intel.com, Sergey.Semin@baikalelectronics.ru,
rppt@kernel.org, loic.poulain@linaro.org, tali.perry1@gmail.com,
u.kleine-koenig@pengutronix.de, bjorn.andersson@linaro.org,
yu1.wang@intel.com, shuo.a.liu@intel.com,
viresh.kumar@linaro.org, stefanha@redhat.com,
pbonzini@redhat.com
Subject: Re: [PATCH v10] i2c: virtio: add a virtio i2c frontend driver
Date: Wed, 30 Jun 2021 15:51:08 +0800 [thread overview]
Message-ID: <3016ab8b-cbff-1309-6a1f-080703a4130f@intel.com> (raw)
In-Reply-To: <YNwd/t3DMKSOrTAT@ninjato>
On 2021/6/30 15:32, Wolfram Sang wrote:
>>>> + snprintf(vi->adap.name, sizeof(vi->adap.name), "Virtio I2C Adapter");
>>> Is there something to add so you can distinguish multiple instances?
>>> Most people want that.
>>
>> I find the I2C core will set a device name "i2c-%d" for this purpose, right?
>>
>> I think this name can be used to distinguish the adapter types while
>> "i2c-%d" can be used to
>>
>> distinguish instances. Does it make sense ?
> That alone does not help. See the 'i2cdetect -l' output of my Renesas
> board here:
>
> i2c-4 i2c e66d8000.i2c I2C adapter
> i2c-2 i2c e6510000.i2c I2C adapter
> i2c-7 i2c e60b0000.i2c I2C adapter
>
> Notice that the third column carries the base address, so you know which
> i2c-%d is which physical bus. I don't know if it makes sense in your
> "virtual" case, but so far it would always print "Virtio I2C Adapter".
> Maybe it makes sense to add some parent device name, too?
>
> And if this is not reasonable, just skip it. As I said, it can be
> helpful at times, but it is definately not a show stopper.
OK. I will add the virtio_device index for this purpose.
which indicates the unique position on the virtio bus.
Thanks Wolfram, I will fix it and send the v11.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-06-30 7:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 14:19 [PATCH v10] i2c: virtio: add a virtio i2c frontend driver Jie Deng
[not found] ` <20210323072704.rgoelmq62fl2wjjf@vireshk-i7>
2021-03-23 8:33 ` Jie Deng
2021-03-23 9:27 ` Arnd Bergmann
2021-03-24 1:17 ` Jie Deng
[not found] ` <20210415064538.a4vf7egk6l3u6zfz@vireshk-i7>
2021-04-15 6:56 ` Jie Deng
[not found] ` <20210415072131.GA1006@kunai>
[not found] ` <20210415072431.apntpcwrk5hp6zg4@vireshk-i7>
[not found] ` <20210415072823.GB1006@kunai>
2021-04-15 8:15 ` Jie Deng
[not found] ` <20210415081828.GD1006@kunai>
2021-04-15 8:20 ` Jie Deng
2021-05-27 6:49 ` Jie Deng
2021-05-12 1:37 ` Jie Deng
[not found] ` <20210323090108.ygx76exdgzudeeqi@vireshk-i7>
[not found] ` <20210323093839.n7cq7f5poebqdwit@vireshk-i7>
2021-03-24 0:53 ` Jie Deng
[not found] ` <20210324035225.skkllxexjl65gs6x@vireshk-i7>
2021-03-24 4:00 ` Jie Deng
[not found] ` <20210324042046.idkctj2t7cxi53jf@vireshk-i7>
2021-03-24 6:05 ` Jie Deng
[not found] ` <20210324060907.nwilmghg2xcdz7nv@vireshk-i7>
2021-03-24 6:41 ` Jie Deng
2021-04-14 2:07 ` Jie Deng
[not found] ` <20210414035229.7uqfdcd6dy2ryg3s@vireshk-i7>
2021-04-15 6:25 ` Jie Deng
2021-04-15 3:51 ` Jason Wang
2021-04-15 6:17 ` Jie Deng
[not found] ` <YNmK0MP5ffQpiipt@ninjato>
2021-06-28 9:01 ` Arnd Bergmann
[not found] ` <YNmVg3ZhshshlbSx@ninjato>
2021-06-28 9:51 ` Arnd Bergmann
[not found] ` <YNmg2IEpUlArZXPK@ninjato>
2021-06-28 11:50 ` Arnd Bergmann
[not found] ` <YNnjh3xxyaZZSo9N@ninjato>
2021-06-29 3:04 ` Jie Deng
[not found] ` <YNraQMl3yJyZ6d5+@kunai>
2021-06-29 9:13 ` Viresh Kumar
2021-06-29 4:10 ` Viresh Kumar
[not found] ` <YNrZVho/98qgJS9N@kunai>
2021-06-29 8:52 ` Viresh Kumar
[not found] ` <YNyB/+fNK0u2bI6j@kunai>
2021-06-30 15:09 ` Viresh Kumar
2021-06-29 3:03 ` Jie Deng
[not found] ` <YNrw4rxihFLuqLtY@ninjato>
2021-06-29 10:16 ` Viresh Kumar
[not found] ` <YNr0uDx1fv+Gjd7m@ninjato>
2021-06-29 10:30 ` Viresh Kumar
[not found] ` <YNr5Jf3WDTH7U5b7@ninjato>
[not found] ` <YNr5ZRhT3qn+e9/m@ninjato>
2021-06-29 10:56 ` Viresh Kumar
[not found] ` <YNr/2E/T4FRjLOgy@ninjato>
2021-06-29 11:16 ` Viresh Kumar
2021-07-05 12:18 ` Viresh Kumar
2021-07-06 1:50 ` Jie Deng
[not found] ` <YPmLoeLSPS1tfYUK@ninjato>
2021-07-23 2:28 ` Viresh Kumar
2021-07-23 5:28 ` Viresh Kumar
2021-06-30 6:45 ` Jie Deng
[not found] ` <YNwd/t3DMKSOrTAT@ninjato>
2021-06-30 7:51 ` Jie Deng [this message]
2021-06-30 7:55 ` Arnd Bergmann
2021-06-30 8:07 ` Andy Shevchenko
2021-06-30 8:29 ` Arnd Bergmann
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=3016ab8b-cbff-1309-6a1f-080703a4130f@intel.com \
--to=jie.deng@intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=conghui.chen@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=kblaiech@mellanox.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rppt@kernel.org \
--cc=shuo.a.liu@intel.com \
--cc=stefanha@redhat.com \
--cc=tali.perry1@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa@kernel.org \
--cc=yu1.wang@intel.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).