From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Alain Volmat <avolmat@me.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: soc: sti: add STi platform syscon
Date: Wed, 16 Aug 2023 09:45:54 +0200 [thread overview]
Message-ID: <ce0a160e-a666-5b34-b7b7-cbd18c480e58@foss.st.com> (raw)
In-Reply-To: <20230213185633.15187-2-avolmat@me.com>
On 2/13/23 19:56, Alain Volmat wrote:
> Add DT schema of STi platform syscon
>
> Signed-off-by: Alain Volmat <avolmat@me.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> v3: correct subject line arm -> soc
>
> v2: update wording of commit log
> reorder compatible enum
> update example within the binding file
> .../bindings/soc/sti/st,sti-syscon.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/sti/st,sti-syscon.yaml
>
> diff --git a/Documentation/devicetree/bindings/soc/sti/st,sti-syscon.yaml b/Documentation/devicetree/bindings/soc/sti/st,sti-syscon.yaml
> new file mode 100644
> index 000000000000..5f97d9ff17fb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/sti/st,sti-syscon.yaml
> @@ -0,0 +1,46 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/sti/st,sti-syscon.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: STMicroelectronics STi platform sysconfig
> +
> +maintainers:
> + - Patrice Chotard <patrice.chotard@foss.st.com>
> +
> +description: |
> + Binding for the various sysconfig nodes used within the STi
> + platform device-tree to point to some common configuration
> + registers used by other nodes.
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - st,stih407-core-syscfg
> + - st,stih407-flash-syscfg
> + - st,stih407-front-syscfg
> + - st,stih407-lpm-syscfg
> + - st,stih407-rear-syscfg
> + - st,stih407-sbc-reg-syscfg
> + - st,stih407-sbc-syscfg
> + - const: syscon
> +
> + reg:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + syscfg_sbc: syscon@9620000 {
> + compatible = "st,stih407-sbc-syscfg", "syscon";
> + reg = <0x9620000 0x1000>;
> + };
> +
> +...
Applied on sti-next
Thanks
Patrice
next prev parent reply other threads:[~2023-08-16 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 18:56 [PATCH v3 0/2] dt-bindings: sti: updates for STi platform Alain Volmat
2023-02-13 18:56 ` [PATCH v3 1/2] dt-bindings: soc: sti: add STi platform syscon Alain Volmat
2023-08-16 7:45 ` Patrice CHOTARD [this message]
2023-02-13 18:56 ` [PATCH v3 2/2] dt-bindings: arm: sti: add STi boards and remove stih415/stih416 Alain Volmat
2023-02-14 9:45 ` Krzysztof Kozlowski
2023-08-16 7:46 ` Patrice CHOTARD
2023-04-18 20:25 ` [PATCH v3 0/2] dt-bindings: sti: updates for STi platform Alain Volmat
2023-04-19 7:44 ` 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=ce0a160e-a666-5b34-b7b7-cbd18c480e58@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=avolmat@me.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).