From: Jie Deng <jie.deng@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, wsa@kernel.org,
wsa+renesas@sang-engineering.com, mst@redhat.com, arnd@arndb.de,
jasowang@redhat.com, yu1.wang@intel.com, shuo.a.liu@intel.com,
conghui.chen@intel.com, viresh.kumar@linaro.org,
stefanha@redhat.com
Subject: Re: [PATCH v11] i2c: virtio: add a virtio i2c frontend driver
Date: Fri, 2 Jul 2021 09:05:22 +0800 [thread overview]
Message-ID: <a0ee5b05-0316-2529-143f-7da42ed56994@intel.com> (raw)
In-Reply-To: <YN2cs0H+5C892kM4@smile.fi.intel.com>
On 2021/7/1 18:45, Andy Shevchenko wrote:
> On Thu, Jul 01, 2021 at 11:24:46AM +0800, Jie Deng wrote:
>> Add an I2C bus driver for virtio para-virtualization.
>>
>> The controller can be emulated by the backend driver in
>> any device model software by following the virtio protocol.
>>
>> The device specification can be found on
>> https://lists.oasis-open.org/archives/virtio-comment/202101/msg00008.html.
>>
>> By following the specification, people may implement different
>> backend drivers to emulate different controllers according to
>> their needs.
>> - Use #ifdef CONFIG_PM_SLEEP to replace the "__maybe_unused".
> Why is that?
Please refer to https://lkml.org/lkml/2021/3/23/285.
prev parent reply other threads:[~2021-07-02 1:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 3:24 [PATCH v11] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-07-01 4:04 ` Viresh Kumar
2021-07-01 6:10 ` Jie Deng
2021-07-01 6:18 ` Viresh Kumar
2021-07-02 3:36 ` Jie Deng
2021-07-02 4:56 ` Viresh Kumar
2021-07-01 19:24 ` Wolfram Sang
2021-07-02 4:55 ` Viresh Kumar
2021-07-02 6:22 ` Wolfram Sang
2021-07-02 6:52 ` Jie Deng
2021-07-02 6:56 ` Viresh Kumar
2021-07-02 7:11 ` Wolfram Sang
2021-07-02 7:15 ` Jie Deng
2021-07-02 7:21 ` Viresh Kumar
2021-07-02 7:36 ` Wolfram Sang
2021-07-01 8:50 ` kernel test robot
2021-07-01 10:00 ` kernel test robot
2021-07-02 3:12 ` Jie Deng
2021-07-02 6:38 ` [kbuild-all] " Rong Chen
2021-07-01 10:45 ` Andy Shevchenko
2021-07-02 1:05 ` Jie Deng [this message]
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=a0ee5b05-0316-2529-143f-7da42ed56994@intel.com \
--to=jie.deng@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=conghui.chen@intel.com \
--cc=jasowang@redhat.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=shuo.a.liu@intel.com \
--cc=stefanha@redhat.com \
--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).