diff options
author | Roderick Colenbrander <roderick@gaikai.com> | 2021-09-08 09:55:38 -0700 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2021-10-27 09:49:29 +0200 |
commit | 61177c088a57bed259122f3c7bc6d61984936a12 (patch) | |
tree | c41c70138c7968119a288a678df9060cc3d72e25 /Documentation/leds | |
parent | fc97b4d6a1a6d418fd4053fd7716eca746fdd163 (diff) | |
download | linux-rpi-61177c088a57bed259122f3c7bc6d61984936a12.tar.gz linux-rpi-61177c088a57bed259122f3c7bc6d61984936a12.tar.bz2 linux-rpi-61177c088a57bed259122f3c7bc6d61984936a12.zip |
leds: add new LED_FUNCTION_PLAYER for player LEDs for game controllers.
Player LEDs are commonly found on game controllers from Nintendo and Sony
to indicate a player ID across a number of LEDs. For example, "Player 2"
might be indicated as "-x--" on a device with 4 LEDs where "x" means on.
This patch introduces LED_FUNCTION_PLAYER1-5 defines to properly indicate
player LEDs from the kernel. Until now there was no good standard, which
resulted in inconsistent behavior across xpad, hid-sony, hid-wiimote and
other drivers. Moving forward new drivers should use LED_FUNCTION_PLAYERx.
Note: management of Player IDs is left to user space, though a kernel
driver may pick a default value.
Signed-off-by: Roderick Colenbrander <roderick.colenbrander@sony.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/leds')
-rw-r--r-- | Documentation/leds/well-known-leds.txt | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Documentation/leds/well-known-leds.txt b/Documentation/leds/well-known-leds.txt index 4a8b9dc4bf52..2160382c86be 100644 --- a/Documentation/leds/well-known-leds.txt +++ b/Documentation/leds/well-known-leds.txt @@ -16,6 +16,20 @@ but then try the legacy ones, too. Notice there's a list of functions in include/dt-bindings/leds/common.h . +* Gamepads and joysticks + +Game controllers may feature LEDs to indicate a player number. This is commonly +used on game consoles in which multiple controllers can be connected to a system. +The "player LEDs" are then programmed with a pattern to indicate a particular +player. For example, a game controller with 4 LEDs, may be programmed with "x---" +to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on. +Input drivers can utilize the LED class to expose the individual player LEDs +of a game controller using the function "player". +Note: tracking and management of Player IDs is the responsibility of user space, +though drivers may pick a default value. + +Good: "input*:*:player-{1,2,3,4,5} + * Keyboards Good: "input*:*:capslock" |