From: Minghao Xue <quic_mingxue@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
<mst@redhat.com>, <jasowang@redhat.com>, <quic_ztu@quicinc.com>,
<robh+dt@kernel.org>, <virtualization@lists.linux-foundation.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: virtio: mmio: add optional virtio,wakeup property
Date: Tue, 22 Mar 2022 14:19:56 +0800 [thread overview]
Message-ID: <20220322061956.GA1441@mingxue-gv.qualcomm.com> (raw)
In-Reply-To: <d4d69acd-72d3-dfe1-9a11-d6590d2d90d8@kernel.org>
Hi Krzysztof,
Thanks for your comment. First of all, which "generic wakeup-source
property" do you mean? Could you give an example? I find "wakeup-source"
property in several binding files. Are you pointing to this? As my
understanding, there is no standard naming rule about the property of
each driver right? Currently, there's no virtio-mmio driver using this.
Anyway, I can modify my patch, if you prefer "wakeup-source".
Regards,
Minghao
On Fri, Mar 18, 2022 at 02:40:29PM +0100, Krzysztof Kozlowski wrote:
> On 18/03/2022 03:10, Minghao Xue wrote:
> > Hi Jean and folks,
> > This is just an optional flag which could be used on an embedded system.
> > For example, if we want to use an virtio-input device as a virtual power
> > key to wake up the virtual machine, we can set this flag in the device
> > tree.
> > Currently, virio-mmio driver does not implement suspend/resume
> > callback(maybe no need). So we want to check this flag and call
> > enable_irq_wake() accordingly in vm_find_vqs().
>
> There is a generic wakeup-source property. How is this one different
> that you need a separate one?
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-03-22 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1646733156-19333-1-git-send-email-quic_mingxue@quicinc.com>
[not found] ` <20220317063515.GA30789@mingxue-gv.qualcomm.com>
[not found] ` <YjMJ32SFXTLCuaRY@myrica>
2022-03-18 2:10 ` Minghao Xue
2022-03-18 13:40 ` Krzysztof Kozlowski
2022-03-22 6:19 ` Minghao Xue [this message]
2022-03-22 8:38 ` Krzysztof Kozlowski
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=20220322061956.GA1441@mingxue-gv.qualcomm.com \
--to=quic_mingxue@quicinc.com \
--cc=devicetree@vger.kernel.org \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=quic_ztu@quicinc.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®