Re: [PATCH 58/62] msi-laptop: Support some MSI 3G netbook that is need load SCM
From: Joey Lee
Date: Tue Mar 02 2010 - 23:52:21 EST
First, thank's for your kindly review and suggestion to me.
æ äï2010-03-02 æ 15:46 -0800ïGreg KH æåï
> On Tue, Mar 02, 2010 at 11:39:29PM +0000, Matthew Garrett wrote:
> > On Tue, Mar 02, 2010 at 03:28:57PM -0800, Greg Kroah-Hartman wrote:
> > > From: Lee, Chun-Yi <jlee@xxxxxxxxxx>
> > >
> > > Some MSI 3G netbook only have one fn key to control Wlan/Bluetooth/3G,
> > > those netbook will load the SCM (windows app) to disable the original
> > > Wlan/Bluetooth control by BIOS when user press fn key, then control
> > > Wlan/Bluetooth/3G by SCM (software control by OS). Without SCM, user
> > > cann't on/off 3G module on those 3G netbook.
> > > On Linux, msi-laptop driver will do the same thing to disable the
> > > original BIOS control, then might need use HAL or other userland
> > > application to do the software control that simulate with SCM.
> > > e.g. MSI N034 netbook
> > How does the function key event get reported to userland? This should
> > generate KEY_RFKILL and then just go through rfkill-input.
I developed this driver on 2.6.31 kernel, and I found this key code is
in 2.6.33 kernel and later.
There have one and only one scancode to control 3 devices when end user
press fn+f11 key on MSI N034.
Currently, we setup this mapping in HAL key and mapping it to KEY_WLAN.
Does that means I need mapping the scancode to KEY_RFKILL in msi-laptop
driver for 2.6.33 kernel?
If YES, I will submit another patch to add this scancode/keycode mapping
> I'm pretty sure that Joey is using rfkill here, but I didn't realize
> that it also supported an input device.
> This code is just detecting the keypress, and acting on it, I think,
> right Joey? Isn't that the way this is supposed to work? Or is it
> supposed to use rfkill-input, which then userspace turns around and
> calls the other rfkill interface to then disable the wireless? If so, I
> think a number of laptop drivers need to be changed to do this.
There have a serial MSI netbook (like: N034) use only one scancode (one
function key) to control 3 devices (Wlan/Bluetooth/3G). It have a
sequence to control those device and userland application control this
sequence, almost like:
- Bluetooth on, WLAN on, WWAN on
- Bluetooth on, WLAN off, WWAN off
- Bluetooth off, WLAN off, WWAN on
- Bluetooth off, WLAN off, WWAN off
Even on Windows platform, this job is also handle by userland
application, not by hardware or driver. And MSI EC provide a address to
turn on/off those devices' power and led light.
This patchset for msi-laptop driver is just to provide Wlan/Bluetooth/3G
rfkill sysfs interface for userland to turn on/off those devices's power
And this patchset doesn't do:
- setup the wifi function key scancode/keycode mapping.
- control those 3 devices on/off sequence. (userland control it)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/