From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: toshiba_acpi.c: Full TOS1900 device support
Date: Wed, 27 Oct 2010 20:29:13 +0100 [thread overview]
Message-ID: <20101027192913.GA14828@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTinmsNzAkp_ZGcaNyVRVMu0Rc4-C+xPKuSOS5jRJ@mail.gmail.com>
On Wed, Oct 27, 2010 at 01:24:15PM -0600, Azael Avalos wrote:
> Yes, actually the ACPI video driver does a better job of detecting the
> video device,
> so perhaps something like the following would be better IMHO for at least the
> backlight:
Yeah, that looks better.
> Is there an ACPI function that let's us query the display brightness?
> Because TOS1900 devices lack the HCI method to query the LCD status,
> and thus the proc interface will be useless, that is, if a userland (or any
> other) application is using it.
Ignore the proc interface. Everyone should be using sysfs now. _BQC is
the standardised ACPI function for this, but it's not always
implemented.
> > Ugh. Use i8042_install_filter instead, and just look at the raw i8042
> > stream. That'll avoid the ugly strncmp for the device names in order to
> > find the right device.
> >
>
> Can you point me to some documents (if any) or even pieces of code
> that I can look at.
>
> I've tried using the i8042_install_filter function, but I haven't had
> any luck so far,
> or perhaps I'm using it in wrong, due to my limited kernel knowledge.
Take a look at the dell-laptop driver in drivers/platform/x86.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-10-27 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 19:14 toshiba_acpi.c: Full TOS1900 device support Azael Avalos
2010-10-26 19:20 ` Matthew Garrett
2010-10-27 19:24 ` Azael Avalos
2010-10-27 19:29 ` Matthew Garrett [this message]
2010-11-12 0:10 ` Azael Avalos
2010-11-24 19:17 ` Matthew Garrett
2010-11-28 0:44 ` Azael Avalos
2010-12-06 17:41 ` Azael Avalos
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=20101027192913.GA14828@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=coproscefalo@gmail.com \
--cc=linux-kernel@vger.kernel.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.