From: tharvey@gateworks.com (Tim Harvey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: imx: ventana: enable LDO-bypass mode
Date: Thu, 30 Oct 2014 21:27:06 -0700 [thread overview]
Message-ID: <1414729631-11005-1-git-send-email-tharvey@gateworks.com> (raw)
The IMX6 has some internal LDO regulators provided by the anatop regulator
block that can regulate the arm, soc, gpu/vpu core supplies. Alternatively a
design can supply vdd_arm and vdd_soc externally via a PMIC to provide a lower
power draw (switches are more efficient that ldo's).
The first two patches add some helper functions to the regulator core that
allow us to determine if two regulator are the same and if a regulator is
in bypass mode.
There are two patches which add device-tree support for specifying core
regulators.
The patch to the imx6q cpufreq driver is where the logic that determines if
we should bypass the LDO's and attempts to do so. I chose to place the logic
there as this the driver that is affecting changes on the core regulators.
This is a followup to an RFC I posted previously [1] and the response I
recieved from Lucas. I feel that this approach is an improvement over the
initial proposal.
Hopefully I have Cc'd the proper parties - please advise if not as I'm not
extactly clear who should be in the loop on regulator core changes.
Tim
[1] http://www.spinics.net/lists/arm-kernel/msg365686.html
Tim Harvey (5):
regulator: add function to determine if 2 regulators are the same
regulator: add function to determine if a regulator is in bypass mode
ARM: dts: imx: add cpu0 alias
cpufreq: imx6q: add ldo-bypass support
ARM: imx: ventana: enable LDO bypass mode for GW54xx
arch/arm/boot/dts/imx6dl.dtsi | 2 +-
arch/arm/boot/dts/imx6q.dtsi | 2 +-
arch/arm/boot/dts/imx6qdl-gw54xx.dtsi | 55 +++++++++++++++++++++++++----------
drivers/cpufreq/imx6q-cpufreq.c | 51 ++++++++++++++++++++++++++++++++
drivers/regulator/core.c | 40 +++++++++++++++++++++++++
include/linux/regulator/consumer.h | 14 +++++++++
6 files changed, 146 insertions(+), 18 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-10-31 4:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 4:27 Tim Harvey [this message]
2014-10-31 4:27 ` [PATCH 1/5] regulator: add function to determine if 2 regulators are the same Tim Harvey
2014-10-31 4:27 ` [PATCH 2/5] regulator: add function to determine if a regulator is in bypass mode Tim Harvey
2014-10-31 4:27 ` [PATCH 3/5] ARM: dts: imx: add cpu0 alias Tim Harvey
2014-10-31 4:27 ` [PATCH 4/5] cpufreq: imx6q: add ldo-bypass support Tim Harvey
2014-12-17 14:36 ` Fabio Estevam
2014-12-18 14:11 ` Tim Harvey
2014-12-18 14:22 ` Mark Brown
2014-12-19 16:17 ` Tim Harvey
2014-12-19 16:23 ` Mark Brown
2015-01-05 14:38 ` Tim Harvey
2015-01-05 14:43 ` Mark Brown
2014-10-31 4:27 ` [PATCH 5/5] ARM: imx: ventana: enable LDO bypass mode for GW54xx Tim Harvey
2015-02-24 21:36 ` [PATCH 0/5] ARM: imx: ventana: enable LDO-bypass mode Jean-Michel Hautbois
[not found] ` <CAJ+vNU3-Q2LkGDau1c6rXTaGkP9c3-RC-OuHiTvv=DETKvnDaw@mail.gmail.com>
2015-03-24 15:27 ` Jean-Michel Hautbois
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=1414729631-11005-1-git-send-email-tharvey@gateworks.com \
--to=tharvey@gateworks.com \
--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).