Ticket #1744 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

Bluetooth don't power up after suspend

Reported by: VDVsx Owned by: openmoko-kernel
Priority: normal Milestone:
Component: kernel Version: GTA02v6
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

The bluetooth system don't power up after the system suspend.

Test Cases:

1- System suspend and bluetooth power up

  • suspend the system and resume;
  • Start bluetooth system with the commands:

echo 1 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/power_on
echo 0 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/reset

Result: Bluetooth don't power up

2- power up bluetooth and suspend

  • Power up the bluetooth system with the commands above;
  • Suspend and resume the system;

Result: Bluetooth still on

Env:
openmoko-fso-image-glibc-ipk--20080729-om-gta02.rootfs.jffs2.summary
uImage-2.6.24+gitr0+7a1370a816b9348dd8f36a667905dd3533cefc9b-r4-om-gta02.bin

Change History

comment:1 Changed 11 years ago by zecke

  • Status changed from new to assigned
  • Owner changed from julian_chu to openmoko-kernel
  • Component changed from Distro to System Software
  • Milestone FSO deleted

comment:2 Changed 10 years ago by Nytowl

I'm seeing the same thing from the sept 4 rootfs and kernel updates to 2008.8

What I also noticed is that bluetooth does power up but the state variable is reversed

comment:3 Changed 10 years ago by TimoJyrinki

Still a problem with andy-tracking de473ca893. After suspend Bluetooth is unusable until reboot, no matter how the power_on/reset are used.

This is an unfortunate in an use case that one would like to wake up the device for some Bluetooth action (like GPRS over Bluetooth), but one has to reboot every time to do that now.

comment:4 Changed 10 years ago by andy

  • HasPatchForReview unset

andy-tracking has a different problem with it that's a known issue... we moved to rfkill and there is an "impedence mismatch" right now with the new PMU regulator APIs. This will get ironed out soon.

comment:5 Changed 10 years ago by lysgaard

I can confirm this bug:
OM2008.12, fresh rootfs and kernel

comment:6 Changed 10 years ago by TimoJyrinki

This is still an issue in the current stable (2.6.29, quite close to andy-tracking AFAIK).

comment:7 Changed 10 years ago by TimoJyrinki

(also andy-tracking as of today, 86247495c3d585)

comment:8 Changed 10 years ago by balajirrao

I see this. When the phone suspends with bluetooth on, it comes up properly. But when suspended with bluetooth off, it can't be powered up.

Will look into it now.

comment:9 Changed 10 years ago by TimoJyrinki

Balaji's commit from the day before yesterday seems to indeed fix this. I cannot break Bluetooth currently anymore with suspend, whether the Bluetooth is on or off before the suspend.

http://git.openmoko.org/?p=kernel.git;a=commit;h=75d17a700b015cd5e99636db035c8bd1324eeca4

comment:10 Changed 10 years ago by balajirrao

  • Status changed from assigned to closed
  • Resolution set to fixed

Thank you for confirming this.

Note: See TracTickets for help on using tickets.