From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: mturquette@linaro.org, grant.likely@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, ldewangan@nvidia.com,
linux-doc@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2 0/2] clk: Support for Palmas clk32kg and clk32kgaudio clocks
Date: Mon, 26 May 2014 10:06:39 +0300 [thread overview]
Message-ID: <5382E7FF.7070600@ti.com> (raw)
In-Reply-To: <20140506133136.GA11626@kahuna>
Mike,
On 05/06/2014 04:31 PM, Nishanth Menon wrote:
> On 16:24-20140506, Peter Ujfalusi wrote:
>> Hi,
>>
>> Changes since v1:
>> - binding documentation and driver has been separated based on Nishanth Menon's
>> comment
Could you take a look at this series please? I really hoped that it would make
it to 3.16...
Thanks,
Péter
>>
>> v1 of the driver can be found:
>> https://lkml.org/lkml/2014/4/3/104
>>
>> Palmas class of devices can provide 32K clock(s) to be used by other devices
>> on the board. Depending on the actual device the provided clocks can be:
>> CLK32K_KG and CLK32K_KGAUDIO
>> or only one:
>> CLK32K_KG (TPS659039 for example)
>>
>> Use separate compatible flags for the two 32K clock.
>> A system which needs or have only one of the 32k clock from
>> Palmas will need to add node(s) for each clock as separate section
>> in the dts file.
>> The two compatible property is:
>> "ti,palmas-clk32kg" for clk32kg clock
>> "ti,palmas-clk32kgaudio" for clk32kgaudio clock
>>
>> Apart from the register control of the clocks - which is done via
>> the clock API there is a posibility to enable the external sleep
>> control. In this way the clock can be enabled/disabled on demand by the
>> user of the clock.
>>
>> Regards,
>> Peter
>> ---
>> Peter Ujfalusi (2):
>> dt/bindings: Binding documentation for Palmas clk32kg and clk32kgaudio
>> clocks
>> clk: Add driver for Palmas clk32kg and clk32kgaudio clocks
>>
>> .../bindings/clock/clk-palmas-clk32kg-clocks.txt | 35 +++
>> drivers/clk/Kconfig | 7 +
>> drivers/clk/Makefile | 1 +
>> drivers/clk/clk-palmas.c | 307 +++++++++++++++++++++
>> include/dt-bindings/mfd/palmas.h | 18 ++
>> 5 files changed, 368 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/clock/clk-palmas-clk32kg-clocks.txt
>> create mode 100644 drivers/clk/clk-palmas.c
>> create mode 100644 include/dt-bindings/mfd/palmas.h
>>
>> --
>> 1.9.2
>>
>
> Series:
> Reviewed-by: Nishanth Menon <nm@ti.com>
prev parent reply other threads:[~2014-05-26 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 13:24 [PATCH v2 0/2] clk: Support for Palmas clk32kg and clk32kgaudio clocks Peter Ujfalusi
2014-05-06 13:24 ` [PATCH v2 1/2] dt/bindings: Binding documentation " Peter Ujfalusi
2014-05-06 13:24 ` [PATCH v2 2/2] clk: Add driver " Peter Ujfalusi
2014-05-06 13:31 ` [PATCH v2 0/2] clk: Support " Nishanth Menon
2014-05-26 7:06 ` Peter Ujfalusi [this message]
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=5382E7FF.7070600@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.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).