phy_mdm6600_device_power_on(9)
πΈ NAME πΈ
phy_mdm6600_device_power_on β power on mdm6600 device β¨
Okay so this is the Kernel API Manual page for it, bestie, and we're about to make it make sense. π
β¨ SYNOPSIS β¨
int phy_mdm6600_device_power_on (struct phy_mdm6600 *ddata );
π ARGUMENTS π
ddataβ device driver data, literally the driver's whole vibe check in one pointer π«Ά
π¦ DESCRIPTION π¦
Getting the integrated USB phy in MDM6600 up and running? Not a one-step slay, unfortunately. It takes some hoops, no cap. π
First we have to make sure the shared USB bootmode GPIOs are configured, then request modem start-up, reset and power-up. Then we need to recycle the shared USB bootmode GPIOs, because they're also used for Out of Band (OOB) wake for the USB and TS 27.010 serial mux. It's giving very "one GPIO, multiple jobs, main character energy" and we respect it. π
π SEE ALSO π
- Kernel file
./drivers/phy/motorola/phy-mapphone-mdm6600.c phy_mdm6600_cmd(9)phy_mdm6600_status(9)phy_mdm6600_wakeirq_thread(9)phy_mdm6600_init_irq(9)phy_mdm6600_init_lines(9)phy_mdm6600_device_power_off(9)
That's the whole page, bestie β source/version ./drivers/phy/motorola, dated October 2026, for phy_mdm6600_device_power_on(9). Periodt. πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms