Hi,
In one of our future hardware designs, we have a MPU (running LInux) connected to a Bluetooth SOC over a serial interface (uart/spi/...).
Our first approach was to use Bluez on the MPU side and control the Bluetooth SOC using the HCI interface. This works quite well to handle the basic communication requirements of our system.
However, we also have a requirement to implement power saving modes where the MPU is completely off. The Bluetooth SOC should then be able to wake-up the MPU. As we want to avoid unneeded wake-ups, we do not want to wake the MPU on each connection request (as a smartphone might try to connect even if the user does not intend to use the device). Are there any other options that can be used as wake-up events?
There is an idea to use a special "power states" Gatt service. The smartphone would then be able to query the power state and if required, send a wake-up command. However, as far as we can see, it would then no longer be possible to use the Bluez stack (as the Gatt services are defined on the host side). Is this correct?
Have you seen similar requirements in the past? Do you have any recommendations?
KInd regards,
Yoshi
