From: Rob Herring <robh@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
"Marek Behún" <kabel@kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: reset: syscon-reboot: Add priority property
Date: Mon, 22 Aug 2022 07:47:28 -0500 [thread overview]
Message-ID: <20220822124728.GA3641041-robh@kernel.org> (raw)
In-Reply-To: <20220820102925.29476-1-pali@kernel.org>
On Sat, Aug 20, 2022 at 12:29:23PM +0200, Pali Rohár wrote:
> This new optional priority property allows to specify custom priority level
> of reset device. Default level was always 192.
Why do we need/want this? What problem does it solve?
> Signed-off-by: Pali Rohár <pali@kernel.org>
> ---
> .../devicetree/bindings/power/reset/syscon-reboot.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml b/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml
> index da2509724812..d905133aab27 100644
> --- a/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml
> +++ b/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml
> @@ -42,6 +42,10 @@ properties:
> $ref: /schemas/types.yaml#/definitions/uint32
> description: The reset value written to the reboot register (32 bit access).
>
> + priority:
A bit too generic for the name.
> + $ref: /schemas/types.yaml#/definitions/sint32
> + description: Priority level of this syscon reset device. Default 192.
default: 192
Though I'm not really sure about the whole concept of this in DT. Where
does 192 come from? Presumably if we have more than 1 reset device, then
'priority' is needed in multiple places. So you need a common schema
defining the property (as property types should be defined exactly
once) which this schema can reference.
Rob
next prev parent reply other threads:[~2022-08-22 12:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 10:29 [PATCH 1/3] dt-bindings: reset: syscon-reboot: Add priority property Pali Rohár
2022-08-20 10:29 ` [PATCH 2/3] power: reset: syscon-reboot: Add support for specifying priority Pali Rohár
2022-08-20 10:29 ` [PATCH 3/3] powerpc: dts: turris1x.dts: Set lower priority for CPLD syscon-reboot Pali Rohár
2022-08-21 20:21 ` [PATCH 1/3] dt-bindings: reset: syscon-reboot: Add priority property Rob Herring
2022-08-22 12:47 ` Rob Herring [this message]
2022-08-22 13:50 ` Pali Rohár
2022-09-02 20:37 ` Rob Herring
2022-09-07 12:27 ` Krzysztof Kozlowski
2022-08-30 23:00 ` [PATCH v2 " Pali Rohár
2022-08-30 23:00 ` [PATCH v2 2/3] power: reset: syscon-reboot: Add support for specifying priority Pali Rohár
2022-08-30 23:00 ` [PATCH v2 3/3] powerpc: dts: turris1x.dts: Set lower priority for CPLD syscon-reboot Pali Rohár
2022-08-31 7:31 ` [PATCH v2 1/3] dt-bindings: reset: syscon-reboot: Add priority property Krzysztof Kozlowski
2022-08-31 7:36 ` Pali Rohár
2022-08-31 7:52 ` Krzysztof Kozlowski
2022-08-31 8:17 ` [PATCH v3 " Pali Rohár
2022-08-31 8:17 ` [PATCH v3 2/3] power: reset: syscon-reboot: Add support for specifying priority Pali Rohár
2022-08-31 8:17 ` [PATCH v3 3/3] powerpc: dts: turris1x.dts: Set lower priority for CPLD syscon-reboot Pali Rohár
2022-09-07 12:38 ` [PATCH v3 1/3] dt-bindings: reset: syscon-reboot: Add priority property Krzysztof Kozlowski
2022-09-07 16:33 ` Pali Rohár
2022-09-08 7:26 ` Krzysztof Kozlowski
2022-12-26 11:45 ` [PATCH v4 " Pali Rohár
2022-12-26 11:45 ` [PATCH v4 2/3] power: reset: syscon-reboot: Add support for specifying priority Pali Rohár
2022-12-26 11:45 ` [PATCH v4 3/3] powerpc: dts: turris1x.dts: Set lower priority for CPLD syscon-reboot Pali Rohár
2023-02-09 0:10 ` Pali Rohár
2023-02-18 12:05 ` Pali Rohár
2023-02-20 0:55 ` Michael Ellerman
2022-12-26 12:02 ` [PATCH v4 1/3] dt-bindings: reset: syscon-reboot: Add priority property Krzysztof Kozlowski
2022-12-26 18:23 ` Rob Herring
2023-01-22 11:27 ` Pali Rohár
2023-02-03 12:16 ` Sebastian Reichel
2023-02-03 12:35 ` Krzysztof Kozlowski
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=20220822124728.GA3641041-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=pali@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;
as well as URLs for NNTP newsgroup(s).