From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com,
don@syst.com.br, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] cmpc_acpi: Added support for Classmate PC ACPI devices.
Date: Wed, 30 Sep 2009 15:57:07 -0300 [thread overview]
Message-ID: <20090930185707.GI17475@vespa.holoscopio.com> (raw)
In-Reply-To: <200909301227.49916.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]
On Wed, Sep 30, 2009 at 12:27:48PM -0600, Bjorn Helgaas wrote:
> On Wednesday 30 September 2009 11:51:43 am Thadeu Lima de Souza Cascardo wrote:
> > On Wed, Sep 30, 2009 at 09:50:38AM -0600, Bjorn Helgaas wrote:
> > > On Monday 28 September 2009 07:38:00 pm Thadeu Lima de Souza Cascardo wrote:
> > > > This add supports for devices like keyboard, backlight, tablet and
> > > > accelerometer.
> > >
> > > Something about the PNP IDs bothered me yesterday, but I couldn't
> > > figure out what. You're using:
> > >
> > > ACCE0000
> > > TBLT0000
> > > IPML200
> > > FnBT0000
> > >
> > > Normally these OEM-specific ACPI drivers claim PNP IDs like ATK0100,
> > > TOS6200, FUJ02B1, etc., that are obviously OEM-specific.
> > >
> > > But the ones you're claiming seem pretty generic, like things
> > > we could imagine appearing on machines other than the Classmate.
> > >
> > > So I guess my question is, "Are these really generic? If so, should
> > > this be split into separate, non-Classmate named drivers, such as
> > > 'accelerometer', 'tablet', etc.?"
> > >
> >
> > Although I agree that {ATK,TOS,FUJ,IBM}* give pretty much a certainty
> > these are OEM-specific, I think we'd need some evidence that
> > {ACCE,TBLT,IPML,FnBT}* are generic enough to grant them a non-classmate
> > driver.
> >
> > What I mean is that we should push this driver forward and turn these
> > into a generic driver if we get some evidence these are not
> > Classmate-specific. And that will happen when we hit some other system
> > with these devices.
>
> Yep, I agree with you that it's not worth splitting things up until
> we find these devices on more systems. Just out of curiosity, where
> did you find specs for these devices? If there's a public spec, it'd
> be nice to have a pointer to it in the driver.
>
> Bjorn
There was no public spec. I used as reference some source code released
as GPL. This implementation used proc files as user interface. Other
references are the dumped tables, which I am using to implement what is
very likely a rfkill device. We are still doing some tests before adding
it to the driver.
Regards,
Cascardo.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-09-30 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 1:38 [PATCH] cmpc_acpi: Added support for Classmate PC ACPI devices Thadeu Lima de Souza Cascardo
2009-09-29 9:20 ` Alan Jenkins
2009-09-29 14:16 ` Thadeu Lima de Souza Cascardo
2009-09-29 16:41 ` Alan Jenkins
2009-10-01 16:38 ` Dmitry Torokhov
2009-09-29 16:12 ` Bjorn Helgaas
2009-09-29 20:05 ` Andrew Morton
2009-09-29 20:10 ` Thadeu Lima de Souza Cascardo
2009-09-29 20:17 ` Joe Perches
2009-09-30 15:50 ` Bjorn Helgaas
2009-09-30 17:51 ` Thadeu Lima de Souza Cascardo
2009-09-30 18:27 ` Bjorn Helgaas
2009-09-30 18:57 ` Thadeu Lima de Souza Cascardo [this message]
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=20090930185707.GI17475@vespa.holoscopio.com \
--to=cascardo@holoscopio.com \
--cc=bjorn.helgaas@hp.com \
--cc=don@syst.com.br \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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