From: Sebastian Ene <sebastianene@google.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Derek Kiernan <derek.kiernan@xilinx.com>,
Dragan Cvetic <dragan.cvetic@xilinx.com>,
Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org, qperret@google.com, will@kernel.org,
maz@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: vm-wdt: Add qemu,vm-watchdog compatible
Date: Thu, 28 Apr 2022 14:29:05 +0000 [thread overview]
Message-ID: <Ymqksfth+sj5JOWo@google.com> (raw)
In-Reply-To: <YmbonypWxzZJbjQ1@robh.at.kernel.org>
On Mon, Apr 25, 2022 at 01:29:51PM -0500, Rob Herring wrote:
> On Mon, Apr 25, 2022 at 01:42:05PM +0000, Sebastian Ene wrote:
> > The stall detection mechanism allows to configure the expiration
> > duration and the internal counter clock frequency measured in Hz.
> > Add these properties in the schema.
> >
> > Signed-off-by: Sebastian Ene <sebastianene@google.com>
> > ---
> > .../devicetree/bindings/misc/vm-wdt.yaml | 44 +++++++++++++++++++
> > 1 file changed, 44 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/misc/vm-wdt.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/misc/vm-wdt.yaml b/Documentation/devicetree/bindings/misc/vm-wdt.yaml
> > new file mode 100644
> > index 000000000000..cb7665a0c5af
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/misc/vm-wdt.yaml
> > @@ -0,0 +1,44 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/misc/vm-wdt.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: VM watchdog
> > +
> > +description: |
> > + This binding describes a CPU stall detector mechanism for virtual cpus.
> > +
> > +maintainers:
> > + - Sebastian Ene <sebastianene@google.com>
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - qemu,vm-watchdog
> > + clock:
Hi,
>
> 'clocks' is already a defined property and 'clock' is too close. It's
> also ambiguous what it is. 'clock-frequency' instead perhaps.
>
Yes, I think 'clock-frequency' is a better name. I will update it.
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + description: |
> > + The watchdog internal clock measure in Hz used to decrement the
> > + watchdog counter register on each tick.
> > + Defaults to 10 if unset.
> > + timeout-sec:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + description: |
> > + The watchdog expiration timeout measured in seconds.
> > + Defaults to 8 if unset.
> > +
> > +required:
> > + - compatible
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + watchdog {
> > + compatible = "qemu,vm-watchdog";
> > + clock = <10>;
> > + timeout-sec = <8>;
>
> How does one access this 'hardware'?
>
This is a MMIO device.
> Why does this need to be in DT?
>
> We have DT because h/w designers are incapable of making h/w
> discoverable. Why repeat that problem with s/w interfaces?
>
We need to have this one in the DT because in a secure VM we only load
trusted DT components.
> Rob
Thanks,
Sebastian
next prev parent reply other threads:[~2022-04-28 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 13:42 [PATCH v3 0/2] Detect stalls on guest vCPUS Sebastian Ene
2022-04-25 13:42 ` [PATCH v3 1/2] dt-bindings: vm-wdt: Add qemu,vm-watchdog compatible Sebastian Ene
2022-04-25 18:29 ` Rob Herring
2022-04-28 14:29 ` Sebastian Ene [this message]
2022-04-29 20:46 ` Rob Herring
2022-04-25 13:42 ` [PATCH v3 2/2] misc: Add a mechanism to detect stalls on guest vCPUs Sebastian Ene
2022-04-25 14:15 ` Greg Kroah-Hartman
2022-04-28 14:23 ` Sebastian Ene
2022-04-25 16:02 ` Randy Dunlap
2022-04-28 14:10 ` Sebastian Ene
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=Ymqksfth+sj5JOWo@google.com \
--to=sebastianene@google.com \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=qperret@google.com \
--cc=robh@kernel.org \
--cc=will@kernel.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 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.