From: Rob Herring <robh@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: devicetree@vger.kernel.org, tony@atomide.com,
p.zabel@pengutronix.de, ssantosh@kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 01/10] dt-bindings: omap: add new binding for PRM instances
Date: Mon, 02 Sep 2019 14:39:16 +0100 [thread overview]
Message-ID: <20190902042631.GA22055@bogus> (raw)
In-Reply-To: <20190830121816.30034-2-t-kristo@ti.com>
On Fri, Aug 30, 2019 at 03:18:07PM +0300, Tero Kristo wrote:
> Add new binding for OMAP PRM (Power and Reset Manager) instances. Each
> of these will act as a power domain controller and potentially as a reset
> provider.
>
Converting this to schema would be nice.
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> .../devicetree/bindings/arm/omap/prm-inst.txt | 31 +++++++++++++++++++
bindings/reset/
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/omap/prm-inst.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/omap/prm-inst.txt b/Documentation/devicetree/bindings/arm/omap/prm-inst.txt
> new file mode 100644
> index 000000000000..7c7527c37734
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/omap/prm-inst.txt
> @@ -0,0 +1,31 @@
> +OMAP PRM instance bindings
> +
> +Power and Reset Manager is an IP block on OMAP family of devices which
> +handle the power domains and their current state, and provide reset
> +handling for the domains and/or separate IP blocks under the power domain
> +hierarchy.
> +
> +Required properties:
> +- compatible: Must be one of:
> + "ti,am3-prm-inst"
> + "ti,am4-prm-inst"
> + "ti,omap4-prm-inst"
> + "ti,omap5-prm-inst"
> + "ti,dra7-prm-inst"
'-inst' seems a bit redundant.
> +- reg: Contains PRM instance register address range
> + (base address and length)
> +
> +Optional properties:
> +- #reset-cells: Should be 1 if the PRM instance in question supports resets.
> +- clocks: Associated clocks for the reset signals if any. Certain reset
> + signals can't be toggled properly without functional clock
> + being active for them.
> +
> +Example:
> +
> +prm_dsp2: prm@1b00 {
reset-controller@...
> + compatible = "ti,dra7-prm-inst";
> + reg = <0x1b00 0x40>;
> + #reset-cells = <1>;
> + clocks = <&dsp2_clkctrl DRA7_DSP2_MMU0_DSP2_CLKCTRL 0>;
> +};
> --
> 2.17.1
>
> --
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2019-09-02 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 12:18 [PATCHv3 00/10] soc: ti: add OMAP PRM driver (for reset) Tero Kristo
2019-08-30 12:18 ` [PATCHv3 01/10] dt-bindings: omap: add new binding for PRM instances Tero Kristo
2019-09-02 13:39 ` Rob Herring [this message]
2019-09-03 7:25 ` Tero Kristo
2019-09-03 8:10 ` Rob Herring
2019-09-03 8:14 ` Tero Kristo
2019-09-03 13:16 ` Tony Lindgren
2019-09-03 13:25 ` Philipp Zabel
2019-09-03 13:19 ` Adam Ford
2019-09-03 13:50 ` Tero Kristo
2019-09-06 10:35 ` [PATCHv4 " Tero Kristo
2019-09-06 12:56 ` Rob Herring
2019-09-06 15:36 ` Tony Lindgren
2019-09-06 20:02 ` Tero Kristo
2019-08-30 12:18 ` [PATCHv3 02/10] soc: ti: add initial PRM driver with reset control support Tero Kristo
2019-08-30 12:18 ` [PATCHv3 03/10] soc: ti: omap-prm: poll for reset complete during de-assert Tero Kristo
2019-08-30 12:18 ` [PATCHv3 04/10] soc: ti: omap-prm: add support for denying idle for reset clockdomain Tero Kristo
2019-08-30 12:18 ` [PATCHv3 05/10] soc: ti: omap-prm: sync func clock status with resets Tero Kristo
2019-08-30 12:18 ` [PATCHv3 06/10] soc: ti: omap-prm: add omap4 PRM data Tero Kristo
2019-08-30 12:18 ` [PATCHv3 07/10] soc: ti: omap-prm: add data for am33xx Tero Kristo
2019-08-30 12:18 ` [PATCHv3 08/10] soc: ti: omap-prm: add dra7 PRM data Tero Kristo
2019-08-30 12:18 ` [PATCHv3 09/10] soc: ti: omap-prm: add am4 " Tero Kristo
2019-08-30 12:18 ` [PATCHv3 10/10] soc: ti: omap-prm: add omap5 " Tero Kristo
2019-08-30 16:50 ` [PATCHv3 00/10] soc: ti: add OMAP PRM driver (for reset) santosh.shilimkar
2019-09-02 6:50 ` Tero Kristo
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=20190902042631.GA22055@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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).