All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 3 Jan 2015 20:47:25 +0100	[thread overview]
Message-ID: <20150103194725.GA13390@amd> (raw)
In-Reply-To: <20150102201117.GD25336@type.youpi.perso.aquilenet.fr>

On Fri 2015-01-02 21:11:17, Samuel Thibault wrote:
> Pavel Machek, le Fri 02 Jan 2015 20:53:51 +0100, a ?crit :
> > input4::capsl/trigger was none by default, that can't be right, right?
> 
> Indeed. And I don't see how it can be that way, since the input4::capsl
> LED and the input4-capsl trigger get initialized at the same time in
> input_led_connect... (and the order does not matter since both will
> try to connect to the other on registration).
> 
> > I tried putting kbd-capslock and input4-capsl there, but that did not
> > seem to help.
> 
> That should have.
> 
> > It works with heartbeat trigger, but not with input4-numl
> > trigger.
> 
> It should have worked with input4-numl too.
> 
> > vt::capsl/brightness controls capslock led, even when
> > input4-capsl/trigger is set to input4-numl.
> 
> It shouldn't.
> 
> > Confused,
> 
> I guess I'm even more.  I had tested everything that you have described,
> without any issue, on both an internal laptop keyboard and an external
> USB keyboard, and have tested again just now, with the same success.
> 
> Which hardware setup do you have, more precisely?

I tested on Thinkpad X60, with internal keyboard. (PS/2, I'd say). I
let Debian boot into graphical login prompt, switched to text console,
and did the testing there.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Herrmann" <dh.herrmann@gmail.com>,
	jslaby@suse.cz, "Bryan Wu" <cooloney@gmail.com>,
	rpurdie@rpsys.net, linux-kernel@vger.kernel.org,
	"Evan Broder" <evan@ebroder.net>,
	"Arnaud Patard" <arnaud.patard@rtp-net.org>,
	"Peter Korsgaard" <jacmet@sunsite.dk>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Rob Clark" <robdclark@gmail.com>,
	"Niels de Vos" <devos@fedoraproject.org>,
	linux-arm-kernel@lists.infradead.org, blogic@openwrt.org,
	"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer
Date: Sat, 3 Jan 2015 20:47:25 +0100	[thread overview]
Message-ID: <20150103194725.GA13390@amd> (raw)
In-Reply-To: <20150102201117.GD25336@type.youpi.perso.aquilenet.fr>

On Fri 2015-01-02 21:11:17, Samuel Thibault wrote:
> Pavel Machek, le Fri 02 Jan 2015 20:53:51 +0100, a écrit :
> > input4::capsl/trigger was none by default, that can't be right, right?
> 
> Indeed. And I don't see how it can be that way, since the input4::capsl
> LED and the input4-capsl trigger get initialized at the same time in
> input_led_connect... (and the order does not matter since both will
> try to connect to the other on registration).
> 
> > I tried putting kbd-capslock and input4-capsl there, but that did not
> > seem to help.
> 
> That should have.
> 
> > It works with heartbeat trigger, but not with input4-numl
> > trigger.
> 
> It should have worked with input4-numl too.
> 
> > vt::capsl/brightness controls capslock led, even when
> > input4-capsl/trigger is set to input4-numl.
> 
> It shouldn't.
> 
> > Confused,
> 
> I guess I'm even more.  I had tested everything that you have described,
> without any issue, on both an internal laptop keyboard and an external
> USB keyboard, and have tested again just now, with the same success.
> 
> Which hardware setup do you have, more precisely?

I tested on Thinkpad X60, with internal keyboard. (PS/2, I'd say). I
let Debian boot into graphical login prompt, switched to text console,
and did the testing there.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-01-03 19:47 UTC|newest]

Thread overview: 36+ 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 ` 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:21   ` Samuel Thibault
2014-12-26 23:23 ` [PATCHv5 2/2] INPUT: Introduce generic trigger/LED pairs to " Samuel Thibault
2014-12-26 23:23   ` Samuel Thibault
2015-01-04 23:28   ` Dmitry Torokhov
2015-01-04 23:28     ` Dmitry Torokhov
2015-01-04 23:45     ` Samuel Thibault
2015-01-04 23:45       ` Samuel Thibault
2015-01-05 17:42       ` Dmitry Torokhov
2015-01-05 17:42         ` Dmitry Torokhov
2015-01-05 18:00         ` Samuel Thibault
2015-01-05 18:00           ` Samuel Thibault
2015-01-23  0:10     ` Samuel Thibault
2015-01-23  0:10       ` Samuel Thibault
2015-01-23  0:30       ` Samuel Thibault
2015-01-23  0:30         ` Samuel Thibault
2015-01-23  0:37         ` Dmitry Torokhov
2015-01-23  0:37           ` Dmitry Torokhov
2015-01-23  0:44           ` Samuel Thibault
2015-01-23  0:44             ` Samuel Thibault
2015-01-23  0:51             ` Dmitry Torokhov
2015-01-23  0:51               ` Dmitry Torokhov
2015-01-23  0:54               ` Samuel Thibault
2015-01-23  0:54                 ` Samuel Thibault
2015-01-02 19:53 ` [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Pavel Machek
2015-01-02 19:53   ` Pavel Machek
2015-01-02 20:11   ` Samuel Thibault
2015-01-02 20:11     ` Samuel Thibault
2015-01-03 19:47     ` Pavel Machek [this message]
2015-01-03 19:47       ` Pavel Machek
2015-01-21 15:21   ` Samuel Thibault
2015-01-21 15:21     ` Samuel Thibault
2015-01-23 12:31     ` 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=20150103194725.GA13390@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.