[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83da19cc-a140-406a-bdac-e6d2bdcc9794@linaro.org>
Date: Thu, 25 Jan 2024 11:54:46 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Oleksij Rempel <o.rempel@...gutronix.de>,
Sebastian Reichel <sre@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: kernel@...gutronix.de, linux-kernel@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>, Zhang Rui <rui.zhang@...el.com>,
Lukasz Luba <lukasz.luba@....com>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, Søren Andersen <san@...v.dk>
Subject: Re: [PATCH v2 2/8] dt-bindings: power: reset: add generic PSCRR
binding trackers
On 24/01/2024 13:21, Oleksij Rempel wrote:
> Add binding for Power State Change Reason Recording (PSCRR) subsystem
>
> Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
> ---
> .../bindings/power/reset/pscrr.yaml | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/power/reset/pscrr.yaml
>
> diff --git a/Documentation/devicetree/bindings/power/reset/pscrr.yaml b/Documentation/devicetree/bindings/power/reset/pscrr.yaml
> new file mode 100644
> index 000000000000..c8738b4930fe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/reset/pscrr.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/reset/pscrr.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Power State Change Reason (PSCR)
Missing final R?
> +
> +maintainers:
> + - Oleksij Rempel <o.rempel@...gutronix.de>
> +
> +description: Binding for devices responsible to store reasons for power state
Line break after description:
> + changes such as reboot and power-off. Reasons like unknown, under voltage,
> + and over temperature are captured for diagnostic or automatic recovery
> + purposes.
> +
> +properties:
> + pscr-under-voltage:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Value to indicate an under-voltage condition of a system critical
> + regulator as the reason for the power state change.
I don't understand how it is supposed to work... unless you wrote
binding for drivers. For drivers it would make sense, but that's another
problem: binding is not for drivers.
You also did not present here DTS with any actual device doing this. You
just added a driver...
Best regards,
Krzysztof
Powered by blists - more mailing lists