Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about LED updates to README.md #16

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add note about LED updates to README.md #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,12 +38,21 @@ Tools for testing

Since this module uses the input subsystem, you can use standard tools such as
[evemu](http://cgit.freedesktop.org/evemu/) to test it. Outputs are
implemented using the leds subsystem and are consequently located in the
implemented using the LED subsystem and are consequently located in the
`/sys/class/leds` directory. You can test these by echoing zero/nonzero values
to the `brightness` file in a given led directory:

echo 1 > /sys/class/leds/piuio::output3/brightness

Note that for LEDs to update, there must be an active reader of the joystick
(pad) input device, otherwise changes made to the LED pseudofiles will not
affect a cab's lighting until the pads are next read from. That is, you may
want to run something like this in another terminal when testing:

cat /dev/input/js0

This will output binary garbage on every button / pad press, but will allow
LEDs to update.

Implementation and accuracy
---------------------------
Expand Down