[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200728191842.GB2778962@bogus>
Date: Tue, 28 Jul 2020 13:18:42 -0600
From: Rob Herring <robh@...nel.org>
To: Daniel Palmer <daniel@...f.com>
Cc: soc@...nel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
arnd@...db.de
Subject: Re: [PATCH v2 1/9] dt-bindings: arm: mstar: Add binding details for
mstar,pmsleep
On Tue, Jul 28, 2020 at 07:03:13PM +0900, Daniel Palmer wrote:
> This adds a YAML description of the pmsleep node used by
> MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer <daniel@...f.com>
> ---
> .../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/mstar/mstar,pmsleep.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/mstar/mstar,pmsleep.yaml b/Documentation/devicetree/bindings/arm/mstar/mstar,pmsleep.yaml
> new file mode 100644
> index 000000000000..ef78097a7087
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/mstar/mstar,pmsleep.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2020 thingy.jp.
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/arm/mstar/mstar,pmsleep.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: MStar/SigmaStar Armv7 SoC pmsleep register region
> +
> +maintainers:
> + - Daniel Palmer <daniel@...ngy.jp>
> +
> +description: |
> + MStar/Sigmastar's Armv7 SoCs contain a region of registers that are
> + in the always on domain that the vendor code calls the "pmsleep" area.
> +
> + This area contains registers and bits for a broad range of functionality
> + ranging from registers that control going into deep sleep to bits that
> + turn things like the internal temperature sensor on and off.
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - mstar,pmsleep
Needs to be SoC specific. Random collections of bits are never
'standard' from one SoC to the next.
If your never going to have child nodes, then you can just add the
compatible to syscon.yaml.
> + - const: syscon
> +
> + reg:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + pmsleep: pmsleep@...0 {
> + compatible = "mstar,pmsleep", "syscon";
> + reg = <0x0x1c00 0x100>;
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 991814ea6f76..432fcc867ed6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2140,6 +2140,7 @@ L: linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
> S: Maintained
> W: http://linux-chenxing.org/
> F: Documentation/devicetree/bindings/arm/mstar.yaml
> +F: Documentation/devicetree/bindings/arm/mstar/*
> F: arch/arm/boot/dts/infinity*.dtsi
> F: arch/arm/boot/dts/mercury*.dtsi
> F: arch/arm/boot/dts/mstar-v7.dtsi
> --
> 2.27.0
>
Powered by blists - more mailing lists