From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>
Cc: linux-actions@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: power: actions,owl-sps: convert to YAML
Date: Wed, 11 Dec 2024 19:23:53 +0200 [thread overview]
Message-ID: <f395a019-800f-49a4-a3cc-28efafc4faa9@gmail.com> (raw)
In-Reply-To: <20241103123917.2890436-1-ivo.ivanov.ivanov1@gmail.com>
On 11/3/24 14:39, Ivaylo Ivanov wrote:
> Convert the Actions Semi Owl Smart Power System (SPS) bindings to DT
> schema.
>
> Changes during conversion:
> - Add a description
>
> Signed-off-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> v2: add r-b tag from Krzysztof Kozlowski <krzk@kernel.org>
> v2: update commit message to be accurate (Krzysztof)
> v2: don't preserve formatting in the description (Krzysztof)
> v2: add a blank line after additionalProperties (Krzysztof)
> ---
> .../bindings/power/actions,owl-sps.txt | 21 --------
> .../bindings/power/actions,owl-sps.yaml | 51 +++++++++++++++++++
> MAINTAINERS | 2 +-
> 3 files changed, 52 insertions(+), 22 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/power/actions,owl-sps.txt
> create mode 100644 Documentation/devicetree/bindings/power/actions,owl-sps.yaml
>
> diff --git a/Documentation/devicetree/bindings/power/actions,owl-sps.txt b/Documentation/devicetree/bindings/power/actions,owl-sps.txt
BUMP - what happened with the patch? Been a month now and
all the other ones have been applied.
Best regards, Ivo.
> deleted file mode 100644
> index a3571937b..000000000
> --- a/Documentation/devicetree/bindings/power/actions,owl-sps.txt
> +++ /dev/null
> @@ -1,21 +0,0 @@
> -Actions Semi Owl Smart Power System (SPS)
> -
> -Required properties:
> -- compatible : "actions,s500-sps" for S500
> - "actions,s700-sps" for S700
> - "actions,s900-sps" for S900
> -- reg : Offset and length of the register set for the device.
> -- #power-domain-cells : Must be 1.
> - See macros in:
> - include/dt-bindings/power/owl-s500-powergate.h for S500
> - include/dt-bindings/power/owl-s700-powergate.h for S700
> - include/dt-bindings/power/owl-s900-powergate.h for S900
> -
> -
> -Example:
> -
> - sps: power-controller@b01b0100 {
> - compatible = "actions,s500-sps";
> - reg = <0xb01b0100 0x100>;
> - #power-domain-cells = <1>;
> - };
> diff --git a/Documentation/devicetree/bindings/power/actions,owl-sps.yaml b/Documentation/devicetree/bindings/power/actions,owl-sps.yaml
> new file mode 100644
> index 000000000..0855d82f3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/actions,owl-sps.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/actions,owl-sps.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Actions Semi Owl Smart Power System (SPS)
> +
> +maintainers:
> + - Andreas Färber <afaerber@suse.de>
> +
> +description:
> + Actions Semi Owl SoCs feature a Smart Power System (SPS) that manages power
> + domains to optimize power usage across various hardware blocks. Each power
> + domain corresponds to a specific hardware block and is represented by a bit
> + in the power control register and an acknowledgment bit, which is then
> + translated into a corresponding voltage on a rail.
> +
> +properties:
> + compatible:
> + enum:
> + - actions,s500-sps
> + - actions,s700-sps
> + - actions,s900-sps
> +
> + reg:
> + maxItems: 1
> +
> + "#power-domain-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - "#power-domain-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/power/owl-s500-powergate.h>
> + soc {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + sps: power-controller@b01b0100 {
> + compatible = "actions,s500-sps";
> + reg = <0xb01b0100 0x100>;
> + #power-domain-cells = <1>;
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 76ea65128..420d06d37 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2023,7 +2023,7 @@ F: Documentation/devicetree/bindings/interrupt-controller/actions,owl-sirq.yaml
> F: Documentation/devicetree/bindings/mmc/owl-mmc.yaml
> F: Documentation/devicetree/bindings/net/actions,owl-emac.yaml
> F: Documentation/devicetree/bindings/pinctrl/actions,*
> -F: Documentation/devicetree/bindings/power/actions,owl-sps.txt
> +F: Documentation/devicetree/bindings/power/actions,owl-sps.yaml
> F: Documentation/devicetree/bindings/timer/actions,owl-timer.yaml
> F: arch/arm/boot/dts/actions/
> F: arch/arm/mach-actions/
prev parent reply other threads:[~2024-12-11 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 12:39 [PATCH v2] dt-bindings: power: actions,owl-sps: convert to YAML Ivaylo Ivanov
2024-12-11 17:23 ` Ivaylo Ivanov [this message]
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=f395a019-800f-49a4-a3cc-28efafc4faa9@gmail.com \
--to=ivo.ivanov.ivanov1@gmail.com \
--cc=afaerber@suse.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@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