linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev keymaps: support for force_release quirk
Date: Fri, 27 Nov 2009 15:33:51 +0000	[thread overview]
Message-ID: <20091127153351.GF24295@piware.de> (raw)
In-Reply-To: <20091126173912.GA25185@sig21.net>

Hello Johannes,

Johannes Stezenbach [2009-11-26 18:39 +0100]:
> I guess it would make sense to add support for the forced release
> attribute into extras/keymap/keymap.c

Indeed, that'd need to happen now that it gets pushed out of the
kernel.

> in such a way that the keymap files (e.g. samsung-other) can have an
> optional third column with flags.

This sounds good.

> Since many models share samsung-other, but only
> three had the force_release handled in to the kernel
> I'd also add a flag to keymap.c so that the
> forced_release flag is only applied when the --force-release/-f
> switch is present.

I don't understand this. We need separate rules for the quirked vs.
non-quirked models anyway, so why would we need this -f switch if we
already specify it in the rules? I think I see what you try to do, but
IMHO it would just make matters more confusing, and not really help to
reduce rules either.

> The we can add two lines to 95-keymap.rules,
> one for models which need the quirk and one fo the others.
> On an older kernel which doesn't support the force_release
> sysfs attribute the flag would be silently ignored.
> 
> Entries in samsung-other would then look like this:
> 
> 0x82 switchvideomode force_release # Fn+F4 CRT/LCD (high keycode: "displaytoggle")
> 0x83 battery force_release,some_other_flag # Fn+F2
> 0x84 prog1 # Fn+F5 backlight on/off

This looks good.

> Should I go forward and try to implement it?

That would be great!

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

  reply	other threads:[~2009-11-27 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 17:39 udev keymaps: support for force_release quirk Johannes Stezenbach
2009-11-27 15:33 ` Martin Pitt [this message]
2009-11-27 15:48 ` Johannes Stezenbach
2009-11-27 15:57 ` Martin Pitt
2009-11-28 19:14 ` Greg KH
2009-11-28 21:36 ` Johannes Stezenbach
2009-11-30 23:27 ` Johannes Stezenbach
2009-12-01  1:28 ` Kay Sievers
2009-12-01  1:37 ` Dmitry Torokhov
2009-12-01  1:49 ` Kay Sievers
2009-12-01  1:52 ` Johannes Stezenbach
2009-12-01  1:55 ` Kay Sievers
2009-12-01  2:21 ` Johannes Stezenbach
2009-12-03  3:12 ` Dmitry Torokhov
2009-12-06 21:49 ` Johannes Stezenbach

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=20091127153351.GF24295@piware.de \
    --to=martin.pitt@ubuntu.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).