From: Tero Kristo <t-kristo@ti•com>
To: Tony Lindgren <tony@atomide•com>, Rob Herring <robh+dt@kernel•org>
Cc: devicetree@vger•kernel.org,
linux-omap <linux-omap@vger•kernel.org>,
Philipp Zabel <p.zabel@pengutronix•de>,
Santosh Shilimkar <ssantosh@kernel•org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists•infradead.org>
Subject: Re: [PATCHv4 01/10] dt-bindings: omap: add new binding for PRM instances
Date: Fri, 6 Sep 2019 23:02:28 +0300 [thread overview]
Message-ID: <e2b75368-df70-b6c9-e019-61610859f146@ti.com> (raw)
In-Reply-To: <20190906153658.GB52127@atomide.com>
On 06/09/2019 18:36, Tony Lindgren wrote:
> * Rob Herring <robh+dt@kernel•org> [190906 12:57]:
>> On Fri, Sep 6, 2019 at 11:36 AM Tero Kristo <t-kristo@ti•com> 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>
>>> ---
>>> v4:
>>> - renamed nodes as power-controller
>>> - added documentation about hierarchy
>>>
>>> .../devicetree/bindings/arm/omap/prm-inst.txt | 31 +++++++++++++++++++
>>> 1 file changed, 31 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/arm/omap/prm-inst.txt
>>
>> Reviewed-by: Rob Herring <robh@kernel•org>
>
> Looks good to me too:
>
> Reviewed-by: Tony Lindgren <tony@atomide•com>
>
I may need to re-spin slightly new version of this. Stephen has some
comments on the clock driver side I am depending on, he does not like
the hard link between reset + clocks, so I may need to ditch the
"clocks" property from this one also.
I'll see next week which direction I need to go.
-Tero
--
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-09-06 20:02 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
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 [this message]
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=e2b75368-df70-b6c9-e019-61610859f146@ti.com \
--to=t-kristo@ti$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=p.zabel@pengutronix$(echo .)de \
--cc=robh+dt@kernel$(echo .)org \
--cc=ssantosh@kernel$(echo .)org \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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