[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4d69acd-72d3-dfe1-9a11-d6590d2d90d8@kernel.org>
Date: Fri, 18 Mar 2022 14:40:29 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Minghao Xue <quic_mingxue@...cinc.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>
Cc: mst@...hat.com, jasowang@...hat.com, quic_ztu@...cinc.com,
robh+dt@...nel.org, virtualization@...ts.linux-foundation.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: virtio: mmio: add optional virtio,wakeup
property
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
Powered by blists - more mailing lists