linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Peter Stokes <linux@dadeos.co.uk>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH] ati_remote2 autorepeat and loadable keymap support
Date: Tue, 4 Mar 2008 14:47:15 +0200	[thread overview]
Message-ID: <20080304124715.GK8473@sci.fi> (raw)
In-Reply-To: <200802161622.43223.linux@dadeos.co.uk>

On Sat, Feb 16, 2008 at 04:22:43PM +0000, Peter Stokes wrote:
> The attached patch reconfigures the ati_remote2 driver to use soft-autorepeat 
> functionality and adds support for loadable key maps.

Why was this submitted (and even accepted) without cc:ing me?

> I have reconfigure the driver to use the input system's built-in autorepeat 
> functionality as the device only appears to be able to produce key repeat 
> notifications at a fixed period. Switching to the software autorepeat 
> functionality provides more precise configuration of the timings requested 
> for repeat-delay and repeat-rate.

The soft-autorepeat support should be split into a separate patch. I don't
need such fast repeat but if it helps people I'm fine with it.

> As this device is exposed as a combined keyboard and mouse, this change 
> somewhat depends upon the suggested modification to the core soft-autorepeat 
> functionality as outlined in my previous post to the linux-input mailing list 
> (on 12th Feb 2008 entitled "Soft-autorepeat functionality"), without that 
> modification, the mouse buttons are autorepeated :-(
> 
> The loadable keymap support exposes the ability to map 5 separate keycodes to 
> each key (depending on which "mode" the remote control is currently in). 
> Additionally, I have attempted to ensure that the scancodes used to map 
> keycodes to the keys lie outside of the range normally covered by regular 
> keyboards so as to avoid requests to remap the keys on the remote from being 
> intercepted by a normal keyboard.

I thought the idea of input devices was to reflect the hardware and the
keymaps should be handled in userspace. If that's not the case then I think
the keymap support code should not be inside the driver but instead inside
the input core. We don't want such invasive changes in every driver do
we?

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-03-04 12:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 16:22 [PATCH] ati_remote2 autorepeat and loadable keymap support Peter Stokes
2008-03-03 22:53 ` Jiri Kosina
2008-03-04 12:47 ` Ville Syrjälä [this message]
2008-03-04 13:20   ` Jiri Kosina
2008-03-04 13:47     ` Ville Syrjälä
2008-03-04 14:01       ` Jiri Kosina
2008-03-04 14:07         ` Ville Syrjälä
2008-03-04 18:40         ` Ville Syrjälä
2008-03-04 18:50           ` Jiri Kosina
2008-03-04 19:53             ` Ville Syrjälä
2008-03-04 20:28               ` Jiri Kosina
2008-03-04 20:32                 ` Ville Syrjälä
2008-03-04 20:42                   ` Jiri Kosina
2008-03-04 21:21                     ` Ville Syrjälä
2008-03-04 22:02                       ` Jiri Kosina
2008-03-04 18:55   ` Peter Stokes
2008-03-04 20:38     ` Ville Syrjälä
2008-03-04 21:34       ` Peter Stokes
2008-03-04 22:17         ` Ville Syrjälä
2008-03-04 22:25           ` Jiri Kosina
2008-03-25  8:23             ` Jiri Kosina
2008-04-07 20:39               ` 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=20080304124715.GK8473@sci.fi \
    --to=syrjala@sci.fi \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux@dadeos.co.uk \
    /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).