From: Krzysztof Kozlowski <krzk@kernel.org>
To: hrishabh.rajput@oss.qualcomm.com,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Add binding for gunyah watchdog
Date: Thu, 4 Sep 2025 11:52:32 +0200 [thread overview]
Message-ID: <ea295ff6-5395-4470-afc2-76e5e2dc9fb5@kernel.org> (raw)
In-Reply-To: <20250903-gunyah_watchdog-v1-1-3ae690530e4b@oss.qualcomm.com>
On 03/09/2025 21:33, Hrishabh Rajput via B4 Relay wrote:
> From: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
>
> The Gunyah Hypervisor applies a devicetree overlay providing the
> pretimeout interrupt for the Gunyah Watchdog that it will be using to
> notify watchdog's pretimeout event. Add the DT bindings that Gunyah
> adheres to for the hypervisor and watchdog.
Wasn't tested, so limited review.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
A nit, subject: drop second/last, redundant "bindings". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.17-rc3/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
>
> Signed-off-by: Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> ---
> .../bindings/watchdog/qcom,gh-watchdog.yaml | 76 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 77 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/watchdog/qcom,gh-watchdog.yaml b/Documentation/devicetree/bindings/watchdog/qcom,gh-watchdog.yaml
> new file mode 100644
> index 000000000000..bde8438c6242
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/qcom,gh-watchdog.yaml
> @@ -0,0 +1,76 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/watchdog/qcom,gh-watchdog.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Gunyah Virtual Watchdog
> +
> +maintainers:
> + - Hrishabh Rajput <hrishabh.rajput@oss.qualcomm.com>
> +
> +description: |+
> + The Gunyah Hypervisor provides an SMC-based watchdog interface for its virtual
> + machines. The virtual machines use this information to determine the
> + pretimeout IRQ which the hypervisor will be using to communicate pretimeout
> + event.
> + See also: [1]
> +
> + [1]: https://github.com/quic/gunyah-resource-manager/blob/1b23ceb0dfa010b3b6b5a5f7a4ec1e95b93ab99d/src/vm_creation/dto_construct.c#L519
> +
> +properties:
> + compatible:
> + allOf:
> + - const: gunyah-hypervisor
> + - const: simple-bus
What? No.
Don't create patches with AI.
> +
> + "#address-cells":
> + description: Number of cells needed to represent 64-bit capability IDs.
> + const: 2
> +
> + "#size-cells":
> + description: must be 0, because capability IDs are not memory address
> + ranges and do not have a size.
> + const: 0
> +
> +patternProperties:
> + "^gh-watchdog":
I could not express more: NAK. Does not match any DT style. Please do
some internal reviews first. This patch does not meet minimum quality
criteria for public posting.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 9:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 19:33 [PATCH 0/2] Add support for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-09-03 19:33 ` [PATCH 1/2] dt-bindings: Add binding for gunyah watchdog Hrishabh Rajput via B4 Relay
2025-09-03 23:27 ` Rob Herring (Arm)
2025-09-04 9:52 ` Krzysztof Kozlowski [this message]
2025-09-04 10:16 ` Pavan Kondeti
2025-09-04 10:49 ` Krzysztof Kozlowski
2025-09-04 10:59 ` Krzysztof Kozlowski
2025-09-04 12:29 ` Pavan Kondeti
2025-09-04 13:07 ` Hrishabh Rajput
2025-09-04 13:17 ` Krzysztof Kozlowski
2025-09-04 19:03 ` Hrishabh Rajput
2025-09-03 19:34 ` [PATCH 2/2] watchdog: Add driver for Gunyah Watchdog Hrishabh Rajput via B4 Relay
2025-09-03 20:13 ` Bjorn Andersson
2025-09-04 11:40 ` Hrishabh Rajput
2025-09-04 13:47 ` Bjorn Andersson
2025-09-04 17:11 ` Pavan Kondeti
2025-09-05 9:19 ` Konrad Dybcio
2025-09-04 0:10 ` [PATCH 0/2] Add support " Rob Herring
2025-09-04 11:31 ` Konrad Dybcio
2025-09-04 22:51 ` Rob Herring
2025-09-05 0:00 ` Pavan Kondeti
2025-09-05 10:18 ` Konrad Dybcio
2025-09-08 5:49 ` Pavan Kondeti
2025-09-12 11:16 ` Konrad Dybcio
2025-09-04 14:39 ` Hrishabh Rajput
2025-09-04 7:13 ` Neil Armstrong
2025-09-04 9:18 ` Pavan Kondeti
2025-09-04 13:53 ` Bjorn Andersson
2025-09-04 17:05 ` Pavan Kondeti
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=ea295ff6-5395-4470-afc2-76e5e2dc9fb5@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hrishabh.rajput@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.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).