From: Yong Wang <yong.y.wang@linux.intel.com>
To: cascardo@holoscopio.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 20:24:16 +0800 [thread overview]
Message-ID: <20100320122416.GA10558@ywang-moblin2.bj.intel.com> (raw)
In-Reply-To: <20100320122049.GA1478@holoscopio.com>
On Sat, Mar 20, 2010 at 09:20:50AM -0300, cascardo@holoscopio.com wrote:
> On Sat, Mar 20, 2010 at 08:55:53AM +0800, Yong Wang wrote:
> >
> > 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.
>
Oh, I see. Thank for clarifying, Cascardo.
-Yong
next prev parent reply other threads:[~2010-03-20 12:33 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
2010-03-20 12:24 ` Yong Wang [this message]
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=20100320122416.GA10558@ywang-moblin2.bj.intel.com \
--to=yong.y.wang@linux.intel.com \
--cc=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 \
/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.