mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-27 06:34:11 +08:00
2d8ff0b586
When Thunderbolt host controller is set to RTD3 mode (Runtime D3) it is present all the time. Because of this it is important to runtime suspend the controller whenever possible. In case of ICM we have following rules which all needs to be true before the host controller can be put to D3: - The controller firmware reports to support RTD3 - All the connected devices announce support for RTD3 - There is no active XDomain connection Implement this using standard Linux runtime PM APIs so that when all the children devices are runtime suspended, the Thunderbolt host controller PCI device is runtime suspended as well. The ICM firmware then starts powering down power domains towards RTD3 but it can prevent this if it detects that there is an active Display Port stream (this is not visible to the software, though). The Thunderbolt host controller will be runtime resumed either when there is a remote wake event (device is connected or disconnected), or when there is access from userspace that requires hardware access. Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
|---|---|---|
| .. | ||
| cap.c | ||
| ctl.c | ||
| ctl.h | ||
| dma_port.c | ||
| dma_port.h | ||
| domain.c | ||
| eeprom.c | ||
| icm.c | ||
| Kconfig | ||
| Makefile | ||
| nhi_regs.h | ||
| nhi.c | ||
| nhi.h | ||
| path.c | ||
| property.c | ||
| switch.c | ||
| tb_msgs.h | ||
| tb_regs.h | ||
| tb.c | ||
| tb.h | ||
| tunnel_pci.c | ||
| tunnel_pci.h | ||
| xdomain.c | ||