summaryrefslogtreecommitdiff
path: root/drivers/vme
diff options
context:
space:
mode:
authorSamuel Holland <samuel@sholland.org>2020-01-14 21:40:47 -0600
committerSebastian Reichel <sebastian.reichel@collabora.com>2020-01-15 21:40:59 +0100
commit09aaaec5f658a7cf04c6318ac794eafdb23fa240 (patch)
tree8c85180f63518186dbc5a940192b5aac42a87c3f /drivers/vme
parentecbc8dd78ed9fab5bc02d8cf2e839a3a0f2cdc5f (diff)
power: supply: axp20x_usb_power: Add wakeup control
The USB power supply input can be used as a wakeup source. Hook up the VBUS_PLUGIN IRQ to trigger wakeup based on userspace configuration. To do this, we must remember the list of IRQs for the life of the device. To know how much space to allocate for the flexible array member, we switch from using a NULL sentinel to using an array length. Because we now depend on the specific order of the IRQs (we assume VBUS_PLUGIN is first and always present), failing to acquire an IRQ during probe must be a fatal error. To avoid spuriously waking up the system when the USB power supply is not configured as a wakeup source, we must explicitly disable all non- wake IRQs during system suspend. This is because the SoC's NMI input is shared among all IRQs on the AXP PMIC. Due to the use of regmap-irq, the individual IRQs within the PMIC are nested threaded interrupts, and are therefore not automatically disabled during system suspend. The upshot is that if any other device within the MFD (such as the power key) is an enabled wakeup source, all enabled IRQs within the PMIC will cause wakeup. We still need to call enable_irq_wake() when we *do* want wakeup, in case those other wakeup sources on the PMIC are all disabled. Reviewed-by: Chen-Yu Tsai <wens@csie.org> Signed-off-by: Samuel Holland <samuel@sholland.org> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Diffstat (limited to 'drivers/vme')
0 files changed, 0 insertions, 0 deletions