On 4/4/2014 12:11, simon@xxxxxxxxxxxxx wrote:
Why not make the triggers/etc apply across the board, so it doesn't matter
which led the command is sent to - it's just registered/copied to the
first (red?) led data[].
Unfortunately, it's not that simple. There is no API for setting
triggers from within the module and from looking at the code for these
triggers, some set the hardware blink rate which will blink the whole
light bar and some just use their own software timers and send
brightness commands which will only effect the LED they are set on which
results in unpredictable behavior depending on how the trigger is
implemented.
These software-only triggers are why I'm thinking it would be good to
have an extra global control for controlling the whole light bar
synchronously. Even if you set all the LEDs to the same software
trigger the colors may not flash in sync if the trigger starts a
separate timer for each LED and in some cases the trigger may mangle the
user defined brightness settings (ie. the heartbeat trigger doesn't read
the current brightness and just uses the maximum).
With an extra global switch, you can set the desired brightness levels
for each color, then just use the global control to set the on/off state
and get consistent blink behavior even if the trigger uses software
timers or doesn't care about the user's brightness settings. Plus, if
for some reason you do want to flash individual colors, setting the
blink rate of an individual color will always blink only that color
instead of potentially blinking the whole light bar if the trigger tries
to set the hardware blink rate.
I think it will be more functional, more predictable and less confusing.
3rd Party Intec - Was unable to get any controlled blinking.
It sounds like this controller just doesn't implement all of the
behavior of the official controller. I'm not sure how to fix it if it's
not obeying the instructions in valid output reports and I don't have
one to test personally. Do the lights flash properly when the
controller is used with a PS3?
I presume that they just reversed engineered what they thought to be
correct, I don't have a Playstation so can't confirm for certain.
In my testing from a year ago or so, I could make the blink work via
sending data with python. The script can be found here:
http://www.spinics.net/lists/linux-input/msg28271.html
Note: "Which LED to enable(LED1..4 << 1, 0x20=none)"
Cheers,
Simon
I'll take a look, but without having that particular controller all I
can do is take a shot in the dark.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
