[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57C9E0A8.4010701@ti.com>
Date: Fri, 2 Sep 2016 15:27:20 -0500
From: Dave Gerlach <d-gerlach@...com>
To: Nishanth Menon <nm@...com>, Rob Herring <robh@...nel.org>
CC: Tero Kristo <t-kristo@...com>, Lokesh Vutla <lokeshvutla@...com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Sudeep Holla <sudeep.holla@....com>,
lkml <linux-kernel@...r.kernel.org>,
"Andrew F . Davis" <afd@...com>,
Russell King <rmk+kernel@...linux.org.uk>,
Russ Dill <Russ.Dill@...com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Santosh Shilimkar <ssantosh@...nel.org>,
dt list <devicetree@...r.kernel.org>
Subject: Re: [PATCH V2 1/5] Documentation: Add support for TI System Control
Interface (TI-SCI) protocol
On 09/02/2016 12:07 PM, Nishanth Menon wrote:
> Rob,
>
> On Fri, Sep 2, 2016 at 10:06 AM, Rob Herring <robh@...nel.org> wrote:
>> On Tue, Aug 30, 2016 at 08:06:43AM -0500, Nishanth Menon wrote:
> [...]
>>> +
>>> +TI-SCI Client Device Node:
>>> +========================
>>> +
>>> +Client nodes refer to the required TI-SCI device using the "ti,sci" property.
>>
>> As I mentioned for power domains, for clients that are self contained
>> (i.e. a single function) I think the should be child nodes.
>>
>
> Thanks for the feedback. I think we should be able to do that and also
> assume you have no further improvements you'd like to see here.
>
> Looking at current Documentation/devicetree/bindings/arm/arm,scpi.txt
> -> it makes sense to stick along the same lines as you mentioned.
>
> Dave, Tero: do you guys have any objections?
No objections, I think this is a logical move.
Regards,
Dave
>
>
> ---
> Regards,
> Nishanth Menon
>
Powered by blists - more mailing lists