From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-v2 0/5] clk: 88pm800: Add new clk provider driver for 88PM800 MFD
Date: Tue, 25 Aug 2015 00:26:28 +0530 [thread overview]
Message-ID: <1440442594-3102-1-git-send-email-vaibhav.hiremath@linaro.org> (raw)
88PM800 family of devices provides multiple buffered 32.768 KHz clock
output.
88PM800 : CLK32k_1, CLK32k_2 and CLK32k_3
88PM860 : CLK32k_1 and CLK32k_2
This patch-series adds new clock provider driver for enabling/disabling
buffered 32Khz clock output from 88PM800 family of device. Adds clock device to
MFD and updates the binding documentation.
The PATCH [1/4], created separately, as it would be easy between maintainers to
queue it.
Note that, I have access to only 88PM800 and 88PM860 datasheet,
so enabling support for only above two devices.
Testing:
- Boot tested on 88PM860 based platform
- Clock enable/disable
- Non PM860, to make sure that it won't lead to any issues
V1 => V2:
========
Link to V1: https://lkml.org/lkml/2015/7/21/298
- Added new patch to the series [1/5], fixing tabbing issue in the file
- Removed unnecessary brackets around macro value
- Used devm_kcalloc variants for array allocation instead of kzalloc.
- Fixed all other trivial issues.
Vaibhav Hiremath (5):
mfd: 88pm800: Fix tabbing issue
mfd: 88pm800: Update the header file with 32K clk related macros
mfd: devicetree: bindings: Add clock subdevice node information
clk: 88pm800: Add clk provider driver for 88pm800 family of devices
mfd: 88pm800: Add support for clk subdevice
Documentation/devicetree/bindings/mfd/88pm800.txt | 27 ++
drivers/clk/Kconfig | 8 +
drivers/clk/Makefile | 1 +
drivers/clk/clk-88pm800.c | 341 ++++++++++++++++++++++
drivers/mfd/88pm800.c | 150 ++++++----
include/linux/mfd/88pm80x.h | 12 +
6 files changed, 475 insertions(+), 64 deletions(-)
create mode 100644 drivers/clk/clk-88pm800.c
--
1.9.1
next reply other threads:[~2015-08-24 18:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:56 Vaibhav Hiremath [this message]
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
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=1440442594-3102-1-git-send-email-vaibhav.hiremath@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).