Nick A

https://patchew.org/linux/20240317-add-t95-axp313-support-v3-0-0d63f7c23d37@gmail.com/20240317-add-t95-axp313-support-v3-3-0d63f7c23d37@gmail.com/ It's actually BCM43342/1 It System doesn't detect this chip by default. The most relevant message from dmesg is: [ 14.042035] kernel: brcmfmac: brcmf_fw_alloc_request: Unknown chip BCM43342/1 I believe that it's only a matter of missing module. I don't think it is supported in mainline ATM. I left it to have a wi-fi node accessible and detectable by kernel. If you think that it's better to remove the node if it's not supported I can do it. Somebody actually extracted modified precompiled module from custom 5.15.16 rockchip kernel, which implements support for this card. There's no patch for it that could be submitted to mainline unfortunately ATM. I've found a patch that adds chip id strings to brcmfmac, but I would like to test it beforehand. V4 of the patch. If you want to borrow the code. https://patchew.org/linux/20240319-add-t95-axp313-support-v4-0-6204b6d23229@gmail.com/20240319-add-t95-axp313-support-v4-3-6204b6d23229@gmail.com/

U-Boot SPL 2024.01-armbian (Apr 17 2024 - 03:30:23 +0000) DRAM:This DRAM setup is currently not supported. resetting ... When you tested my build you got. Then you test my build with mate defconfig? probably you used mate dts. I don't see any wifi code in mate's uboot or kernel dts. You can't use my dts directly without modifying the defconfig. You need your dram setup and axp305 code. Maybe a few other defconfig changes. My kernel dts would also need changes because of the axp305 code. What I'm asking is if you can just use my wlan and bluetooth code. Also you need to check your dmesg to see if wifi is asking for firmware. Sometimes it's looking for a specific file name.

I'm wondering if my wifi code would work for you. I'm using bcm4335. https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-add-Transpeed-8K618-T-TV-box.patch

No 13, 11, 10 are in HEX you need to convert it to decimal 19,17,16 https://www.rapidtables.com/convert/number/hex-to-decimal.html Use my code the way it is. + bluetooth { + compatible = "brcm,bcm43438-bt"; + shutdown-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PG19 */ + clocks = <&rtc CLK_OSC32K_FANOUT>; + host-wakeup-gpios = <&pio 6 16 GPIO_ACTIVE_HIGH>; /* PG16 */ + clock-names = "lpo"; + vddio-supply = <&reg_dldo1>; + device-wakeup-gpios = <&pio 6 17 GPIO_ACTIVE_HIGH>; /* PG17 */ + vbat-supply = <&reg_dldo1>; + };

This should be PG18 not 12. 12 hex = 18 dec You want decimal in the linux dts. + reg_vcc_wifi: reg_vcc_wifi { + compatible = "regulator-fixed"; + regulator-name = "vcc-wifi"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + gpio = <&pio 6 18 GPIO_ACTIVE_HIGH>;/* PG18 WL_REG_ON */ + regulator-always-on; + enable-active-high; + status = "okay"; + }; Your BT should be something like this. + + bluetooth { + compatible = "brcm,bcm43438-bt"; + shutdown-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PG19 */ + clocks = <&rtc CLK_OSC32K_FANOUT>; + host-wakeup-gpios = <&pio 6 16 GPIO_ACTIVE_HIGH>; /* PG16 */ + clock-names = "lpo"; + vddio-supply = <&reg_dldo1>; + device-wakeup-gpios = <&pio 6 17 GPIO_ACTIVE_HIGH>; /* PG17 */ + vbat-supply = <&reg_dldo1>; + }; You need this patch. https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/Code-to-enable-Internal-OSC-Clock-Auto-Calibration.patch

One of your mmcblk2 patitions must have a dtb0_a.img in them. That wifi code was taken from the dts you had in your u-boot.patch you created. It doesn't look like your original dts.

