From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-v2 3/5] mfd: devicetree: bindings: Add clock subdevice node information
Date: Tue, 25 Aug 2015 14:21:43 +0530 [thread overview]
Message-ID: <55DC2C9F.8000203@linaro.org> (raw)
In-Reply-To: <20150825075858.GH19409@x1>
On Tuesday 25 August 2015 01:28 PM, Lee Jones wrote:
> On Tue, 25 Aug 2015, Vaibhav Hiremath wrote:
>
>> This patch updates the binding documentation for optional
>> clocks node and related information for buffered 32KHz clock.
>>
>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> Acked-by: Rob Herring <robh@kernel.org>
>> ---
>> Documentation/devicetree/bindings/mfd/88pm800.txt | 27 +++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/88pm800.txt b/Documentation/devicetree/bindings/mfd/88pm800.txt
>> index 2c82fcb..bc6cb02 100644
>> --- a/Documentation/devicetree/bindings/mfd/88pm800.txt
>> +++ b/Documentation/devicetree/bindings/mfd/88pm800.txt
>> @@ -15,6 +15,26 @@ Optional properties :
>> Without this both BUCK1A and BUCK1B operates independently with 3A capacity.
>> (This property is only applicable to 88PM860)
>>
>> +Optional nodes:
>> +- clocks: 88pm800 family of devices provide multiple buffered 32.768
>> + KHz outputs, so to register these as clocks with common clock framework
>> + instantiate a sub-node named "clocks". It uses the common clock binding
>> + documented in :
>> + [Documentation/devicetree/bindings/clock/clock-bindings.txt]
>
> I tend to prefer relative paths. Firstly because they're shorter and
> more succinct and secondly because if we do eventually move DT out of
> the kernel, it will be less hassle to rename each of them.
>
>> + - #clock-cells: should be 1.
>> +
>> + - The following is the list of clocks generated by the controller. Each clock
>> + is assigned an identifier and client nodes use this identifier to specify
>> + the clock which they consume.
>> + Clock ID Devices
>> + ----------------------------------------------------------
>> + pm800_clk32k_1 0 88PM800 and 88PM860
>> + pm800_clk32k_2 1 88PM800 and 88PM860
>> + pm800_clk32k_3 2 88PM800
>> +
>> + - compatible: Should be : "marvell,88pm800-clk"
>> +
>> 88pm80x family of devices consists of varied group of sub-devices:
>>
>> Device Supply Names Description
>> @@ -22,6 +42,7 @@ Device Supply Names Description
>> 88pm80x-onkey : : On key
>> 88pm80x-rtc : : RTC
>> 88pm80x-regulator : : Regulators
>> +88pm80x-clk : : 32KHz Clk provider
>
> Nit: Alphabetical?
>
Will correct both comments.
Thanks,
Vaibhav
next prev parent reply other threads:[~2015-08-25 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:56 [PATCH-v2 0/5] clk: 88pm800: Add new clk provider driver for 88PM800 MFD Vaibhav Hiremath
2015-08-24 18:56 ` [PATCH-v2 1/5] mfd: 88pm800: Fix tabbing issue Vaibhav Hiremath
2015-08-25 7:51 ` Lee Jones
2015-08-25 8:41 ` Vaibhav Hiremath
2015-08-25 10:30 ` Lee Jones
2015-08-25 10:49 ` Vaibhav Hiremath
2015-08-24 18:56 ` Vaibhav Hiremath
2015-08-25 7:52 ` Lee Jones
2015-08-25 8:50 ` Vaibhav Hiremath
2015-08-25 10:35 ` Lee Jones
2015-08-25 10:56 ` Vaibhav Hiremath
2015-08-24 18:56 ` [PATCH-v2 2/5] mfd: 88pm800: Update the header file with 32K clk related macros Vaibhav Hiremath
2015-08-25 7:55 ` Lee Jones
2015-08-25 8:45 ` Vaibhav Hiremath
2015-08-24 18:56 ` [PATCH-v2 3/5] mfd: devicetree: bindings: Add clock subdevice node information Vaibhav Hiremath
2015-08-25 7:58 ` Lee Jones
2015-08-25 8:51 ` Vaibhav Hiremath [this message]
2015-08-24 18:56 ` [PATCH-v2 4/5] clk: 88pm800: Add clk provider driver for 88pm800 family of devices Vaibhav Hiremath
2015-08-25 5:08 ` Krzysztof Kozlowski
2015-08-24 18:56 ` [PATCH-v2 5/5] mfd: 88pm800: Add support for clk subdevice Vaibhav Hiremath
2015-08-25 5:25 ` Krzysztof Kozlowski
2015-08-25 7:49 ` Lee Jones
2015-08-25 8:38 ` Vaibhav Hiremath
2015-08-25 8:31 ` Vaibhav Hiremath
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=55DC2C9F.8000203@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).