From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer
Date: Fri, 2 Jan 2015 20:53:51 +0100 [thread overview]
Message-ID: <20150102195350.GB27538@amd> (raw)
In-Reply-To: <20141226232116.GA5069@type>
Hi!
> Here is v5 coming, with separate patches for the kbd and the input
> parts.
After booting with this, capslock led does not seem to work on text
console.
input4::capsl/trigger was none by default, that can't be right, right?
I tried putting kbd-capslock and input4-capsl there, but that did not
seem to help.
It works with heartbeat trigger, but not with input4-numl
trigger. (But numlock led works ok with that trigger, weird).
vt::capsl/brightness controls capslock led, even when
input4-capsl/trigger is set to input4-numl.
Confused,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-01-02 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 23:21 [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Samuel Thibault
2014-12-26 23:21 ` [PATCHv5 1/2] INPUT: Introduce generic trigger/LED pairs between keyboard modifiers and input LEDs Samuel Thibault
2014-12-26 23:23 ` [PATCHv5 2/2] INPUT: Introduce generic trigger/LED pairs to " Samuel Thibault
2015-01-04 23:28 ` Dmitry Torokhov
2015-01-04 23:45 ` Samuel Thibault
2015-01-05 17:42 ` Dmitry Torokhov
2015-01-05 18:00 ` Samuel Thibault
2015-01-23 0:10 ` Samuel Thibault
2015-01-23 0:30 ` Samuel Thibault
2015-01-23 0:37 ` Dmitry Torokhov
2015-01-23 0:44 ` Samuel Thibault
2015-01-23 0:51 ` Dmitry Torokhov
2015-01-23 0:54 ` Samuel Thibault
2015-01-02 19:53 ` Pavel Machek [this message]
2015-01-02 20:11 ` [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Samuel Thibault
2015-01-03 19:47 ` Pavel Machek
2015-01-21 15:21 ` Samuel Thibault
2015-01-23 12:31 ` 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=20150102195350.GB27538@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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