Hello, The voltage regulators need to be coupled on NVIDIA Tegra20 and Tegra30 SoCs in order to provide voltage scaling functionality in a generic way. All necessary regulator-core patches that added support for the regulators coupling are already have been merge into mainline kernel. This series adds customized voltage couplers for Tegra20/30 SoCs, paving the way for a refined CPUFreq driver that will utilize voltage scaling and other neat features. This is a resend of a leftover patches from a previous series [1] that was partially applied by Mark Brown. Please review, thanks in advance! [1] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=115626 Changelog: v2: - Some days ago OPP framework got a change that makes CPU regulator to be enabled at the time of CPUFreq's driver initializing OPPs. In a result the CPU's voltage is dropped to a minimum value on CPUFreq's setting up because there are no consumers at the time of regulator's enabling, thus CPU is getting into a big trouble. This problem is now resolved in the couplers code by assuming that min_uV=current_uV for CPU's regulator if it doesn't have any active consumers. Dmitry Osipenko (3): dt-bindings: regulator: Document regulators coupling of NVIDIA Tegra20/30 SoCs soc/tegra: regulators: Add regulators coupler for Tegra20 soc/tegra: regulators: Add regulators coupler for Tegra30 .../nvidia,tegra-regulators-coupling.txt | 65 ++++ drivers/soc/tegra/Kconfig | 10 + drivers/soc/tegra/Makefile | 2 + drivers/soc/tegra/regulators-tegra20.c | 364 ++++++++++++++++++ drivers/soc/tegra/regulators-tegra30.c | 316 +++++++++++++++ 5 files changed, 757 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/nvidia,tegra-regulators-coupling.txt create mode 100644 drivers/soc/tegra/regulators-tegra20.c create mode 100644 drivers/soc/tegra/regulators-tegra30.c -- 2.22.0
