From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] i.MX: drop secondary clocks
Date: Thu, 8 Mar 2012 22:42:27 +0100 [thread overview]
Message-ID: <1331242949-22780-1-git-send-email-s.hauer@pengutronix.de> (raw)
Hi All,
On i.MX we currently have grouped clocks, also known as secondary clocks.
These are clocks that get enabled when the primary clock gets enabled. This
doesn't integrate well into the generic clock framework. Also we often return
the rate of one clock and really enable/disable another clock. I plan to get
rid of these clocks by exposing the individual clocks to the drivers. The
following is meant as an example how this can be done. I have a more complete
series internally but this conflicts with Richards clk_prepare series.
Thanks to the nature of clk_get we can simply clk_get the individual clocks in
the drivers and the current clock implementation will always return the one
with con_id = NULL. Then with the generic clk implementation the drivers will
finally get the individual clocks.
So unless there are objections I will follow up on this after the next merge
window.
Sascha
----------------------------------------------------------------
Sascha Hauer (2):
clk: Add helper to get/put arrays of clocks
spi i.MX: do not depend on grouped clocks
drivers/clk/clkdev.c | 36 ++++++++++++++++++++++++++++++++++++
drivers/spi/spi-imx.c | 30 ++++++++++++++++++++----------
include/linux/clk.h | 3 +++
3 files changed, 59 insertions(+), 10 deletions(-)
next reply other threads:[~2012-03-08 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 21:42 Sascha Hauer [this message]
2012-03-08 21:42 ` [PATCH 1/2] clk: Add helper to get/put arrays of clocks Sascha Hauer
2012-03-08 21:42 ` [PATCH 2/2] spi i.MX: do not depend on grouped clocks Sascha Hauer
2012-03-09 8:03 ` [RFC] i.MX: drop secondary clocks Shawn Guo
2012-03-09 9:32 ` Lothar Waßmann
2012-03-09 10:29 ` Sascha Hauer
2012-03-09 11:47 ` Lothar Waßmann
2012-03-09 14:20 ` Richard Zhao
2012-03-09 14:22 ` Sascha Hauer
2012-03-09 14:44 ` Lothar Waßmann
2012-03-09 16:09 ` Sascha Hauer
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=1331242949-22780-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).