LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: "Jason Wang" <jasowang@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Bill Mills" <bill.mills@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Enrico Weigelt, metux IT consult" <info@metux.net>,
	"Jie Deng" <jie.deng@intel.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH V4 3/5] dt-bindings: gpio: Add bindings for gpio-virtio
Date: Tue, 3 Aug 2021 10:00:14 +0530	[thread overview]
Message-ID: <20210803043014.paskwghdio6azplp@vireshk-i7> (raw)
In-Reply-To: <YQhKKyPmOUE8z+US@robh.at.kernel.org>

On 02-08-21, 13:40, Rob Herring wrote:
> Humm, how does one implement interrupts without a parent interrupt? It 
> uses the parent virtio,mmio interrupt?

Kind of, yeah, but not necessarily.

The interrupt information is passed over buffers shared between host and guest.
Now the guest may process the buffers when it receives a notification from the
host, that will be at downpath of an interrupt for virtio,mmio. Or the guest may
poll on the virtqueue and process any buffers as soon as they are made
available, no interrupts then.

-- 
viresh

  reply	other threads:[~2021-08-03  4:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  5:23 [PATCH V4 0/5] virtio: Add virtio-device bindings Viresh Kumar
2021-07-27  5:23 ` [PATCH V4 1/5] dt-bindings: virtio: Add binding for virtio devices Viresh Kumar
2021-07-27  7:51   ` Arnd Bergmann
2021-08-02 19:40   ` Rob Herring
2021-07-27  5:23 ` [PATCH V4 2/5] dt-bindings: i2c: Add bindings for i2c-virtio Viresh Kumar
2021-08-02 19:41   ` Rob Herring
2021-07-27  5:23 ` [PATCH V4 3/5] dt-bindings: gpio: Add bindings for gpio-virtio Viresh Kumar
2021-08-02 19:40   ` Rob Herring
2021-08-03  4:30     ` Viresh Kumar [this message]
2021-08-03 15:47       ` Rob Herring
2021-08-04  3:49         ` Viresh Kumar
2021-07-27  5:23 ` [PATCH V4 4/5] uapi: virtio_ids: Sync ids with specification Viresh Kumar
2021-07-27  5:23 ` [PATCH V4 5/5] virtio: Bind virtio device to device-tree node Viresh Kumar
2021-08-04  3:56 ` [PATCH V4 0/5] virtio: Add virtio-device bindings Viresh Kumar
2021-08-11  5:38   ` Viresh Kumar
2021-08-31  5:31 ` Viresh Kumar
2021-08-31 14:25   ` Michael S. Tsirkin

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=20210803043014.paskwghdio6azplp@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=bill.mills@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=info@metux.net \
    --cc=jasowang@redhat.com \
    --cc=jean-philippe@linaro.org \
    --cc=jie.deng@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=robh@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=virtualization@lists.linux-foundation.org \
    --subject='Re: [PATCH V4 3/5] dt-bindings: gpio: Add bindings for gpio-virtio' \
    /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

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).