From: "Pali Rohár" <pali@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: power: reset: restart-handler: add common schema
Date: Wed, 7 Sep 2022 18:32:18 +0200 [thread overview]
Message-ID: <20220907163218.aja4pazw3sbxnoop@pali> (raw)
In-Reply-To: <20220907123630.57383-1-krzysztof.kozlowski@linaro.org>
On Wednesday 07 September 2022 14:36:30 Krzysztof Kozlowski wrote:
> Add common schema for restart and shutdown handlers, so they all use
> same meaning of "priority" field. The Linux drivers already have this
> property and some systems want to customize it per-board in DTS.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> See also:
> https://lore.kernel.org/all/8fe93da3-f768-16ae-7025-1cfa97a42b27@linaro.org/
> https://lore.kernel.org/all/20220831081715.14673-1-pali@kernel.org/
> ---
> .../bindings/power/reset/gpio-restart.yaml | 13 ++------
> .../bindings/power/reset/restart-handler.yaml | 30 +++++++++++++++++++
> 2 files changed, 33 insertions(+), 10 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/power/reset/restart-handler.yaml
>
> diff --git a/Documentation/devicetree/bindings/power/reset/gpio-restart.yaml b/Documentation/devicetree/bindings/power/reset/gpio-restart.yaml
> index a72d5c721516..d3d18e0f5db3 100644
> --- a/Documentation/devicetree/bindings/power/reset/gpio-restart.yaml
> +++ b/Documentation/devicetree/bindings/power/reset/gpio-restart.yaml
> @@ -25,6 +25,9 @@ description: >
> inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the
> restart handler completes allowing other restart handlers to be attempted.
>
> +allOf:
> + - $ref: restart-handler.yaml#
> +
> properties:
> compatible:
> const: gpio-restart
> @@ -41,16 +44,6 @@ properties:
> in its inactive state.
>
> priority:
> - $ref: /schemas/types.yaml#/definitions/uint32
> - description: |
> - A priority ranging from 0 to 255 (default 129) according to the following guidelines:
> -
> - 0: Restart handler of last resort, with limited restart capabilities.
> - 128: Default restart handler; use if no other restart handler is expected to be available,
> - and/or if restart functionality is sufficient to restart the entire system.
> - 255: Highest priority restart handler, will preempt all other restart handlers.
> - minimum: 0
> - maximum: 255
> default: 129
>
> active-delay:
> diff --git a/Documentation/devicetree/bindings/power/reset/restart-handler.yaml b/Documentation/devicetree/bindings/power/reset/restart-handler.yaml
> new file mode 100644
> index 000000000000..f5d22ca0cd45
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/reset/restart-handler.yaml
> @@ -0,0 +1,30 @@
> +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/reset/restart-handler.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Restart and shutdown handler generic binding
> +
> +maintainers:
> + - Sebastian Reichel <sre@kernel.org>
> +
> +description:
> + Restart and shutdown handler device is responsible for powering off the
> + system, e.g. my cutting off the power. System might have several restart
> + handlers, which usually are tried from most precise to last resort.
> +
> +properties:
> + priority:
> + $ref: /schemas/types.yaml#/definitions/uint32
IIRC priority is signed integer number, not unsigned.
> + description: |
> + A priority ranging from 0 to 255 according to the following guidelines::
> + 0: Restart handler of last resort, with limited restart capabilities.
> + 128: Typical, default restart handler; use if no other restart handler
> + is expected to be available, and/or if restart functionality is
> + sufficient to restart the entire system.
> + 255: Highest priority restart handler, will preempt all other restart handlers.
> + minimum: 0
> + maximum: 255
And IIRC also other values (above 255 or below 0) are allowed for tuning
two "highest" or two "last resort" handlers.
This needs to be checked / tested to ensure that new schema is not incorrect.
> +
> +additionalProperties: true
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-09-07 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 12:36 Krzysztof Kozlowski
2022-09-07 16:32 ` Pali Rohár [this message]
2022-09-08 7:28 ` Krzysztof Kozlowski
2022-09-11 12:27 ` Sebastian Reichel
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=20220907163218.aja4pazw3sbxnoop@pali \
--to=pali@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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 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®