ARM64: dts: rockchip: Change PWM regulators to 300kHz for gru base

Apparently the time constant for for the PWM regulator circuit on
gru-based devices is different than EVB.  Let's run at 300kHz which
should make us work well.

BUG=None
TEST=None

Change-Id: I0973f416d026de27908c3ef527c1e9274b967fc8
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chrome-internal-review.googlesource.com/254648
Reviewed-by: Stephen Barber <smbarber@google.com>
Tested-by: Doug Anderson <dianders@google.com>
This commit is contained in:
Douglas Anderson 2016-04-11 17:51:56 -07:00 committed by Huang, Tao
parent 6cb8263cd9
commit 86fc316162

View File

@ -173,9 +173,7 @@ ppvar_bigcpu: ppvar-bigcpu {
regulator-name = "ppvar_bigcpu";
status = "okay";
// TODO: schematics say 600kHz so period of 1667 ns
// Rockchip has 25000 (40kHz) for these though.
pwms = <&pwm1 0 1667 0>;
pwms = <&pwm1 0 3333 0>;
// TODO: where's the mapping of duty cycle to voltage???
// TODO: we probably need in-flight PWM regulator series?
@ -195,9 +193,7 @@ ppvar_litcpu: ppvar-litcpu {
regulator-name = "ppvar_litcpu";
status = "okay";
// TODO: schematics say 600kHz so period of 1667 ns
// Rockchip has 25000 (40kHz) for these though.
pwms = <&pwm2 0 1667 0>;
pwms = <&pwm2 0 3333 0>;
/* EC turns on w/ ap_core_en; always on for AP */
regulator-always-on;
@ -214,9 +210,7 @@ ppvar_gpu: ppvar-gpu {
regulator-name = "ppvar_gpu";
status = "okay";
// TODO: schematics say 600kHz so period of 1667 ns
// Rockchip has 25000 (40kHz) for these though.
pwms = <&pwm0 0 1667 0>;
pwms = <&pwm0 0 3333 0>;
/* EC turns on w/ ap_core_en; always on for AP */
regulator-always-on;
@ -233,9 +227,7 @@ ppvar_centerlogic: ppvar-centerlogic {
regulator-name = "ppvar_centerlogic";
status = "okay";
// TODO: schematics say 600kHz so period of 1667 ns
// Rockchip has 25000 (40kHz) for these though.
pwms = <&pwm3 0 1667 0>;
pwms = <&pwm3 0 3333 0>;
/* EC turns on w/ ppvar_centerlogic_en; always on for AP */
regulator-always-on;