lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Jun 2019 23:59:58 +0200 From: Heiko Stuebner <heiko@...ech.de> To: Douglas Anderson <dianders@...omium.org> Cc: linux-rockchip@...ts.infradead.org, mka@...omium.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH] ARM: dts: rockchip: Configure BT_DEV_WAKE in on rk3288-veyron Am Mittwoch, 19. Juni 2019, 20:34:25 CEST schrieb Douglas Anderson: > This is the other half of the hacky solution from commit f497ab6b4bb8 > ("ARM: dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on > veyron"). Specifically the LPM driver that the Broadcom Bluetooth > expects to have (but is missing in mainline) has two halves of the > equation: BT_HOST_WAKE and BT_DEV_WAKE. The BT_HOST_WAKE (which was > handled in the previous commit) is the one that lets the Bluetooth > wake the system up. The BT_DEV_WAKE (this patch) tells the Bluetooth > that it's OK to go into a low power mode. That means we were burning > a bit of extra power in S3 without this patch. Measurements are a bit > noisy, but it appears to be a few mA worth of difference. > > NOTE: Though these pins don't do much on systems with Marvell > Bluetooth, downstream kernels set it on all veyron boards so we'll do > the same. > > Signed-off-by: Douglas Anderson <dianders@...omium.org> applied for 5.3 Thanks Heiko
Powered by blists - more mailing lists