From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: rpurdie@rpsys.net, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] leds: add keyboard num/caps lock trigger
Date: Mon, 17 Jan 2011 00:54:05 +0100 [thread overview]
Message-ID: <87aaj01k2q.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20110113131323.GJ5995@const.bordeaux.inria.fr> (Samuel Thibault's message of "Thu, 13 Jan 2011 14:13:23 +0100")
Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
> Hello,
Hi,
>
>
> Arnaud Patard, le Thu 13 Jan 2011 13:59:13 +0100, a écrit :
>> Implement a led trigger which enable/disable a led according
>> to keyboard leds events.
>
> This is already being implemented in a more generic and useful way,
> also permitting to use the keyboard leds for other triggers, see the
> leds-route-kbd-leds-through-the-generic-leds-layer.patch in the mm tree,
> and the “route kbd LEDs through the generic LEDs layer” thread here.
I've download the patch at [1] and after a quick runtime test, got no
success. When booting with the LEDS_INPUT set to y, the machine is
hanging. I didn't have a serial console at hand so no log for now. I've
then tried it as module, and it didn't work too. No freeze, but led
state did not change.
Moreover, I found a bug. The kbd_update_leds_helper() change is
wrong. It should use !!(leds & (1<<VC_*)) and not !!(leds & VC_*).
btw, my use case/problem is different than yours. I've a arm system
where the keyboard is usb hid one and the led I'm trying to control a
led connected on a gpio.
Arnaud
[1] http://userweb.kernel.org/~akpm/mmotm/broken-out/leds-route-kbd-leds-through-the-generic-leds-layer.patch
next prev parent reply other threads:[~2011-01-16 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 12:59 [patch 1/1] leds: add keyboard num/caps lock trigger Arnaud Patard
2011-01-13 13:13 ` Samuel Thibault
2011-01-16 23:54 ` Arnaud Patard [this message]
2011-01-23 22:55 ` Samuel Thibault
2011-11-14 0:03 ` Samuel Thibault
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=87aaj01k2q.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=samuel.thibault@ens-lyon.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