From: Antonio Ospite <ao2@ao2.it>
To: linux-bluetooth@vger.kernel.org
Cc: Antonio Ospite <ao2@ao2.it>, Bastien Nocera <hadess@hadess.net>,
Szymon Janc <szymon.janc@gmail.com>,
Frank Praznik <frank.praznik@oh.rr.com>
Subject: [PATCH BlueZ 0/5] plugin/sixaxis: use the sysfs leds class
Date: Tue, 6 May 2014 12:06:11 +0200 [thread overview]
Message-ID: <1399370776-5027-1-git-send-email-ao2@ao2.it> (raw)
Hi,
on kernels >= 3.14 the hid-sony driver exposes leds class entries in
sysfs for setting the Sixaxis LEDs, the patches in this set make BlueZ
use this interface as the default one and fall-back to hidraw in case
using sysfs fails (e.g. on older hid-sony versions).
Patch 1 is a cleanup, it's optional, feel free to reject it; the libudev
version bump is needed for patch 5 tho.
Patches 2,3 and 4 are refactorings in preparation of patch 5.
Patch 5 adds the actual support for the sysfs mechanism.
The changes have been tested with libudev-204 along with linux-3.13,
linux 3.14 and linux-3.15-rc4, however some more testing with different
libudev and kernel versions won't hurt :)
Thanks,
Antonio
Antonio Ospite (5):
plugins/sixaxis: simplify get_js_numbers()
plugins/sixaxis: factor out a set_leds_hidraw() function
plugins/sixaxis: factor out a calc_leds_bitmap() function
plugins/sixaxis: add a get_leds_data() function
plugins/sixaxis: add a set_leds_sysfs() function
configure.ac | 4 +-
plugins/sixaxis.c | 256 ++++++++++++++++++++++++++++++++++++++++--------------
2 files changed, 193 insertions(+), 67 deletions(-)
--
Antonio Ospite
http://ao2.it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next reply other threads:[~2014-05-06 10:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:06 Antonio Ospite [this message]
2014-05-06 10:06 ` [PATCH BlueZ 1/5] plugins/sixaxis: simplify get_js_numbers() Antonio Ospite
2014-05-07 19:57 ` Szymon Janc
2014-05-06 10:06 ` [PATCH BlueZ 2/5] plugins/sixaxis: factor out a set_leds_hidraw() function Antonio Ospite
2014-05-07 19:58 ` Szymon Janc
2014-05-06 10:06 ` [PATCH BlueZ 3/5] plugins/sixaxis: factor out a calc_leds_bitmap() function Antonio Ospite
2014-05-07 19:59 ` Szymon Janc
2014-05-06 10:06 ` [PATCH BlueZ 4/5] plugins/sixaxis: add a get_leds_data() function Antonio Ospite
2014-05-07 20:04 ` Szymon Janc
2014-05-09 12:22 ` Johan Hedberg
2014-05-09 13:31 ` Antonio Ospite
2014-05-06 10:06 ` [PATCH BlueZ 5/5] plugins/sixaxis: add a set_leds_sysfs() function Antonio Ospite
2014-05-07 20:24 ` Szymon Janc
2014-05-14 21:40 ` [PATCHv2 BlueZ 0/5] plugin/sixaxis: Set leds using the sysfs leds class Antonio Ospite
2014-05-14 21:40 ` [PATCHv2 BlueZ 2/5] plugins/sixaxis: Factor out a set_leds_hidraw() function Antonio Ospite
2014-05-14 21:40 ` [PATCHv2 BlueZ 3/5] plugins/sixaxis: Factor out a calc_leds_bitmap() function Antonio Ospite
2014-05-14 21:40 ` [PATCHv2 BlueZ 4/5] plugins/sixaxis: Add a get_leds_data() function Antonio Ospite
2014-05-15 20:25 ` Szymon Janc
2014-05-16 8:13 ` Antonio Ospite
2014-05-14 21:40 ` [PATCHv2 BlueZ 5/5] plugins/sixaxis: Add a set_leds_sysfs() function Antonio Ospite
2014-05-15 20:25 ` Szymon Janc
2014-05-15 15:28 ` [PATCHv2 BlueZ 0/5] plugin/sixaxis: Set leds using the sysfs leds class Frank Praznik
2014-05-15 16:33 ` Antonio Ospite
2014-05-16 12:37 ` Szymon Janc
2014-05-27 11:25 ` [PATCHv3 " Antonio Ospite
2014-05-27 11:25 ` [PATCHv3 BlueZ 4/5] plugins/sixaxis: Add a get_leds_data() function Antonio Ospite
2014-05-27 11:25 ` [PATCHv3 BlueZ 5/5] plugins/sixaxis: Add a set_leds_sysfs() function Antonio Ospite
2014-06-08 12:58 ` [PATCHv3 BlueZ 0/5] plugin/sixaxis: Set leds using the sysfs leds class Szymon Janc
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=1399370776-5027-1-git-send-email-ao2@ao2.it \
--to=ao2@ao2.it \
--cc=frank.praznik@oh.rr.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@gmail.com \
/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).