devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, aisheng.dong@nxp.com,
	l.stach@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V5 1/6] dt-bindings: soc: add i.MX93 SRC
Date: Mon, 18 Jul 2022 12:01:10 -0600	[thread overview]
Message-ID: <20220718180110.GA3252763-robh@kernel.org> (raw)
In-Reply-To: <20220711062452.3575032-2-peng.fan@oss.nxp.com>

On Mon, Jul 11, 2022 at 02:24:47PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Add bindings for i.MX93 System Reset Controller(SRC). SRC supports
> resets and power gating for mixes.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  .../bindings/soc/imx/fsl,imx93-src.yaml       | 95 +++++++++++++++++++
>  1 file changed, 95 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx93-src.yaml
> 
> diff --git a/Documentation/devicetree/bindings/soc/imx/fsl,imx93-src.yaml b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-src.yaml
> new file mode 100644
> index 000000000000..5eb22c993d59
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-src.yaml
> @@ -0,0 +1,95 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/imx/fsl,imx93-src.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP i.MX93 System Reset Controller
> +
> +maintainers:
> +  - Peng Fan <peng.fan@nxp.com>
> +
> +description: |
> +  The System Reset Controller (SRC) is responsible for the generation of
> +  all the system reset signals and boot argument latching.
> +
> +  Its main functions are as follows,
> +  - Deals with all global system reset sources from other modules,
> +    and generates global system reset.
> +  - Responsible for power gating of MIXs (Slices) and their memory
> +    low power control.
> +
> +properties:
> +  compatible:
> +    items:
> +      - const: fsl,imx93-src
> +      - const: syscon
> +
> +  reg:
> +    maxItems: 1
> +
> +  ranges: true
> +
> +  '#address-cells':
> +    const: 1
> +
> +  '#size-cells':
> +    const: 1
> +
> +patternProperties:
> +  "power-domain@[0-9a-f]+$":
> +    $ref: /schemas/power/power-domain.yaml#

No need to reference this as you have to define '#power-domain-cells' 
constraints anyways.

> +
> +    type: object
> +    properties:
> +      compatible:
> +        items:
> +          - const: fsl,imx93-src-slice
> +
> +      '#power-domain-cells':
> +        const: 0
> +
> +      reg:
> +        maxItems: 2

You need to define what each entry is.

> +
> +      clocks:
> +        description: |
> +          A number of phandles to clocks that need to be enabled
> +          during domain power-up sequencing to ensure reset
> +          propagation into devices located inside this power domain.
> +        minItems: 1
> +        maxItems: 5
> +
> +    required:
> +      - compatible
> +      - '#power-domain-cells'
> +      - reg
> +
> +required:
> +  - compatible
> +  - reg
> +  - ranges
> +  - '#address-cells'
> +  - '#size-cells'
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/clock/imx93-clock.h>
> +
> +    system-controller@44460000 {
> +        compatible = "fsl,imx93-src", "syscon";
> +        reg = <0x44460000 0x10000>;
> +        #address-cells = <1>;
> +        #size-cells = <1>;
> +        ranges;
> +
> +        mediamix: power-domain@0 {
> +            compatible = "fsl,imx93-src-slice";
> +            reg = <0x44462400 0x400>, <0x44465800 0x400>;
> +            #power-domain-cells = <0>;
> +            clocks = <&clk IMX93_CLK_MEDIA_AXI>,
> +                     <&clk IMX93_CLK_MEDIA_APB>;
> +        };
> +    };
> -- 
> 2.25.1
> 
> 

  reply	other threads:[~2022-07-18 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  6:24 [PATCH V5 0/6] imx: support i.MX93 SRC and mediamix blk ctrl Peng Fan (OSS)
2022-07-11  6:24 ` [PATCH V5 1/6] dt-bindings: soc: add i.MX93 SRC Peng Fan (OSS)
2022-07-18 18:01   ` Rob Herring [this message]
2022-07-11  6:24 ` [PATCH V5 2/6] dt-bindings: soc: add i.MX93 mediamix blk ctrl Peng Fan (OSS)
2022-07-11  6:24 ` [PATCH V5 3/6] soc: imx: add i.MX93 SRC power domain driver Peng Fan (OSS)
2022-07-11 22:03   ` Randy Dunlap
2022-07-15 15:17   ` kernel test robot
2022-07-15 19:02   ` kernel test robot
2022-07-11  6:24 ` [PATCH V5 4/6] soc: imx: add i.MX93 media blk ctrl driver Peng Fan (OSS)
2022-07-11  6:24 ` [PATCH V5 5/6] arm64: dts: imx93: add src node Peng Fan (OSS)
2022-07-11  6:24 ` [PATCH V5 6/6] arm64: dts: imx93: add mediamix blk ctrl node Peng Fan (OSS)

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=20220718180110.GA3252763-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).