You are not logged in.
Pages: 1
I noticed that LED power saving (brightness == 0, off) in throttle seems to work for the controller LEDs.
Oh neat! I thought. Let's have fun with DS3 leds!
First test:
# echo 1 > /sys/module/hid_sony/drivers/hid\:sony/0005\:054C\:0268.0006/leds/0005\:054C\:0268.0006\:\:sony1/brightness
LEDs (4321):
XXXO
Second test:
# echo 2 > /sys/module/hid_sony/drivers/hid\:sony/0005\:054C\:0268.0006/leds/0005\:054C\:0268.0006\:\:sony1/brightness
LEDs (4321):
XXOX
Third test:
# echo 3 > /sys/module/hid_sony/drivers/hid\:sony/0005\:054C\:0268.0006/leds/0005\:054C\:0268.0006\:\:sony1/brightness
LEDs (4321):
XXOO
Wat?
Fourth test:
# echo 4 > /sys/module/hid_sony/drivers/hid\:sony/0005\:054C\:0268.0006/leds/0005\:054C\:0268.0006\:\:sony1/brightness
LEDs (4321):
XOXX
Oh.
It's a binary vector!
1 = 0001, 2 = 0010, 3 = 0011, 4 = 0100, etc, 255 = 1111
Changing the led has no affect on input or connection state, but for reference:
Controller 1 is "1" and 2 is "2", but 3 is "4" and 4 is "8". All leds off (good for battery) is "0"; all on is "255". Invalid values are also off.
Coming soon to DS3: On-board battery and signal indicators?
EDIT: Since this post the kernel devs have seen if fit to radically alter how the leds work--there are now individual entries in sysfs for each led on the controller with the range 0~1.
Last edited by quequotion (2017-03-02 20:56:27)
makepkg-optimize · indicator-powersave · pantheon-{3d,lite} · {pantheon,higan}-qq
Offline
Pages: 1