diff --git a/arch/arm64/boot/dts/exynos/google/zuma-husky.dts b/arch/arm64/boot/dts/exynos/google/zuma-husky.dts index f9d30456ae..38e9961a8f 100644 --- a/arch/arm64/boot/dts/exynos/google/zuma-husky.dts +++ b/arch/arm64/boot/dts/exynos/google/zuma-husky.dts @@ -228,16 +228,29 @@ status = "okay"; }; +&cmu_peric1 { + status = "okay"; +}; + +&sysreg_peric1 { + status = "okay"; +}; + +&usi11 { + status = "okay"; +}; + /* * MAX77759 (charger, Type-C port controller, fuel gauge, PMIC) on USI11 / * hsi2c_11. Like the Pixel 7 Pro's, but the interrupt lines are on gpa7 and - * gpa8. The bus and CMU_PERIC1 stay disabled here, and a bring-up overlay - * enables them. Binding the PMIC at 0x66 also creates its charger cell, - * and the charger driver then programs charge limits from the battery - * node, so max77759_charger, gpio_max77759, nvmem_max77759 and tcpci_maxim - * have to be kept from loading until each step is tested. The husky device - * package does not block them yet (cheetah's omamobile-max77759.conf - * does), and has to before an overlay that enables this bus ships. + * gpa8. The bus, USI11 and CMU_PERIC1 are enabled here: the USB replug + * rescue in the husky device package needs the bus (without it the phone + * leaves the USB bus on an unplug and stays off it after a replug). Binding + * the PMIC at 0x66 also creates its charger cell, and the charger driver + * then programs charge limits from the battery node, so max77759_charger, + * gpio_max77759, nvmem_max77759 and tcpci_maxim have to be kept from loading + * until each step is tested: the husky device package blocks them + * (omamobile-max77759.conf, as cheetah's does), so install it with this DTB. * * The fuel gauge has no battery model yet: the pack (ATL or COS, stock * reads its ID resistor) is not known, and a wrong model would be written @@ -246,6 +259,7 @@ */ &hsi2c_11 { clock-frequency = <400000>; + status = "okay"; usb-typec@25 { compatible = "maxim,max77759-tcpci", "maxim,max33359";