From: Tero Kristo <t-kristo@ti.com> To: Suman Anna <s-anna@ti.com>, Keerthy <j-keerthy@ti.com>, ssantosh@kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, robh+dt@kernel.org Cc: tony@atomide.com, devicetree@vger.kernel.org Subject: Re: [PATCH 1/8] dt-bindings: omap: add new binding for PRM instances Date: Tue, 20 Aug 2019 10:45:58 +0300 [thread overview] Message-ID: <c485156c-735f-40d3-d6a9-1b277e9c3d1d@ti.com> (raw) In-Reply-To: <b6506850-f4fc-43be-b5b7-b83cd77b5d66@ti.com> On 20.8.2019 0.28, Suman Anna wrote: > Hi Tero, > > On 8/19/19 4:28 AM, Tero Kristo wrote: >> On 08/08/2019 07:35, Keerthy wrote: >>> >>> >>> On 07/08/19 1:18 PM, 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. >>>> >>>> Signed-off-by: Tero Kristo <t-kristo@ti.com> >>>> --- >>>> .../devicetree/bindings/arm/omap/prm-inst.txt | 24 >>>> ++++++++++++++++++++++ >>>> 1 file changed, 24 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 0000000..e0ae87b >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/arm/omap/prm-inst.txt >>>> @@ -0,0 +1,24 @@ >>>> +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. > > So, I see that you are adding these as flat nodes directly under the prm > nodes where we have the clocks and clock_domains. Are you anticipating a > single DT node and/or driver managing both power-domains and resets? Single DT node + driver for both power-domains / resets. You can probably see from the driver code that the reset probing is called separately from the main probe function; power domain support should be added in similar manner under it. > >>>> + >>>> +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" > > What about OMAP2, OMAP3, DM814x, DM816x? OMAP2/3 architectures are slightly different beast to tackle, so planning to work on those later on. -Tero > > regards > Suman > >>>> +- reg: Contains PRM instance register address range >>>> + (base address and length) >>> >>> How about reset-cells property, Isn't that a mandatory property? >> >> It is optional, but you are right, should be added to this. >> >> -Tero >> >>> >>>> + >>>> +Example: >>>> + >>>> +prm_dsp2: prm@1b00 { >>>> + compatible = "ti,dra7-prm-inst"; >>>> + reg = <0x1b00 0x40>; >>>> + #reset-cells = <1>; >>>> +}; >>>> >> >> -- > -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com> To: Suman Anna <s-anna@ti.com>, Keerthy <j-keerthy@ti.com>, <ssantosh@kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-omap@vger.kernel.org>, <robh+dt@kernel.org> Cc: tony@atomide.com, devicetree@vger.kernel.org Subject: Re: [PATCH 1/8] dt-bindings: omap: add new binding for PRM instances Date: Tue, 20 Aug 2019 10:45:58 +0300 [thread overview] Message-ID: <c485156c-735f-40d3-d6a9-1b277e9c3d1d@ti.com> (raw) In-Reply-To: <b6506850-f4fc-43be-b5b7-b83cd77b5d66@ti.com> On 20.8.2019 0.28, Suman Anna wrote: > Hi Tero, > > On 8/19/19 4:28 AM, Tero Kristo wrote: >> On 08/08/2019 07:35, Keerthy wrote: >>> >>> >>> On 07/08/19 1:18 PM, 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. >>>> >>>> Signed-off-by: Tero Kristo <t-kristo@ti.com> >>>> --- >>>> .../devicetree/bindings/arm/omap/prm-inst.txt | 24 >>>> ++++++++++++++++++++++ >>>> 1 file changed, 24 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 0000000..e0ae87b >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/arm/omap/prm-inst.txt >>>> @@ -0,0 +1,24 @@ >>>> +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. > > So, I see that you are adding these as flat nodes directly under the prm > nodes where we have the clocks and clock_domains. Are you anticipating a > single DT node and/or driver managing both power-domains and resets? Single DT node + driver for both power-domains / resets. You can probably see from the driver code that the reset probing is called separately from the main probe function; power domain support should be added in similar manner under it. > >>>> + >>>> +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" > > What about OMAP2, OMAP3, DM814x, DM816x? OMAP2/3 architectures are slightly different beast to tackle, so planning to work on those later on. -Tero > > regards > Suman > >>>> +- reg: Contains PRM instance register address range >>>> + (base address and length) >>> >>> How about reset-cells property, Isn't that a mandatory property? >> >> It is optional, but you are right, should be added to this. >> >> -Tero >> >>> >>>> + >>>> +Example: >>>> + >>>> +prm_dsp2: prm@1b00 { >>>> + compatible = "ti,dra7-prm-inst"; >>>> + reg = <0x1b00 0x40>; >>>> + #reset-cells = <1>; >>>> +}; >>>> >> >> -- > -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-20 7:45 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-07 7:48 [PATCH 0/8] soc: ti: Add OMAP PRM driver Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 1/8] dt-bindings: omap: add new binding for PRM instances Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-08 4:35 ` Keerthy 2019-08-08 4:35 ` Keerthy 2019-08-19 9:28 ` Tero Kristo 2019-08-19 9:28 ` Tero Kristo 2019-08-19 21:28 ` Suman Anna 2019-08-19 21:28 ` Suman Anna 2019-08-20 7:45 ` Tero Kristo [this message] 2019-08-20 7:45 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 2/8] soc: ti: add initial PRM driver with reset control support Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-08 5:26 ` Keerthy 2019-08-08 5:26 ` Keerthy 2019-08-19 9:32 ` Tero Kristo 2019-08-19 9:32 ` Tero Kristo 2019-08-19 23:01 ` Suman Anna 2019-08-19 23:01 ` Suman Anna 2019-08-20 7:37 ` Tero Kristo 2019-08-20 7:37 ` Tero Kristo 2019-08-20 16:47 ` Suman Anna 2019-08-20 16:47 ` Suman Anna 2019-08-21 15:10 ` Philipp Zabel 2019-08-21 15:10 ` Philipp Zabel 2019-08-21 15:45 ` Suman Anna 2019-08-21 15:45 ` Suman Anna 2019-08-21 18:15 ` Tero Kristo 2019-08-21 18:15 ` Tero Kristo 2019-08-23 8:50 ` Philipp Zabel 2019-08-23 8:50 ` Philipp Zabel 2019-08-23 11:27 ` Tero Kristo 2019-08-23 11:27 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 3/8] soc: ti: omap-prm: poll for reset complete during de-assert Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 4/8] soc: ti: omap-prm: add support for denying idle for reset clockdomain Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-19 23:16 ` Suman Anna 2019-08-19 23:16 ` Suman Anna 2019-08-20 7:51 ` Tero Kristo 2019-08-20 7:51 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 5/8] soc: ti: omap-prm: add omap4 PRM data Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-08 5:30 ` Keerthy 2019-08-08 5:30 ` Keerthy 2019-08-19 9:32 ` Tero Kristo 2019-08-19 9:32 ` Tero Kristo 2019-08-19 23:08 ` Suman Anna 2019-08-19 23:08 ` Suman Anna 2019-08-20 7:52 ` Tero Kristo 2019-08-20 7:52 ` Tero Kristo 2019-08-20 17:23 ` Suman Anna 2019-08-20 17:23 ` Suman Anna 2019-08-21 6:38 ` Tero Kristo 2019-08-21 6:38 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 6/8] soc: ti: omap_prm: add data for am33xx Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-19 23:11 ` Suman Anna 2019-08-19 23:11 ` Suman Anna 2019-08-20 18:48 ` Suman Anna 2019-08-20 18:48 ` Suman Anna 2019-08-21 7:23 ` Tero Kristo 2019-08-21 7:23 ` Tero Kristo 2019-08-21 15:49 ` Suman Anna 2019-08-21 15:49 ` Suman Anna 2019-08-07 7:48 ` [PATCH 7/8] soc: ti: omap-prm: add dra7 PRM data Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-19 23:12 ` Suman Anna 2019-08-19 23:12 ` Suman Anna 2019-08-20 19:03 ` Suman Anna 2019-08-20 19:03 ` Suman Anna 2019-08-21 7:36 ` Tero Kristo 2019-08-21 7:36 ` Tero Kristo 2019-08-07 7:48 ` [PATCH 8/8] ARM: OMAP2+: pdata-quirks: add PRM data for reset support Tero Kristo 2019-08-07 7:48 ` Tero Kristo 2019-08-19 23:20 ` [PATCH 0/8] soc: ti: Add OMAP PRM driver Suman Anna 2019-08-19 23:20 ` Suman Anna 2019-08-20 7:54 ` Tero Kristo 2019-08-20 7:54 ` Tero Kristo 2019-08-20 16:51 ` Suman Anna 2019-08-20 16:51 ` Suman Anna
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=c485156c-735f-40d3-d6a9-1b277e9c3d1d@ti.com \ --to=t-kristo@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=j-keerthy@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=s-anna@ti.com \ --cc=ssantosh@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.