From: Minghao Xue <quic_mingxue@quicinc.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: Minghao Xue <quic_mingxue@quicinc.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	<virtualization@lists.linux-foundation.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<quic_ztu@quicinc.com>
Subject: [PATCH v2 0/2] virtio_mmio: add support to set IRQ of a virtio device as wakeup source
Date: Fri, 10 Jun 2022 16:58:25 +0800	[thread overview]
Message-ID: <1654851507-13891-1-git-send-email-quic_mingxue@quicinc.com> (raw)
Hi,
Some systems want to set the interrupt of virtio_mmio device as a wakeup source of system.
This patch series add support for such use case. And it can be enbaled by adding "wakeup-source" property to the device tree.
Patch 1: Add an optional "wakeup-source" property into binding file of virtio_mmio device.
Patch 2: Set IRQ of virtio_mmio device as wakeup source in virtqueue initialization, if "wakeup-source" is set in the device tree.
Version 2 changes (mostly feedback from Krzysztof Kozlowski)
-rename property from "virtio,wakeup" to "wakeup-source"
Minghao Xue (2):
  dt-bindings: virtio: mmio: add optional wakeup-source property
  virtio_mmio: add support to set IRQ of a virtio device as wakeup
    source
 Documentation/devicetree/bindings/virtio/mmio.yaml | 4 ++++
 drivers/virtio/virtio_mmio.c                       | 3 +++
 2 files changed, 7 insertions(+)
-- 
2.7.4
next             reply	other threads:[~2022-06-10  8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  8:58 Minghao Xue [this message]
2022-06-10  8:58 ` [PATCH v2 1/2] dt-bindings: virtio: mmio: add optional wakeup-source property Minghao Xue
2022-06-10  8:58 ` [PATCH v2 2/2] virtio_mmio: add support to set IRQ of a virtio device as wakeup source Minghao Xue
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=1654851507-13891-1-git-send-email-quic_mingxue@quicinc.com \
    --to=quic_mingxue@quicinc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jasowang@redhat.com \
    --cc=jean-philippe@linaro.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;
as well as URLs for NNTP newsgroup(s).