AM3352: How to reflect device tree tps65910 regulator settings?

To: anyone concerned

Hello,

I am now using Am3352 and the SDK ver 7.3 for embeded programming.

The file am335x-evmsk.dts under u-boot folder has the following items.

...

#include "tps65910.dtsi"

&mcasp1 {
		pinctrl-names = "default";
		pinctrl-0 = <&am335x_evm_audio_pins>;

		status = "okay";

		op-mode = <0>;          /* MCASP_IIS_MODE */
		tdm-slots = <2>;
		/* 4 serializers */
		serial-dir = <  /* 0: INACTIVE, 1: TX, 2: RX */
			0 0 1 2
		>;
		tx-num-evt = <32>;
		rx-num-evt = <32>;
};

&tps {
	vcc1-supply = <&vbat>;
	vcc2-supply = <&vbat>;
	vcc3-supply = <&vbat>;
	vcc4-supply = <&vbat>;
	vcc5-supply = <&vbat>;
	vcc6-supply = <&vbat>;
	vcc7-supply = <&vbat>;
	vccio-supply = <&vbat>;

	regulators {
		vrtc_reg: regulator@0 {
			regulator-always-on;
		};

		vio_reg: regulator@1 {
			regulator-always-on;
		};

		vdd1_reg: regulator@2 {
			/* VDD_MPU voltage limits 0.95V - 1.26V with +/-4% tolerance */
			regulator-name = "vdd_mpu";
			regulator-min-microvolt = <912500>;
			regulator-max-microvolt = <1312500>;
			regulator-boot-on;
			regulator-always-on;
		};

...

I found that no mater how to modify the settings here,  those are not reflected to tps65910 registers.

I searched the source code with u-boot-<version> folder, it seems that ./drivers/regulator is not exist as what in linux-<version> folder.

My questions are:

1.  Does that mean tps65910 settings in the device tree file is not valid when u-boot is running?

2.  If I want to reflect tps65910 settings for u-boot, what should I do?

regards.

Xitong Zhang