From: Tomasz Figa <t.figa@samsung.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Tomasz Figa <t.figa@samsung.com>
Subject: [PATCH 0/8] clk: max77686: Clock provider implementation fixes
Date: Thu, 17 Oct 2013 18:30:34 +0200 [thread overview]
Message-ID: <1382027442-1992-1-git-send-email-t.figa@samsung.com> (raw)
This series intends to improve clock provider impementation of max77686
PMIC driver. First two patches are simple fixes of current implementation
to allow correct control of provided clocks. Further patches refactor
the driver to make the code cleaner and prepare for further patches. Then
last two patches add registration of OF clock provider and adjust device
tree nodes of boards containing max77686 chip to contain properties
required by clock provider.
Tested on Exynos4412-based Trats2 board, with additional patches adding
driver being a consumer of one of max77686 clocks.
Tomasz Figa (8):
clk: max77686: Correct callback used for checking clock status
clk: max77686: Provide .recalc_rate() operation
clk: max77686: Refactor successful exit of probe function
clk: max77686: Make max77686_clk_register() return struct clk *
clk: max77686: Fix clean-up in error and remove paths
clk: max77686: Refactor driver data handling
clk: max77686: Register OF clock provider
ARM: dts: Add clock provider specific properties to max77686 node
.../devicetree/bindings/clock/maxim,max77686.txt | 38 +++++++++
Documentation/devicetree/bindings/mfd/max77686.txt | 3 +
arch/arm/boot/dts/cros5250-common.dtsi | 1 +
arch/arm/boot/dts/exynos4412-odroidx.dts | 1 +
arch/arm/boot/dts/exynos4412-trats2.dts | 1 +
drivers/clk/clk-max77686.c | 97 +++++++++++++---------
6 files changed, 104 insertions(+), 37 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/maxim,max77686.txt
--
1.8.3.2
next reply other threads:[~2013-10-17 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 16:30 Tomasz Figa [this message]
[not found] ` <1382027442-1992-1-git-send-email-t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-10-17 16:30 ` [PATCH 1/8] clk: max77686: Correct callback used for checking clock status Tomasz Figa
2013-10-17 16:30 ` [PATCH 2/8] clk: max77686: Provide .recalc_rate() operation Tomasz Figa
2013-10-17 16:30 ` [PATCH 3/8] clk: max77686: Refactor successful exit of probe function Tomasz Figa
2013-10-21 9:41 ` Sachin Kamat
2013-10-17 16:30 ` [PATCH 4/8] clk: max77686: Make max77686_clk_register() return struct clk * Tomasz Figa
2013-10-17 16:30 ` [PATCH 5/8] clk: max77686: Fix clean-up in error and remove paths Tomasz Figa
2013-10-17 16:30 ` [PATCH 6/8] clk: max77686: Refactor driver data handling Tomasz Figa
2013-10-17 16:30 ` [PATCH 7/8] clk: max77686: Register OF clock provider Tomasz Figa
2013-10-17 16:30 ` [PATCH 8/8] ARM: dts: Add clock provider specific properties to max77686 node Tomasz Figa
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=1382027442-1992-1-git-send-email-t.figa@samsung.com \
--to=t.figa@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sameo@linux.intel.com \
/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