Then you need to change your hdmi connector type to "a" connector { compatible = "hdmi-connector"; type = "a";

Can you run this command ls -al /dev/block/platform/soc@3000000/4022000.sdmmc/by-name Also can I see you dmesg? My hdmi connector is "a" type. connector { compatible = "hdmi-connector"; type = "a"; is your connector a micro-HDMI? Did you add these settings to both u-boot and kernel dts?

Here's more information that might help. https://linux-sunxi.org/TOC0 https://patchwork.ozlabs.org/project/uboot/patch/20210822044649.13585-3-samuel@sholland.org/#2746768 https://linux-sunxi.org/Jide_Remix_Mini#Tips.2C_Tricks.2C_Caveats

Rodrigo, try miniarch images until find one that has similar specs. https://github.com/warpme/miniarch/releases

I'm thinking the DTS that you extracted is a DTS for axp1530 but there might be an overlay that converts it back to axp305. If not then axp305 is compatible with axp1530 and all you have to do is change the dram settings in transpeed-8k618-t.defconfig. In this case you have all my warpme patches. The chip on your board does say axp305. So it's confusing why your android DTS has axp1530. Can you look for this partition and copy the dtbo_a file and extract it? dtbo_a -> /dev/block/mmcblk0p21

I'll be more active developing my build maybe adding more tv boxes after summer when work slows down.

Your android version of DTS has to be converted to the mainline linux DTS. I gave you enough information to get your box Ethernet running and maybe wifi. You're Ethernet is an easy fix. Change 0 to 1. I'm confused!! where did you get the DTS in your patches? The first link "01_dtbdump_,sun50iw9.dtb" didn't work. "devicetree.dts" says you have axp1530. If your box is a axp1530. I would use my transpeed build but change the dram settings in transpeed-8k618-t_defconfig. Use this tool to extract the dram settings. I think you can extract it using boot0. I hex edited my boot0 to get the settings. (post 8 on the first page.) https://github.com/apritzel/sunxi-fw Do you have a dtso partition? (DTS overlay) I'm guessing hdmi might be a pain to port over to u-boot. I haven't looked into it.

It's weird that you are booting further with tx6s but it shows your pmic isn't setup. I guess it has something to do with axp305 being defined in &r_i2c and &r_rsb. In &r_rsb it's defined as axp305: pmic@745. I guess without these changes you probably introduce more errors. INFO: PMIC: Probing AXP305 on RSB WARNING: PMIC: No regulators DT node, skipping setup +&r_i2c { + status = "okay"; + + axp305_1: pmic@36 { + compatible = "x-powers,axp305", "x-powers,axp805", + "x-powers,axp806"; + reg = <0x36>; + + /* dummy interrupt to appease the driver for now */ + interrupts = <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>; + interrupt-controller; + #interrupt-cells = <1>; + }; +}; But then axp305 goes back to normal in the kernel dtb and it's only defined once. Probably a uboot issue. https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.6/files/0632-arm64-dts-allwinner-h616-add-Tanix-TX6s-TVbox.patch Also, there's two Ethernet devices for H616 emac0 uses the external Ethernet chip. While, emac1 uses the SOC internal Ethernet phy called AC200. OrangePi-Zero2: (Uses external Ethernet chip) ethernet0 = &emac0; tx6s: (Miniarch uses emac1 but in your uboot.patch you have ethernet0 set to emac0!) I think this is where you are having problems. ethernet0 = &emac1; H618 is similar to H616 but it now has AC300 as the Ethernet phy.

Kajan, Your kernel patches need changes.. first you can't use your original android dtb as a dtsi file. Use your u-boot dtb. Make a copy and move it to your kernel. Then you can add changes like wifi. Your dtb already includes a dtsi file called sun50i-h616.dtsi. Normally, Both u-boot and kernel share the same dtb. But in our case it's different due to the mmc max-frequency and ethernet patches being different. The mmc max-frequency has changed to a lower frequency in the u-boot dts but not in the kernel dts. This is due to u-boot having issues reading mmc during boot. For now it's just a hack. Someone needs to figure out why u-boot is having this problem. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/107-sunxi_mmc-dec-f_max-to-12MHz-to-get-emmc-reliable.patch Here's my u-boot and kernel ethernet patches notice the differences. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/dts-Transpeed-8K618-T-Enable-Ethernet.patch https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-Transpeed-8k618-T-Enable-Ethernet.patch Looking at your original android dts for wifi I found this. + reg_vcc_wifi { + compatible = "regulator-fixed"; + regulator-name = "vcc-wifi"; + regulator-min-microvolt = <0x325aa0>; + regulator-max-microvolt = <0x325aa0>; + gpio = <0x15 0x06 0x12 0x00>; + regulator-always-on; + enable-active-high; + status = "okay"; + phandle = <0x13>; + }; + + wifi_pwrseq { + compatible = "mmc-pwrseq-simple"; + clocks = <0x0f 0x01>; + clock-names = "ext_clock"; + pinctrl-names = "default"; + pinctrl-0 = <0x41>; + phandle = <0x14>; + }; + + mmc@4021000 { + compatible = "allwinner,sun50i-h616-mmc\0allwinner,sun50i-a100-mmc"; + reg = <0x4021000 0x1000>; + clocks = <0x02 0x40 0x02 0x3d>; + clock-names = "ahb\0mmc"; + resets = <0x02 0x0f>; + reset-names = "ahb"; + interrupts = <0x00 0x24 0x04>; + pinctrl-names = "default"; + pinctrl-0 = <0x12>; + status = "okay"; + max-frequency = <0x0b71b00>; + cap-sd-highspeed; + cap-mmc-highspeed; + mmc-ddr-3_3v; + cap-sdio-irq; + #address-cells = <0x01>; + #size-cells = <0x00>; + vmmc-supply = <0x11>; + vqmmc-supply = <0x13>; + mmc-pwrseq = <0x14>; + bus-width = <0x04>; + non-removable; + + wifi@1 { + reg = <0x01>; + interrupt-parent = <0x15>; + interrupts = <0x06 0x0f 0x01>; + interrupt-names = "host-wake"; + }; + }; vmmc-supply = <0x11>; 0x11 is a phandle that points to dcdce. A regulator that is set to 3.3v. https://www.rapidtables.com/convert/number/hex-to-decimal.html 0x325aa0 = 3.3v vqmmc-supply = <0x13>; 0x13 phandle points to reg_vcc_wifi. A regulator that is set to 3.3v. So on your box both vmmc-supply and vqmmc-supply are set to 3.3v. + dcdce { + regulator-always-on; + regulator-min-microvolt = <0x325aa0>; + regulator-max-microvolt = <0x325aa0>; + regulator-name = "vcc-eth-mmc"; + phandle = <0x11>; + }; + reg_vcc_wifi { + compatible = "regulator-fixed"; + regulator-name = "vcc-wifi"; + regulator-min-microvolt = <0x325aa0>; + regulator-max-microvolt = <0x325aa0>; + gpio = <0x15 0x06 0x12 0x00>; + regulator-always-on; + enable-active-high; + status = "okay"; + phandle = <0x13>; + }; Looks similar to OrangePi-Zero2. You can modify the code and have it work on your box. OrangePi-Zero2 uses 1.8v for vqmmc-supply instead of 3.3v. So you don't need reg_vcc_wifi_io with 1.8v. Set vmmc-supply to reg_dcdce and vqmmc-supply to reg_vcc_wifi. reg_dcdce is already defined in your dtb file. + reg_dcdce: dcdce { + regulator-boot-on; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-name = "vcc-eth-mmc"; + }; Your gpio looks the same. 0x12 = 18 gpio = <0x15 0x06 0x12 0x00>; reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */ Have your tried OrangePi-Zero2 images? https://github.com/armbian/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-h616-add-wifi-support-for-orange-pi-zero-2.patch + + reg_vcc33_wifi: vcc33-wifi { + /* Always on 3.3V regulator for WiFi and BT */ + compatible = "regulator-fixed"; + regulator-name = "vcc33-wifi"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + vin-supply = <&reg_vcc5v>; + }; + + reg_vcc_wifi_io: vcc-wifi-io { + /* Always on 1.8V/300mA regulator for WiFi and BT IO */ + compatible = "regulator-fixed"; + regulator-name = "vcc-wifi-io"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + regulator-always-on; + vin-supply = <&reg_vcc33_wifi>; + }; + + wifi_pwrseq: wifi-pwrseq { + compatible = "mmc-pwrseq-simple"; + clocks = <&rtc 1>; + clock-names = "osc32k-out"; + reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */ + post-power-on-delay-ms = <200>; + }; +&mmc1 { + vmmc-supply = <&reg_vcc33_wifi>; + vqmmc-supply = <&reg_vcc_wifi_io>; + mmc-pwrseq = <&wifi_pwrseq>; + bus-width = <4>; + non-removable; + mmc-ddr-1_8v; + status = "okay"; +}; +

Kajen, I think that silver/gold chip on your board might be bluetooth/wifi. But I can't make out the number/letters written on it.

Kajen, For Ethernet you need these two patches in u-boot. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/100-sunsi-add-h616-internal-eth-phy-support.patch https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/106-Add-int-phy-eth-H313-h616-with-AC300.patch https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/dts-Transpeed-8K618-T-Enable-Ethernet.patch Kernel patch. You need to edit your box's dts. https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-Transpeed-8k618-T-Enable-Ethernet.patch Can you take a picture of your boards wifi chip?

Kil, have you tired the miniarch images? you might find a u-boot that works with your box. The u-boot I have is for AXP313. This could be the reason why your box doesn't show anything. You need a u-boot with AXP305. If you can't find a miniarch image that boots. You need to compile a new u-boot with your Dram settings and AXP305. Use the Dram Settings I got from your .DTS file. Download the lastest mainline u-boot. Use this board config. /configs/x96_mate_defconfig /arch/arm/dts/sun50i-h616-x96-mate.dts /arch/arm/dts/Makefile https://github.com/warpme/miniarch/releases https://source.denx.de/u-boot/u-boot https://docs.u-boot.org/en/latest/board/allwinner/sunxi.html Sorry Kil, I don't have your box and time to do this for you. I can only provide information. Without console output there's nothing I can do. Are you using baud rate 115200? If you need more help ask the Sunxi guys at: https://oftc.irclog.whitequark.org/linux-sunxi/2024-05-23

Here's a bunch of links related to your box and uboot. https://linux-sunxi.org/T95H https://linux-sunxi.org/BROM#eGON_Boot https://linux-sunxi.org/Bootable_SD_card#Bootloader https://linux-sunxi.org/U-Boot#Boot https://linux-sunxi.org/FEL#Through_a_special_SD_card_image https://docs.u-boot.org/en/latest/board/allwinner/sunxi.html https://linux-sunxi.org/H616 https://lore.kernel.org/lkml/?q=T95

Kil and Dmitriy can you guys try MiniArch. Steps to install MiniArch can be found here. https://github.com/warpme/miniarch Use the Tanix_tx6s image. https://github.com/warpme/miniarch/releases/download/v20240209/MiniArch-20231112-6.7.4-board-h616.tanix_tx6s-SD-Image.img.xz Dmitriy you can also try these images. Your dts has axp313 but your overlay adds axp806/axp305 values. https://github.com/warpme/miniarch/releases/download/v20240209/MiniArch-20231112-6.7.4-board-h616.tanix_tx6s_axp313-SD-Image.img.xz https://github.com/warpme/miniarch/releases/download/v20240209/MiniArch-20231112-6.7.4-board-h618.vontar_h618-SD-Image.img.xz The Tanix_tx6s has a similar dts. Compare your dts with this one. kernel: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.6/files/0632-arm64-dts-allwinner-h616-add-Tanix-TX6s-TVbox.patch U-boot: https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/52-add-tanix-tx6s-defconfig.patch dcdca { regulator-name = "axp806-dcdca"; regulator-min-microvolt = <0x927c0>; regulator-max-microvolt = <0x173180>; regulator-step-delay-us = <0x19>; regulator-final-delay-us = <0x32>; regulator-always-on; linux,phandle = <0x01>; phandle = <0x01>; }; + reg_dcdca: dcdca { + regulator-always-on; + regulator-min-microvolt = <810000>; + regulator-max-microvolt = <1160000>; + regulator-name = "vdd-cpu"; + }; https://www.rapidtables.com/convert/number/hex-to-decimal.html min = 600000 max = 1520000 You can also compare your dram setup values with the ones in the defconfig. If you have trouble booting you can use these values. (I was able to boot vontar image even tho these values where slightly different. ) dram_para1 { device_type = "dram_para1"; dram_clk = <0x00000288>; dram_type = <0x00000003>; dram_dx_odt = <0x03030303>; dram_dx_dri = <0x0e0e0e0e>; dram_ca_dri = <0x00001c1c>; dram_odt_en = <0x00000001>; dram_para1 = <0x000030fb>; dram_para2 = <0x00000000>; dram_mr0 = <0x00000840>; dram_mr1 = <0x00000004>; dram_mr2 = <0x00000008>; dram_mr3 = <0x00000000>; dram_mr4 = <0x00000000>; dram_mr5 = <0x00000000>; dram_mr6 = <0x00000000>; dram_mr11 = <0x00000000>; dram_mr12 = <0x00000000>; dram_mr13 = <0x00000000>; dram_mr14 = <0x00000000>; dram_mr16 = <0x00000000>; dram_mr17 = <0x00000000>; dram_mr22 = <0x00000000>; dram_tpr0 = <0xc0001305>; dram_tpr1 = <0x00000000>; dram_tpr2 = <0x00000000>; dram_tpr3 = <0x00000000>; dram_tpr6 = <0x33808080>; dram_tpr10 = <0x002f0006>; dram_tpr11 = <0xffffdddd>; dram_tpr12 = <0xfedf7657>; dram_tpr13 = <0x00000040>; }; +CONFIG_DRAM_CLK=648 . . . +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x03030303 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x00001c12 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x00000001 +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0000c05 +CONFIG_DRAM_SUN50I_H616_TPR2=0x00000000 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f0007 +CONFIG_DRAM_SUN50I_H616_TPR11=0xffffdddd +CONFIG_DRAM_SUN50I_H616_TPR12=0xfedf7557 If you want to create your own patches and Armbian build using my github, read the post at the top of this page..

These are the directories and files where all my changes are from. You need to compile a transpeed image first to get the ~/build/cache directory and patches applied. Once the patches are applied you can stop the kernel compile.. (ctrl c). The cache directory is created using root. So to edit the files you need to "sudo". https://github.com/NickAlilovic/build Bottom of this page shows how to create patches. I think linux-6.7.y branch name has changed. So use this command in linux and u-boot root directory to find the current branch name. git branch --show-current U-boot: ~/build/cache/sources/u-boot-worktree/u-boot/v2024.01/configs/transpeed-8k618-t_defconfig ~/build/cache/sources/u-boot-worktree/u-boot/v2024.01/arch/arm/dts/sun50i-h618-transpeed-8k618-t.dts ~/build/cache/sources/u-boot-worktree/u-boot/v2024.01/arch/arm/dts/Makefile Linux-Kernel: ~/build/cache/sources/linux-kernel-worktree/6.7__sunxi64__arm64/arch/arm64/boot/dts/allwinner/sun50i-h618-transpeed-8k618-t.dts ~/build/cache/sources/linux-kernel-worktree/6.7__sunxi64__arm64/arch/arm64/boot/dts/allwinner/Makefile Armbian: Armbian board config... ~/build/config/boards/transpeed-8k618-t.wip Patch directories... ~/build/patch/u-boot/u-boot-sunxi/ ~/build/patch/kernel/archive/sunxi-6.7/patches.armbian/ Kernel patches config... ( mines (-) before the patch name disables the patch) ~/build/patch/kernel/archive/sunxi-6.7/series.armbian ~/build/patch/kernel/archive/sunxi-6.7/series.conf firmware wifi/bluetooth... ~/build/packages/blobs/station/firmware/brcm/ We don't patch Armbian. Only U-boot and Linux-Kernel. If you want to edit transpeed-8k618-t.wip. Create your own wip (Work In Progress) for your box.

Dmitriy Geels any chance you can install a serial connection on the boards uart? Have you tried the desktop image yet? I see your board loaded axp313a. Also enable bluetooth in android before booting the sdcard. Your dts is not your full dts. It looks like dtbo_a an overlay file. You need to extract from boot_a and vendor_boot_a partition. Which is why I used Android_boot_image_editor. It extracted all my partitions with dts files in it without any problems. You only need to do the toothpick trick once. You might need to do the toothpick trick again when you change your sdcard image. Not sure. I'm thinking of updating Armbian again.. Too busy with work right now. If I encounter a failed build due to changes in Armbian I usually update A.S.A.P. Normally, I would fork the Armbian build and add all my changes again. If there's an easier way to do this let me know. Still new to github.

Kil if you go one page back you'll see how I used adb command to extract the .dts file from the stock android. for an H616 board you need the correct DRAM parameters, you can read them from a vendor image using https://github.com/apritzel/sunxi-fw. Maybe you can use the boot_a partition from adb to get your Dram parameters. It's important to know the model of the PMIC and its configuration, to get a board running. You don't want to burn out one of your components.

Dmitriy Geels I think your box is a H616.. again it's probably due to different PMIC (Power Management IC). Need more information. Do you have a serial log? can you post your kernel log?

Your box has a H616.. The problem is due to your box having a different PMIC (Power Management IC). [01.215]PMU: AXP806 Which is the same as axp305. My box uses AXP313a. https://linux-sunxi.org/AXP_PMICs I think you would have better luck booting an OrangePi Zero2 image. I would extract your boxes dts file and compare it with OrangePi Zero2. Make sure the voltages are correct. axp305: pmic@745 { compatible = "x-powers,axp305", "x-powers,axp805", "x-powers,axp806"; interrupt-controller; #interrupt-cells = <1>; reg = <0x745>; x-powers,self-working-mode; vina-supply = <&reg_vcc5v>; vinb-supply = <&reg_vcc5v>; vinc-supply = <&reg_vcc5v>; vind-supply = <&reg_vcc5v>; vine-supply = <&reg_vcc5v>; aldoin-supply = <&reg_vcc5v>; bldoin-supply = <&reg_vcc5v>; cldoin-supply = <&reg_vcc5v>; regulators { reg_aldo1: aldo1 { regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-sys"; }; reg_aldo2: aldo2 { /* 3.3V on headers */ regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc3v3-ext"; }; reg_aldo3: aldo3 { /* 3.3V on headers */ regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc3v3-ext2"; }; reg_bldo1: bldo1 { regulator-always-on; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <1800000>; regulator-name = "vcc1v8"; }; bldo2 { /* unused */ }; bldo3 { /* unused */ }; bldo4 { /* unused */ }; cldo1 { /* reserved */ }; cldo2 { /* unused */ }; cldo3 { /* unused */ }; reg_dcdca: dcdca { regulator-always-on; regulator-min-microvolt = <810000>; regulator-max-microvolt = <1100000>; regulator-name = "vdd-cpu"; }; reg_dcdcc: dcdcc { regulator-always-on; regulator-min-microvolt = <810000>; regulator-max-microvolt = <990000>; regulator-name = "vdd-gpu-sys"; }; reg_dcdcd: dcdcd { regulator-always-on; regulator-min-microvolt = <1500000>; regulator-max-microvolt = <1500000>; regulator-name = "vdd-dram"; }; reg_dcdce: dcdce { regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-eth-mmc"; }; sw { /* unused */ }; }; }; };