From: Mike Turquette <mturquette@linaro.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, grant.likely@linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, ldewangan@nvidia.com,
linux-doc@vger.kernel.org, nm@ti.com, robh+dt@kernel.org
Subject: Re: [RESEND 0/2] clk: Support for Palmas clk32kg and clk32kgaudio clocks
Date: Tue, 01 Jul 2014 21:53:20 -0700 [thread overview]
Message-ID: <20140702045320.23338.25@quantum> (raw)
In-Reply-To: <1403848871-26519-1-git-send-email-peter.ujfalusi@ti.com>
Quoting Peter Ujfalusi (2014-06-26 23:01:09)
> Hi Mike,
>
> This is a resend of the v2 version of the palmas clock driver which seamingly
> missed the 3.16 merge window. I have added Nishanth's Reviewed-by tag to the
> patches.
Thanks for the resend. Applied to clk-next.
Regards,
Mike
>
> Changes since v1:
> - binding documentation and driver has been separated based on Nishanth Menon's
> comment
>
> v2 of the series:
> https://lkml.org/lkml/2014/5/6/323
>
> 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
>
> --
> 2.0.0
>
prev parent reply other threads:[~2014-07-02 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 6:01 [RESEND 0/2] clk: Support for Palmas clk32kg and clk32kgaudio clocks Peter Ujfalusi
2014-06-27 6:01 ` [RESEND 1/2] dt/bindings: Binding documentation " Peter Ujfalusi
2014-06-27 6:01 ` [RESEND 2/2] clk: Add driver " Peter Ujfalusi
2014-06-27 18:23 ` Javier Martinez Canillas
2014-06-30 5:56 ` Peter Ujfalusi
2014-07-02 4:33 ` Mike Turquette
2014-07-02 9:16 ` Javier Martinez Canillas
2014-07-02 4:53 ` Mike Turquette [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=20140702045320.23338.25@quantum \
--to=mturquette@linaro.org \
--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=nm@ti.com \
--cc=peter.ujfalusi@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).