linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: simon@mungewell.org
Cc: linux-input@vger.kernel.org, jkosina@suse.cz,
	simon@mungewell.org, Frank Praznik <frank.praznik@oh.rr.com>
Subject: Re: [PATCH v5 0/7] HID: sony: More Sony controller fixes and improvements.
Date: Fri, 18 Apr 2014 13:24:42 -0400	[thread overview]
Message-ID: <dc5ee3d9ee47d1c6ccb5c6d632f0200f.squirrel@mungewell.org> (raw)
In-Reply-To: <1397484697-2389-1-git-send-email-frank.praznik@oh.rr.com>

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

>  -The new patch adds a 'global' LED to the DualShock 4 for synchronously
>   controlling the whole light bar and setting hardware blink rate.  Under
> the
>   old system where all of the LEDs mapped to one global blink rate
> triggers
>   would constantly override each other if different ones were assigned to
>   different color LEDs and triggers that run their own timers and adjust
> the
>   brightness directly couldn't be synchronously applied to the whole light
> bar.
>   Now, the global LED controls the hardware blink rate and can
> synchronously
>   toggle the state of the whole light bar without disturbing the
> individual
>   colors.  Additionally, if the user wants to apply different triggers to
>   the individual colors, that works as well.

Hi all,
I tested these patches again my controllers (USB connected DS4, DS3-SA and
Intec) and they seem to work OK. I did see some weirdness with DS4,
however I think that this is probably unavoidable with current LED class
and this controller - it probably needs some overall discussion how the
LED class treats RGB leds.

I'd suggest that we use this patch series.
Thanks,
Simon.

<tested-by> Simon Wood <simon@mungewell.org>


[-- Attachment #2: ds4leds.txt --]
[-- Type: text/plain, Size: 1008 bytes --]

DS4 failure when using 'global/timer', only reset by unplugging controller
--
# echo 80 > 0003\:054C\:05C4.0007\:green/brightness	[green]
# echo timer > 0003\:054C\:05C4.0007\:global/trigger	[flashing green]
# echo none > 0003\:054C\:05C4.0007\:global/trigger 	[off]
# echo 80 > 0003\:054C\:05C4.0007\:green/brightness	[off????]
--

DS3SA weirdness before PS button pressed (no jstest activity), works OK 
afer PS button is pressed
--
							[all flashing]
# echo 1 > 0003\:054C\:0268.0008\:\:sony1/brightness	[1 lit]
							[after a few sec starts all flashing]
--

DSA3SA wrong led, controller plugged in while 'on'. Only happened sometimes
--
							[1 lit automatically]
# echo 1 > 0003\:054C\:0268.0009\:\:sony1/brightness 	[1 lit]
# echo 2 > 0003\:054C\:0268.0009\:\:sony2/brightness 	[1+3 lit???]
--

Intec flashing does not (which we knew anyhow/expected)
--
# echo 1 > 0003\:054C\:0268.000D\:\:sony1/brightness 	[1 lit]
# echo timer > 0003\:054C\:0268.000D\:\:sony1/trigger 	[1 lit, not flashing]
--

  parent reply	other threads:[~2014-04-18 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 14:11 [PATCH v5 0/7] HID: sony: More Sony controller fixes and improvements Frank Praznik
2014-04-14 14:11 ` [PATCH v5 1/7] HID: sony: Use inliners for work queue initialization and cancellation Frank Praznik
2014-04-14 14:11 ` [PATCH v5 2/7] HID: sony: Use a struct for the Sixaxis output report Frank Praznik
2014-04-14 14:11 ` [PATCH v5 3/7] HID: sony: Convert startup and shutdown functions to use a uniform parameter type Frank Praznik
2014-04-14 14:11 ` [PATCH v5 4/7] HID: sony: Use the controller Bluetooth MAC address as the unique value in the battery name string Frank Praznik
2014-04-14 14:11 ` [PATCH v5 5/7] HID: sony: Initialize the controller LEDs with a device ID value Frank Praznik
2014-04-14 14:11 ` [PATCH v5 6/7] HID: sony: Add blink support to the Sixaxis and DualShock 4 LEDs Frank Praznik
2014-04-14 14:11 ` [PATCH v5 7/7] HID: hid-sony - allow 3rd party INTEC controller to turn off all leds Frank Praznik
2014-04-18 17:24 ` simon [this message]
2014-04-24 16:56 ` [PATCH v5 0/7] HID: sony: More Sony controller fixes and improvements Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dc5ee3d9ee47d1c6ccb5c6d632f0200f.squirrel@mungewell.org \
    --to=simon@mungewell.org \
    --cc=frank.praznik@oh.rr.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).