From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Jason Wang <jasowang@redhat.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@kernel.org>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
Vincent Guittot <vincent.guittot@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org, Bill Mills <bill.mills@linaro.org>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH V3 5/5] virtio: Bind virtio device to device-tree node
Date: Mon, 13 Sep 2021 05:45:37 -0400 [thread overview]
Message-ID: <20210913053816-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d5f87715-5a3e-1e85-68ba-3e4d35163c68@ozlabs.ru>
On Mon, Sep 13, 2021 at 07:19:17PM +1000, Alexey Kardashevskiy wrote:
>
>
> On 26/07/2021 14:51, Viresh Kumar wrote:
> > Bind the virtio devices with their of_node. This will help users of the
> > virtio devices to mention their dependencies on the device in the DT
> > itself. Like GPIO pin users can use the phandle of the device node, or
> > the node may contain more subnodes to add i2c or spi eeproms and other
> > users.
> >
> > Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > drivers/virtio/virtio.c | 57 ++++++++++++++++++++++++++++++++++++++---
> > 1 file changed, 54 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c
> > index 4b15c00c0a0a..d001e84a5b23 100644
> > --- a/drivers/virtio/virtio.c
> > +++ b/drivers/virtio/virtio.c
> > @@ -4,6 +4,7 @@
> > #include <linux/virtio_config.h>
> > #include <linux/module.h>
> > #include <linux/idr.h>
> > +#include <linux/of.h>
> > #include <uapi/linux/virtio_ids.h>
> >
> > /* Unique numbering for virtio devices. */
> > @@ -292,6 +293,9 @@ static int virtio_dev_remove(struct device *_d)
> >
> > /* Acknowledge the device's existence again. */
> > virtio_add_status(dev, VIRTIO_CONFIG_S_ACKNOWLEDGE);
> > +
> > + of_node_put(dev->dev.of_node);
> > +
> > return 0;
> > }
> >
> > @@ -319,6 +323,43 @@ void unregister_virtio_driver(struct virtio_driver *driver)
> > }
> > EXPORT_SYMBOL_GPL(unregister_virtio_driver);
> >
> > +static int virtio_device_of_init(struct virtio_device *dev)
> > +{
> > + struct device_node *np, *pnode = dev_of_node(dev->dev.parent);
> > + char compat[] = "virtio,XXXXXXXX"; /* Reserve enough space 32-bit id */
> > + int ret, count;
> > +
> > + if (!pnode)
> > + return 0;
> > +
> > + count = of_get_available_child_count(pnode);
> > + if (!count)
> > + return 0;
> > +
> > + /* There can be only 1 child node */
> > + if (WARN_ON(count > 1))
> > + return -EINVAL;
> > +
> > + np = of_get_next_available_child(pnode, NULL);
> > + if (WARN_ON(!np))
> > + return -ENODEV;
> > +
> > + BUG_ON(snprintf(compat, sizeof(compat), "virtio,%x", dev->id.device) >=
> > + sizeof(compat));
> > +
> > + if (!of_device_is_compatible(np, compat)) {
>
>
> This broke powerpc/pseries as there these virtio devices are PCI so
> there is no "compat" - PCI vendor id/device ids play role of "compat".
> Thanks,
Hmm now that you say this I wonder why do we bother
with this check, too. When can this be invoked for something
that is not a virtio device? And is it enough to just
skip of_node initialization then?
>
>
>
> > + ret = -EINVAL;
So basically ret = 0 above?
> > + goto out;
> > + }
> > +
> > + dev->dev.of_node = np;
> > + return 0;
> > +
> > +out:
> > + of_node_put(np);
> > + return ret;
> > +}
> > +
> > /**
> > * register_virtio_device - register virtio device
> > * @dev : virtio device to be registered
> > @@ -343,6 +384,10 @@ int register_virtio_device(struct virtio_device *dev)
> > dev->index = err;
> > dev_set_name(&dev->dev, "virtio%u", dev->index);
> >
> > + err = virtio_device_of_init(dev);
> > + if (err)
> > + goto out_ida_remove;
> > +
> > spin_lock_init(&dev->config_lock);
> > dev->config_enabled = false;
> > dev->config_change_pending = false;
> > @@ -362,10 +407,16 @@ int register_virtio_device(struct virtio_device *dev)
> > */
> > err = device_add(&dev->dev);
> > if (err)
> > - ida_simple_remove(&virtio_index_ida, dev->index);
> > + goto out_of_node_put;
> > +
> > + return 0;
> > +
> > +out_of_node_put:
> > + of_node_put(dev->dev.of_node);
> > +out_ida_remove:
> > + ida_simple_remove(&virtio_index_ida, dev->index);
> > out:
> > - if (err)
> > - virtio_add_status(dev, VIRTIO_CONFIG_S_FAILED);
> > + virtio_add_status(dev, VIRTIO_CONFIG_S_FAILED);
> > return err;
> > }
> > EXPORT_SYMBOL_GPL(register_virtio_device);
> >
>
> --
> Alexey
next prev parent reply other threads:[~2021-09-13 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 4:51 [PATCH V3 0/5] virtio: Add virtio-device bindings Viresh Kumar
2021-07-26 4:51 ` [PATCH V3 1/5] dt-bindings: virtio: Add binding for virtio devices Viresh Kumar
2021-07-26 14:57 ` Rob Herring
2021-07-26 15:53 ` Arnd Bergmann
2021-07-26 20:36 ` Rob Herring
2021-07-26 21:20 ` Arnd Bergmann
2021-07-27 5:09 ` Viresh Kumar
2021-07-26 4:51 ` [PATCH V3 2/5] dt-bindings: i2c: Add bindings for i2c-virtio Viresh Kumar
2021-07-26 8:06 ` Arnd Bergmann
2021-07-26 8:11 ` Arnd Bergmann
2021-07-26 9:21 ` Viresh Kumar
2021-07-26 15:06 ` Rob Herring
2021-07-26 4:51 ` [PATCH V3 3/5] dt-bindings: gpio: Add bindings for gpio-virtio Viresh Kumar
2021-07-26 8:13 ` Arnd Bergmann
2021-07-26 15:11 ` Rob Herring
2021-07-26 4:51 ` [PATCH V3 4/5] uapi: virtio_ids: Sync ids with specification Viresh Kumar
2021-07-26 4:51 ` [PATCH V3 5/5] virtio: Bind virtio device to device-tree node Viresh Kumar
2021-09-13 9:19 ` Alexey Kardashevskiy
2021-09-13 9:45 ` Michael S. Tsirkin [this message]
2021-09-13 10:27 ` Alexey Kardashevskiy
2021-09-13 14:49 ` Guenter Roeck
2021-09-13 16:19 ` Guenter Roeck
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=20210913053816-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aik@ozlabs.ru \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bill.mills@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
/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).