From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Viresh Kumar <viresh.kumar@linaro.org>, Jie Deng <jie.deng@intel.com>
Cc: linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com, wsa@kernel.org,
jasowang@redhat.com, wsa+renesas@sang-engineering.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, stefanha@redhat.com,
pbonzini@redhat.com
Subject: Re: [PATCH v8] i2c: virtio: add a virtio i2c frontend driver
Date: Thu, 18 Mar 2021 15:40:30 +0100 [thread overview]
Message-ID: <0dfff1ac-50bb-b5bc-72ea-880fd52ed60d@metux.net> (raw)
In-Reply-To: <20210316074409.2afwsaeqxuwvj7bd@vireshk-i7>
On 16.03.21 08:44, Viresh Kumar wrote:
> FWIW, this limits this driver to support a single device ever. We
> can't bind multiple devices to this driver now. Yeah, perhaps we will
> never be required to do so, but who knows.
Actually, I believe multiple devices really should be possible.
The major benefit of virtio-i2c is either bridging certan real bus'es
into a confined workload, or creating virtual hw testbeds w/o having to
write a complete emulation (in this case, for dozens of different i2c
controllers) - and having multiple i2c interfaces in one machine isn't
exactly rare.
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2021-03-18 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 10:35 [PATCH v8] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-03-16 7:44 ` Viresh Kumar
2021-03-18 14:40 ` Enrico Weigelt, metux IT consult [this message]
2021-03-18 14:52 ` Arnd Bergmann
2021-03-19 3:54 ` Viresh Kumar
2021-03-19 5:31 ` Jie Deng
2021-03-19 5:40 ` Viresh Kumar
2021-03-19 6:29 ` Jie Deng
2021-03-19 6:35 ` Viresh Kumar
2021-03-19 6:56 ` Jie Deng
2021-03-19 8:27 ` Arnd Bergmann
2021-03-16 7:53 ` Viresh Kumar
2021-03-19 5:53 ` Viresh Kumar
2021-03-19 7:52 ` Jie Deng
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=0dfff1ac-50bb-b5bc-72ea-880fd52ed60d@metux.net \
--to=lkml@metux.net \
--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=jie.deng@intel.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+renesas@sang-engineering.com \
--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).