From: cascardo@holoscopio.com
To: Yong Wang <yong.y.wang@linux.intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Corentin Chary <corentincj@iksaif.net>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] eeepc-wmi: new driver for WMI based hotkeys on Eee PC laptops
Date: Sat, 20 Mar 2010 09:20:50 -0300 [thread overview]
Message-ID: <20100320122049.GA1478@holoscopio.com> (raw)
In-Reply-To: <20100320005553.GB32163@ywang-moblin2.bj.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
On Sat, Mar 20, 2010 at 08:55:53AM +0800, Yong Wang wrote:
> On Fri, Mar 19, 2010 at 03:23:23PM +0000, Matthew Garrett wrote:
> >
> > > > > + if (code >= NOTIFY_BRNUP_MIN && code <= NOTIFY_BRNUP_MAX)
> > > > > + code = NOTIFY_BRNUP_MIN;
> > > > > + else if (code >= NOTIFY_BRNDOWN_MIN && code <= NOTIFY_BRNDOWN_MAX)
> > > > > + code = NOTIFY_BRNDOWN_MIN;
> > > >
> > > > Do the brightness keys just send notifications, or do they actually
> > > > change the brightness? If they actually change the brightness, we
> > > > shouldn't send input events.
> > > >
> > >
> > > Yes, hardware and bios change brightness by themselves without software intervention
> > > on my Eee PC 1005 when pressing the hotkeys.
> >
> > Ok. In that case, you shouldn't send input events. Once backlight
> > control is implemented in the eee-wmi driver you can send notifications
> > via that instead.
> >
>
> One question just popped off the top my head. What if there is a power
> applet that wants to display a slider field at the bottom of the screen
> showing the current brightness real time whenever users press brightness
> hotkeys? Shouldn't it listen to the standard input events translated by
> X into standard XF86 keysyms? Or shall it listen to the ACPI backlight
> events? If so, it is the ACPI LCD event when using acpi backlight
> driver. But what if those vendor specific backlight drivers are used?
>
> Thanks
> -Yong
> --
You may select/poll for the sysfs file actual_brightness. It will return
POLLPRI. Basically, backlight devices end up calling sysfs_notify that
will allow sysfs_poll to work. Read the comments about sysfs_poll at
fs/sysfs/file.c.
You should either use backlight_force_update in your driver or let the
user update it writing to the brightness file. In your case, I'd say you
should use backlight_force_update and give BACKLIGHT_UPDATE_HOTKEY as
the reason.
Regards,
Cascardo.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-20 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100319133924.GA30427@ywang-moblin2.bj.intel.com>
2010-03-19 13:59 ` [PATCH] eeepc-wmi: new driver for WMI based hotkeys on Eee PC laptops Matthew Garrett
2010-03-19 15:10 ` Yong Wang
2010-03-19 15:23 ` Matthew Garrett
2010-03-19 15:21 ` Yong Wang
2010-03-20 0:55 ` Yong Wang
2010-03-20 12:20 ` cascardo [this message]
2010-03-20 12:24 ` Yong Wang
2010-03-20 17:21 ` Corentin Chary
2010-03-21 0:59 ` Yong Wang
2010-03-21 13:14 ` Corentin Chary
2010-03-21 13:35 ` Yong Wang
2010-03-21 13:55 ` Corentin Chary
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=20100320122049.GA1478@holoscopio.com \
--to=cascardo@holoscopio.com \
--cc=corentincj@iksaif.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yong.y.wang@linux.intel.com \
/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).