public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jie Deng <jie.deng@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Linux I2C" <linux-i2c@vger.kernel.org>,
	"open list:DRM DRIVER FOR QEMU'S CIRRUS DEVICE"
	<virtualization@lists.linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	yu1.wang@intel.com, conghui.chen@intel.com,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	gregkh <gregkh@linuxfoundation.org>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	jiedeng@alumni.sjtu.edu.cn
Subject: Re: [PATCH v15] i2c: virtio: add a virtio i2c frontend driver
Date: Tue, 27 Jul 2021 10:15:16 +0800	[thread overview]
Message-ID: <a65f32f6-6068-951c-c080-9ae27915b288@intel.com> (raw)
In-Reply-To: <CAK8P3a1=TpKLGMzvoLafjxtmoBbDL+sBMb8ZiEmTjW91Yr-cYw@mail.gmail.com>


On 2021/7/23 17:03, Arnd Bergmann wrote:
> On Fri, Jul 23, 2021 at 7:44 AM Jie Deng <jie.deng@intel.com> wrote:
>
>> +
>> +       ret = virtio_i2c_setup_vqs(vi);
>> +       if (ret)
>> +               return ret;
>> +
>> +       vi->adap.owner = THIS_MODULE;
>> +       snprintf(vi->adap.name, sizeof(vi->adap.name),
>> +                "i2c_virtio at virtio bus %d", vdev->index);
>> +       vi->adap.algo = &virtio_algorithm;
>> +       vi->adap.quirks = &virtio_i2c_quirks;
>> +       vi->adap.dev.parent = &vdev->dev;
>> +       i2c_set_adapdata(&vi->adap, vi);
>> +
>> +       /*
>> +        * Setup ACPI node for controlled devices which will be probed through
>> +        * ACPI.
>> +        */
>> +       ACPI_COMPANION_SET(&vi->adap.dev, ACPI_COMPANION(pdev));
> Since there is now a generic way for virtio drivers to link up with OF
> device nodes, maybe this should be handled the same way in the
> virtio core rather than the driver?


I'm currently based on the I2C tree. Has that patch been already merged ?

Anyway, I think we can send an additional patch to remove this line once 
that

"generic way" patch is merged.

Regards,

Jie




  parent reply	other threads:[~2021-07-27  2:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23  5:44 [PATCH v15] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-07-23  9:03 ` Arnd Bergmann
2021-07-26  3:59   ` Viresh Kumar
2021-07-28  9:33     ` Wolfram Sang
2021-07-27  2:15   ` Jie Deng [this message]
2021-07-27  4:23     ` Viresh Kumar
2021-08-17 20:22 ` Wolfram Sang
2021-08-18  1:29   ` 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=a65f32f6-6068-951c-c080-9ae27915b288@intel.com \
    --to=jie.deng@intel.com \
    --cc=alex.bennee@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=conghui.chen@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=jiedeng@alumni.sjtu.edu.cn \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vincent.guittot@linaro.org \
    --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