From: Mike Turquette <mturquette@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
Mike Turquette <mturquette@linaro.org>
Subject: [PATCH RFC 0/3] clk: dt: bindings for mux & divider clocks
Date: Mon, 3 Jun 2013 10:53:07 -0700 [thread overview]
Message-ID: <1370281990-15090-1-git-send-email-mturquette@linaro.org> (raw)
This series introduces binding definitions for common register-mapped
clock multiplexor and divider IP blocks, and the corresponding setup
functions once they are matched. The bindings are close the struct
definitions but please don't hold that against the binding: the struct
definitions closely model the hardware.
The only missing basic clock type is the gate clock. A binding for that
was posted some time back and is similar in spirit to these[1]. I guess
we'll need to decide whether register-level programming details belong
in DT. I believe they do since those details describe the hardware.
Note that there is still no generic clock driver that matches these
basic types, but it would be trivial to write one. Thoughts on that?
Is it better for each of the basic clock types to be a driver that
matches, or should there be one drivers/clk/clk-basic.c which matches
all of the basic clock building blocks? I like the latter for aesthetic
purposes.
I am using this code while converting the OMAP4 clock data over to DT
and some common boilerplate code can be factored out of several clock
drivers if this is merged.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137878.html
Mike Turquette (3):
clk: of: helper for determining number of parent clocks
clk: dt: binding for basic multiplexor clock
clk: dt: binding for basic divider clock
.../devicetree/bindings/clock/divider-clock.txt | 80 ++++++++++++++++++++
.../devicetree/bindings/clock/mux-clock.txt | 75 ++++++++++++++++++
drivers/clk/clk-divider.c | 88 +++++++++++++++++++++-
drivers/clk/clk-mux.c | 65 +++++++++++++++-
drivers/clk/clk.c | 6 ++
include/linux/clk-provider.h | 8 +-
6 files changed, 319 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/divider-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/mux-clock.txt
--
1.8.1.2
next reply other threads:[~2013-06-03 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 17:53 Mike Turquette [this message]
2013-06-03 17:53 ` [PATCH RFC 2/3] clk: dt: binding for basic multiplexor clock Mike Turquette
2013-06-03 19:33 ` Heiko Stübner
2013-06-03 20:07 ` Mike Turquette
2013-06-03 20:15 ` Heiko Stübner
[not found] ` <201306032215.45983.heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2013-06-03 21:39 ` Heiko Stübner
2013-06-04 6:14 ` Mike Turquette
2013-06-03 17:53 ` [PATCH RFC 3/3] clk: dt: binding for basic divider clock Mike Turquette
[not found] ` <1370281990-15090-4-git-send-email-mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-03 22:18 ` Heiko Stübner
2013-06-13 2:41 ` Mike Turquette
2013-06-04 17:11 ` Stephen Boyd
2013-06-04 17:39 ` Matt Sealey
2013-06-04 19:22 ` Mike Turquette
2013-06-04 20:13 ` Matt Sealey
2013-06-06 0:09 ` Heiko Stübner
[not found] ` <1370281990-15090-1-git-send-email-mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-03 17:53 ` [PATCH RFC 1/3] clk: of: helper for determining number of parent clocks Mike Turquette
2013-06-03 22:31 ` [PATCH RFC 0/3] clk: dt: bindings for mux & divider clocks Heiko Stübner
2013-06-07 5:51 ` Shawn Guo
[not found] ` <20130607055128.GA20780-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-06-07 17:52 ` Mike Turquette
2013-06-08 3:02 ` Shawn Guo
[not found] ` <20130608030240.GB22134-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-06-08 18:25 ` Mike Turquette
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=1370281990-15090-1-git-send-email-mturquette@linaro.org \
--to=mturquette@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).