Hello Shelley Chen, build bot (Jenkins), Furquan Shaikh, Tim Wawrzynczak, Nick Vaccaro,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/46620
to look at the new patch set (#4).
Change subject: mb/google/poppy/v/atlas: Reset bluetooth during boot ......................................................................
mb/google/poppy/v/atlas: Reset bluetooth during boot
Bluetooth is part of the Thunder Peak 2 module. This is a USB device that is not connected to any system level reset signals. Reset is done via a GPIO. When the SoC reboots, we need to reset Bluetooth so the device is in a known good state. BT_DISABLE_L needs to be asserted for a fairly long time - longer than the gap between early GPIO and main GPIO initialization (about 170ms). So, the recently added late GPIO init step is used to provide the necessary delay before taking the BT chip out of reset.
BRANCH=atlas BUG=b:168757348 TEST=Verified that we successfully reset the bluetooth chip. The quick way to check if the chip was reset is to look for dmesg entries from btusb_setup_intel_new indicating that firmware was downloaded right after rebooting.
Change-Id: I4c489963f7a353e8fc5f55b6cba7aaee0b347a37 Signed-off-by: Caveh Jalali caveh@chromium.org --- M src/mainboard/google/poppy/variants/atlas/gpio.c 1 file changed, 23 insertions(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/20/46620/4