REMOTE WAKE PC SOFTWARE
Thus, vendors are no longer required to supply a software DLL to implement the radio on/off control function. However, starting with Windows 8.1 and Windows RT 8.1, all Bluetooth radios in modern standby platforms should support the Bluetooth Core Specification Version 4.0. Previous versions of Windows, including Windows 8 and Windows 8 RT, require the Bluetooth device vendor to provide a radio control DLL. After the Bluetooth radio is turned off through this user interface, the radio is transitioned to the Off (D3) power state, in which it is expected to consume nearly zero watts. This user interface control is built into Windows.
The Bluetooth radio must also support the capability to turn off the radio through the radio management user interface. The power consumption can be expected to vary based on the number of associated devices, the types of those devices, and their activity patterns. The Bluetooth radio is expected to have a very low power consumption-less than one milliwatt-in the Sleep (D2) state if no devices are connected through RF links. Only paired Bluetooth HID device are allowed to wake the system during modern standby. To support wake from modern standby on Bluetooth-attached HID input devices, the radio stays in the Sleep (D2) state and is armed for wake. Instead, the Bluetooth radio is transitioned in and out of the Sleep (D2) state based on idle time-outs that are managed by BthPort. The Bluetooth radio does not enter a special power management mode when the system enters modern standby.
REMOTE WAKE PC DRIVER
The Windows Bluetooth driver stack requires that a Bluetooth radio support the following three device power states:ĭevice power management for a Bluetooth radio is expected to operate in a consistent way across all system power states. To control the hardware, the driver uses a combination of in-band bus communication, coordination with the power-engine plug-in (PEP), and/or out-of-band signaling through GPIO pins.īluetooth radio devices typically support multiple low-power modes, some of which may be proprietary to the device itself.
In the case of UART, an additional vendor-provided transport bus driver coordinates requests from BthPort to the Bluetooth radio device over the system-specific bus connection. In the case of USB, this is done through USB Selective Suspend via the USB host controller. BthPort works in conjunction with a corresponding transport-specific driver (UART or USB) to appropriately drive the radio into the desired power state.
Just as in typical Windows driver stacks, the Bluetooth radio power policy is managed by a single power policy owner (PPO) - specifically BthPort (bthport.sys).
Currently, Microsoft verifies modern standby compatibility only for Bluetooth radios that are connected to UARTs or USB, or are integrated into a System on a Chip (SoC)). (In theory, the Bluetooth transport bus driver model that was introduced in Windows 8 should support any underlying communication bus.
REMOTE WAKE PC SERIAL
On hardware platforms that support the modern standby power model, Windows supports Bluetooth radios that are connected to UARTs or to Universal Serial Bus (USB). In a Windows system, how the power state of the Bluetooth radio device is managed depends on the bus to which the radio is connected. In a modern standby PC, the driver for a Bluetooth radio should manage this device's power states according to the guidelines presented in this article. A Bluetooth radio device enables short-range RF communication between a PC and an input device, an audio device, or other Bluetooth-attached user peripheral.
0 kommentar(er)
