aboutsummaryrefslogtreecommitdiff
path: root/drivers/mfd/ezx-pcap.c
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-08-03 17:45:21 -0600
committerArnd Bergmann <arnd@arndb.de>2012-08-09 15:16:40 +0200
commit798bd59ce94c8218332996e650ded48ded039fe1 (patch)
tree100100812950a4f7ec01d469b558b9e7651ae278 /drivers/mfd/ezx-pcap.c
parent376249cf57b4e5516ba88f8ed8d45272e793cfb9 (diff)
downloadlinux-linaro-stable-798bd59ce94c8218332996e650ded48ded039fe1.tar.gz
ARM: tegra: more regulator fixes for Harmony
Commit 3d55c29 "ARM: tegra: harmony: add regulator supply name and its input supply" was supposed to fix all the problems with regulators on Harmony. However, it appears that I only tested it when booting using board files, not when booting using device tree. This change fixes two problems with regulators when booting using device tree: 1) That patch only created the vdd_sys regulator when booting using a board file. Since this is the root of the whole regulator tree, this caused no regulators to successfully initialize when booting using device tree. The registration of vdd_sys is moved to fix this. 2) When booting use DT, the regulator core sets has_full_constraints, which in turn causes the core to turn off any regulators not marked as always on. Some of the affected regulators are required for basic system operation. To solve this, add always on constraints to all relevant regulators. This doesn't affect booting using a board file since nothing sets has_full_constraints in that case. Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'drivers/mfd/ezx-pcap.c')
0 files changed, 0 insertions, 0 deletions