From: Yin Kangkai <kangkai.yin@linux.intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86 <platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org, "Wang,
Yong Y" <yong.y.wang@intel.com>,
"Liu, Bing Wei" <bing.wei.liu@intel.com>,
Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [PATCH V2] platform-driver-x86: ACPI EC Extra driver for Oaktrail
Date: Mon, 10 Jan 2011 15:10:13 +0800 [thread overview]
Message-ID: <20110110071013.GJ30215@kai-debian> (raw)
In-Reply-To: <20110107220940.GA32575@srcf.ucam.org>
On 2011-01-07, 22:09 +0000, Matthew Garrett wrote:
> On Fri, Jan 07, 2011 at 03:41:15PM +0800, Yin Kangkai wrote:
>
> > This driver implements an Extra ACPI EC driver for products based on Intel
> > Oaktrail platform. It is programming the EC space, through existing ACPI EC
> > driver, to provide user space layer the sysfs and rfkill interfaces to
> > enable/disable the Camera, Bluetooth, GPS, WiFi, 3G, and to show the status of
> > Touchscreen.
>
> As far as I can tell, the only ACPI aspect of this driver is that it
> makes use of the ACPI EC driver? In that case I think the name's
> misleading.
OK, am rename the driver "EC Extra driver...",
> > @@ -0,0 +1,13 @@
> > +What: /sys/devices/platform/intel_oaktrail/camera
> > +Date: Jan 2011
> > +KernelVersion: 2.6.37
> > +Contact: "Yin Kangkai" <kangkai.yin@intel.com>
> > +Description:
> > + Control the camera. 1 means on, 0 means off.
>
> We really need a better approach for this kind of thing...
>
> > +What: /sys/devices/platform/intel_oaktrail/touchscreen
> > +Date: Jan 2011
> > +KernelVersion: 2.6.37
> > +Contact: "Yin Kangkai" <kangkai.yin@intel.com>
> > +Description:
> > + Show the status of the touch screen. 1 means on, 0 means off.
>
> And this one, but we don't have one yet so I think this is ok.
>
> > + wwan_rfkill = oaktrail_rfkill_new("oaktrail-wwan",
> > + RFKILL_TYPE_WWAN,
> > + OT_EC_WWAN_MASK);
>
> Do you have any way to identify whether the hardware has all these
> features before registering?
AFAIK, no, sorry.
> > +static struct dmi_system_id __initdata oaktrail_dmi_table[] = {
> > + {
> > + .ident = "OakTrail platform",
> > + .matches = {
> > + DMI_MATCH(DMI_PRODUCT_NAME, "OakTrail platform"),
> > + },
> > + .callback = dmi_check_cb
> > + },
> > + { }
> > +};
>
> Is any hardware actually going to ship with this identifier, or will
> vendors change the string?
I think vendors and OEMs will change this string. But we can add the
DMI_BOARD_NAME, DMI_BOARD_VERSION, etc. back later, can we?
Thanks.
next prev parent reply other threads:[~2011-01-10 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 2:59 [PATCH] platform-driver-x86: ACPI EC Extra driver for Oaktrail Yin Kangkai
2011-01-06 7:29 ` Corentin Chary
2011-01-06 10:11 ` Yin Kangkai
2011-01-06 10:21 ` Corentin Chary
2011-01-06 10:50 ` Yin Kangkai
2011-01-06 10:54 ` Corentin Chary
2011-01-06 11:32 ` Joey Lee
2011-01-06 11:35 ` Joey Lee
2011-01-07 0:01 ` Yin Kangkai
2011-01-07 7:41 ` [PATCH V2] " Yin Kangkai
2011-01-07 8:56 ` Corentin Chary
2011-01-07 11:24 ` Yin Kangkai
2011-01-10 6:57 ` Yin Kangkai
2011-01-07 22:09 ` Matthew Garrett
2011-01-10 7:10 ` Yin Kangkai [this message]
2011-01-10 9:16 ` Thomas Renninger
2011-01-10 7:15 ` [PATCH V3] platform-driver-x86: " Yin Kangkai
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=20110110071013.GJ30215@kai-debian \
--to=kangkai.yin@linux.intel.com \
--cc=bing.wei.liu@intel.com \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yong.y.wang@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