[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+BuhbHgnYi6HfAJx986vtDuUJzbxBRgivX9pF1GhUSvQ@mail.gmail.com>
Date: Thu, 30 Jul 2015 17:21:56 -0500
From: Rob Herring <robherring2@...il.com>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Vaibhav Hiremath <vaibhav.hiremath@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Lee Jones <lee.jones@...aro.org>, linux-clk@...r.kernel.org,
Michael Turquette <mturquette@...libre.com>
Subject: Re: [PATCH 2/4] mfd: devicetree: bindings: Add clock subdevice node information
On Thu, Jul 30, 2015 at 5:13 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
> On 07/22/2015 10:08 PM, Krzysztof Kozlowski wrote:
>>
>> 2015-07-21 20:07 GMT+09:00 Vaibhav Hiremath <vaibhav.hiremath@...aro.org>:
>>>
>>> This patch updates the binding documentation for optional
>>> clocks node and related information for buffered 32KHz clock.
>>>
>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@...aro.org>
>>> ---
>>> Documentation/devicetree/bindings/mfd/88pm800.txt | 28
>>> +++++++++++++++++++++++
>>> 1 file changed, 28 insertions(+)
>>
>> +Cc Stephen Boyd (clocks)
>>
>> We had a discussion whether clock bindings should be put in MFD
>> bindings documentation or into separate file in bindings/clock but
>> either way is fine for me:
>
>
> No patch? :)
>
> I think Rob has been pushing for MFDs to document everything within one
> file, but either way is fine from clk perspective.
I don't recall that exactly. I did say that child bindings need to
point back to the MFD binding. So this is fine with me:
Acked-by: Rob Herring <robh@...nel.org>
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists