From: Viresh Kumar <viresh.kumar@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "Jason Wang" <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
"Bill Mills" <bill.mills@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
virtio-dev@lists.oasis-open.org,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
stratos-dev@op-lists.linaro.org,
"Kent Gibson" <warthog618@gmail.com>,
"Marc Zyngier" <maz@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH V9] virtio-gpio: Add support for interrupts
Date: Thu, 14 Oct 2021 15:55:36 +0530 [thread overview]
Message-ID: <20211014102536.yoh4czkikw63cmoz@vireshk-i7> (raw)
In-Reply-To: <87o87rvrry.fsf@redhat.com>
On 14-10-21, 12:12, Cornelia Huck wrote:
> What triggers the device to configure the GPIO lines in that state? Is
> that something that it should already do when it decides to offer the
> feature bit?
Yes, it should be the state before negotiations start.
--
viresh
next prev parent reply other threads:[~2021-10-14 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 7:16 [PATCH V9] virtio-gpio: Add support for interrupts Viresh Kumar
2021-10-12 7:51 ` [virtio-dev] " Arnd Bergmann
2021-10-12 8:33 ` Viresh Kumar
2021-10-12 9:16 ` Arnd Bergmann
2021-10-12 9:31 ` Viresh Kumar
2021-10-14 10:12 ` [virtio-dev] " Cornelia Huck
2021-10-14 10:25 ` Viresh Kumar [this message]
2021-10-14 10:42 ` Cornelia Huck
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=20211014102536.yoh4czkikw63cmoz@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=arnd@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=bill.mills@linaro.org \
--cc=cohuck@redhat.com \
--cc=geert@linux-m68k.org \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=warthog618@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.