From: Stefan Wahren <stefan.wahren@i2se.com>
To: Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Shawn Guo <shawn.guo@linaro.org>, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Marek Vasut <marex@denx.de>, Sascha Hauer <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH RFC 0/3] clk: imx28: add DC-DC clock domain
Date: Mon, 20 Apr 2015 21:45:20 +0000 [thread overview]
Message-ID: <1429566323-8263-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series integrates the DC-DC clock domain into the i.MX28 clock
driver. That enables consumers to change DC-DC clock frequency in order to avoid
interferences without changing hardware. The final patch in the near future
should handle the i.MX23, too.
* patch 1 contains the update for the DT binding documentation
* patch 2 defines the PMU as the clock consumer
* patch 3 is extension of the clock driver
All information about the DC-DC clock was taken from the reference manual [1].
Unfortunately the logical diagram doesn't contain the DC-DC clock domain,
so i decide to create a ASCII diagramm (please look at patch 1).
The series is related to the upcoming MXS PMU and regulator driver
(last patch [2], working repo [3]).
At the end i still have a question:
The MXS PMU driver will using the syscon interface for accessing the
HW_POWER registers. The ctrl register for the DC-DC clock domain is located
under HW_POWER and not under HW_CLKCTRL.
So should the clock registration be done in clock driver like in patch 3 or
in the upcoming PMU driver?
Any other comments about the implementation are also welcome.
Regards
Stefan
[1] - http://cache.freescale.com/files/dsp/doc/ref_manual/MCIMX28RM.pdf
i.MX28 Applications Processor Reference Manual, Rev. 2, 08/2013
11.12.10 DC-DC Miscellaneous Register (HW_POWER_MISC)
[2] - http://marc.info/?l=linux-pm&m=142698428606221&w=2
[3] - https://github.com/lategoodbye/linux-mxs-power/tree/syscon
Stefan Wahren (3):
DT: imx28-clock: add ids for DC-DC clock domain
ARM: imx28: define PMU as clock consumer
clk: imx28: add DC-DC clock domain
.../devicetree/bindings/clock/imx28-clock.txt | 3 ++
arch/arm/boot/dts/imx28.dtsi | 2 ++
drivers/clk/mxs/clk-imx28.c | 33 +++++++++++++++++---
3 files changed, 33 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-04-20 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:45 Stefan Wahren [this message]
[not found] ` <1429566323-8263-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2015-04-20 21:45 ` [PATCH RFC 1/3] DT: imx28-clock: add ids for DC-DC clock domain Stefan Wahren
2015-04-20 21:45 ` [PATCH RFC 2/3] ARM: imx28: define PMU as clock consumer Stefan Wahren
2015-04-20 21:45 ` [PATCH RFC 3/3] clk: imx28: add DC-DC clock domain Stefan Wahren
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=1429566323-8263-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.guo@linaro.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).