diff options
| author | Kevin Hilman <[email protected]> | 2024-12-06 22:12:52 +0000 |
|---|---|---|
| committer | Ulf Hansson <[email protected]> | 2024-12-10 11:37:26 +0000 |
| commit | b06bc47279919628b328710f7767ea7a18a68973 (patch) | |
| tree | 53042d9dbbafa805729d43d3bb30a04f97b07170 /net/switchdev/switchdev.c | |
| parent | pmdomain: ti_sci: add wakeup constraint management (diff) | |
| download | kernel-b06bc47279919628b328710f7767ea7a18a68973.tar.gz kernel-b06bc47279919628b328710f7767ea7a18a68973.zip | |
pmdomain: ti_sci: handle wake IRQs for IO daisy chain wakeups
When a device supports IO daisy-chain wakeups, it uses a dedicated
wake IRQ. Devices with IO daisy-chain wakeups enabled should not set
wakeup constraints since these can happen even from deep power states,
so should not prevent the DM from picking deep power states.
Wake IRQs are set with dev_pm_set_wake_irq() or
dev_pm_set_dedicated_wake_irq(). The latter is used by the serial
driver used on K3 platforms (drivers/tty/serial/8250/8250_omap.c)
when the interrupts-extended property is used to describe the
dedicated wakeup interrupt.
Detect these wake IRQs in the suspend path, and if set, skip sending
constraint.
Tested-by: Dhruva Gole <[email protected]>
Signed-off-by: Kevin Hilman <[email protected]>
Reviewed-by: Dhruva Gole <[email protected]>
Message-ID: <20241206-lpm-v6-10-constraints-pmdomain-v6-3-833980158c68@baylibre.com>
Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions