From: Dmitry Torokhov <dtor@insightbb.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org, Dan Engel <dan@sourceharvest.com>
Subject: Re: [PATCH] hid: add two led codes to hid input mapping
Date: Sun, 1 Apr 2007 10:57:40 -0400 [thread overview]
Message-ID: <200704011057.40725.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704011057420.6040@jikos.suse.cz>
On Sunday 01 April 2007 05:01, Jiri Kosina wrote:
> On Sat, 31 Mar 2007, Dan Engel wrote:
>
> > This patch is really being offered because it's what's needed to make the operation
> > of the Belkin Flip USB KVM switch avaiable to user-space programs through the HID input
> > event interface. The Belkin Flip KVM overloads LED usages to give software control
> > over the device, providing options to flip either audio, video or both. However,
> > without an input mapping to the Off-hook and Speaker LED usages, this functionality
> > isn't available.
>
> Dmitry, would adding these two LED_ constants to input.h be OK by you?
> (the coresponding usages are defined in HUT 1.12 on page 62).
>
No, I do not want to add any more LED constants to input. In fact I think
that adding constants beyond keyboard indicators was a mistake. We have
led subsystem that provides interface to control arbitrary leds and we
should use it.
--
Dmitry
next prev parent reply other threads:[~2007-04-01 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 2:56 [PATCH] hid: add two led codes to hid input mapping Dan Engel
2007-04-01 9:01 ` Jiri Kosina
2007-04-01 14:57 ` Dmitry Torokhov [this message]
2007-04-01 17:43 ` Jiri Kosina
2007-04-02 3:28 ` Dan Engel
2007-04-02 4:04 ` Dmitry Torokhov
2007-04-02 10:14 ` Dan Engel
2007-04-02 13:06 ` Dmitry Torokhov
2007-04-02 13:33 ` Dan Engel
2007-04-02 13:46 ` Dmitry Torokhov
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=200704011057.40725.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=dan@sourceharvest.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@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