From: Jie Deng <jie.deng@intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: 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,
jarkko.nikula@linux.intel.com, jdelvare@suse.de,
Sergey.Semin@baikalelectronics.ru, krzk@kernel.org,
rppt@kernel.org, loic.poulain@linaro.org, tali.perry1@gmail.com,
bjorn.andersson@linaro.org, shuo.a.liu@intel.com,
conghui.chen@intel.com, yu1.wang@intel.com
Subject: Re: [PATCH v3] i2c: virtio: add a virtio i2c frontend driver
Date: Mon, 12 Oct 2020 11:18:38 +0800 [thread overview]
Message-ID: <4b4cd16b-5930-008f-1139-0dae2825f717@intel.com> (raw)
In-Reply-To: <20201008140151.GE897@ninjato>
On 2020/10/8 22:01, Wolfram Sang wrote:
> Hi,
>
> some super high level questions:
>
>> different controllers according to their needs. A backend
>> example can be found in the device model of the open source
>> project ACRN. For more information, please refer to
>> https://projectacrn.org.
> Could you provide a link directly to the backend, please?
Sure. Here is the link.
https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/devicemodel/hw/pci/virtio/virtio_i2c.c
>> The device ID request:
>> https://github.com/oasis-tcs/virtio-spec/issues/85
> Shall we wait for this to be approved? Or will it get only approved once
> the driver here is upstream?
That's what I want to know also.
So hi Michael, what's the upstream flow for this patch ?
Thanks.
>> + If you say yes to this option, support will be included for the virtio
>> + I2C adapter driver. The hardware can be emulated by any device model
>> + software according to the virtio protocol.
> That means stuff like "limiting which devices on a given bus can be
> accessed" will be handled by the backends, or?
>
> What kind of testing has been done with this on which setup?
>
> Thanks and happy hacking,
>
> Wolfram
Yes, you can configure what devices can be seen by the guest.
This provides a way to flexibly organize and manage I2C slave devices
from the guest.
We tested it on Intel APL MRB. There are some docs for you reference.
https://projectacrn.github.io/latest/developer-guides/hld/virtio-i2c.html?highlight=i2c
Regards.
next prev parent reply other threads:[~2020-10-12 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350309657ab0c7b9f97e7a5c71d084f88caa549.1600743079.git.jie.deng@intel.com>
2020-09-22 11:23 ` [PATCH v3] i2c: virtio: add a virtio i2c frontend driver Andy Shevchenko
2020-10-08 14:01 ` Wolfram Sang
2020-10-12 3:18 ` Jie Deng [this message]
2020-10-10 3:14 ` Jason Wang
[not found] ` <2dc4bd12-9f23-7caa-b1ec-f3403d36e065@intel.com>
2020-10-12 3:43 ` Jason Wang
2020-10-13 7:16 ` Jie Deng
2020-10-13 8:00 ` Jason Wang
2020-10-14 8:37 ` Jie Deng
2020-10-15 7:06 ` Jason Wang
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=4b4cd16b-5930-008f-1139-0dae2825f717@intel.com \
--to=jie.deng@intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=conghui.chen@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=jdelvare@suse.de \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mst@redhat.com \
--cc=rppt@kernel.org \
--cc=shuo.a.liu@intel.com \
--cc=tali.perry1@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
--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).