devs/foxbox
1
0
Fork 0
forked from len0rd/rockbox
Code Pull requests Activity

fuze+: workaround the power/volume+ multiplexing that would trigger a false power button detection on heavy usage (FS#12405). Thanks to Jean-Louis Biasini

Browse source 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@31599 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Amaury Pouly 2012-01-07 18:01:01 +00:00
parent fdf574adb4
commit 4200e979fa
1 changed files with 18 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

22
firmware/target/arm/imx233/sansa-fuzeplus/button-fuzeplus.c
View file

@ -349,12 +349,26 @@ int button_read_device(void)
* events as well as recovery mode. Since the power button is the power button * events as well as recovery mode. Since the power button is the power button
* and the volume up button is recovery, it is not possible to know whether * and the volume up button is recovery, it is not possible to know whether
* power button is down when volume up is down (except if there is another * power button is down when volume up is down (except if there is another
* method but volume up and power don't seem to be wired to GPIO pins). */ * method but volume up and power don't seem to be wired to GPIO pins).
* As a probable consequence of that, it has been reported that pressing
* volume up sometimes return BUTTON_POWER instead of BUTTON_VOL_UP. The
* following volume_power_lock prevent BUTTON_POWER to happen if volume up
* has been send since a very short time. */
static int volume_power_lock = 0;
if(volume_power_lock > 0)
volume_power_lock--;
switch(__XTRACT(HW_POWER_STS, PSWITCH)) switch(__XTRACT(HW_POWER_STS, PSWITCH))
{ {
case 1: res |= BUTTON_POWER; break; case 1:
case 3: res |= BUTTON_VOL_UP; break; if(volume_power_lock == 0)
default: break; res |= BUTTON_POWER;
break;
case 3:
res |= BUTTON_VOL_UP;
volume_power_lock = 5;
break;
default:
break;
} }
return res | touchpad_read_device(); return res | touchpad_read_device();
} }