- 21 Oct, 2010 39 commits
-
-
Vernon Mauery authored
After a period of RFC for this driver, I think it is ready for inclusion in the platform-driver-x86 tree, hopefully to be staged in the next merge window into Linus's tree. --Vernon ------------------------------------------------------------ IBM Real-Time "SMI Free" mode driver This driver supports the Real-Time Linux (RTL) BIOS feature. The RTL feature allows non-fatal System Management Interrupts (SMIs) to be disabled on supported IBM platforms and is intended to be coupled with a user-space daemon to monitor the hardware in a way that can be prioritized and scheduled to better suit the requirements for the system. The Device is presented as a special "_RTL_" table to the OS in the Extended BIOS Data Area. There is a simple protocol for entering and exiting the mode at runtime. This driver creates a simple sysfs interface to allow a simple entry and exit from RTL mode in the UFI/BIOS. Since the driver is specific to IBM SystemX hardware (x86- based servers) it only builds on x86 builds. To reduce the risk of loading on the wrong hardware, the module uses DMI information and checks a list of servers that are known to work. Signed-off-by:
Vernon Mauery <vernux@us.ibm.com> Signed-off-by:
Matthew Garrett <mjg@redhat.com>
-
Daniel Drake authored
Add a software rfkill switch for the WLAN interface in the OLPC XO-1 laptop. It uses the OLPC embedded controller to cut/restore power to the Marvell WLAN chip on the motherboard. Signed-off-by:
Daniel Drake <dsd@laptop.org> Signed-off-by:
-
Jean Delvare authored
The hdaps driver isn't a hardware monitoring driver, so it shouldn't live under driver/hwmon. drivers/platform/x86 seems much more appropriate, as the driver is only useful on x86 laptops. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Cc: Guenter Roeck <guenter.roeck@ericsson.com> Cc: Matthew Garrett <mjg@redhat.com> Cc: Frank Seidel <frank@f-seidel.de> Signed-off-by:
-
Matthew Garrett authored
The makefile didn't get updated when the driver changed name, which broke the build. Signed-off-by: -
Alek Du authored
The intel_scu_ipc_update_register 2nd paramter should the bits and 3rd paramter should be the mask. This typo was introduced during IPC function changing... Reported-by:
Ryan Zhou <ryan.zhou@intel.com> Signed-off-by:
Alek Du <alek.du@intel.com> Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
-
Ike Panhc authored
Add new module parameter that force module not to register bluetooth rfkill. There is report that saying using this bluetooth rfkill to enable/disable bluetooth will let bluetooth device initial failed when enable on Lenovo ideapad S12. Fortunately there is another rfkill registered by bluetooth driver for S12 and user can shutdown the bluetooth by either bluetooth driver or HW RF switch. For dual OS user, it may have some trouble that using Linux after turning off bluetooth with another OS if we do not register bluetooth rfkill at all. So we will force bluetooth enable when no_bt_rfkill=1. Signed-off-by:
Ike Panhc <ike.pan@canonical.com> Tested-by:
Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE> Signed-off-by:
-
Ike Panhc authored
Since the platform drivers doing more for laptops than just using specific ACPI device. It will be good to change the name from *_acpi to *-laptop. Reference: http://lkml.org/lkml/2010/8/14/154Signed-off-by:
Len Brown <len.brown@intel.com> Signed-off-by:
-
Ike Panhc authored
Control power of rf modules by ec commands Signed-off-by:
-
Ike Panhc authored
1. Read hw rfkill status by ec command 2. Not to touch sw status of each rfkill when hw rfkill notify 3. Initial rfkill status when module loaded Signed-off-by:
-
Ike Panhc authored
Signed-off-by:
-
Ike Panhc authored
There are several bits of the return value of _CFG shows if RF/Camera devices exist or not. Signed-off-by:
-
Ike Panhc authored
By reading from method _CFG to make sure we bind on the correct VPC2004 device. Signed-off-by:
-
Ike Panhc authored
Check VPC bit to make sure the HW rfkill is touched. Signed-off-by:
-
Ike Panhc authored
There are two methods under VPC2004 which is used to access VDAT/VCMD of EC register. Add helpers for read and write these two registers. And add read_method_int for reading the return value from ACPI methods which requires no parameter. Signed-off-by:
-
Keng-Yu Lin authored
Export the status of RF killswitch through debugfs. The killswitch status is obtained by the SMI to BIOS. Exporting this status through debugfs can help identify the issue with the misbehaving firmware. Signed-off-by:
Keng-Yu Lin <keng-yu.lin@canonical.com> Signed-off-by:
-
Dmitry Torokhov authored
Instead of creating wmi_blocks and then register corresponding devices on a separate pass do it all in one shot, since lifetime rules for both objects are the same. This also takes care of leaking devices when device_create fails for one of them. Signed-off-by:
Dmitry Torokhov <dtor@mail.ru> Signed-off-by:
-
Dmitry Torokhov authored
Instead of adding modalias attribute manually set it up as class's device attribute so driver core will create and remove it for us. Signed-off-by:
-
Dmitry Torokhov authored
This makes source more concise and easier to read. Signed-off-by:
-
Dmitry Torokhov authored
Do not abuse wmi_block structure to hold the head of list of blocks, use separate list_head for that. Signed-off-by:
-
Dmitry Torokhov authored
There is no reason why we allocate memory and copy data into an intermediate buffer, it is not like we are working with data coming from userspace. Signed-off-by:
-
Dmitry Torokhov authored
Signed-off-by:
-
Dmitry Torokhov authored
If we _WDG returned object that is not buffer we were forgetting to free memory allocated for that object. Signed-off-by:
-
Dmitry Torokhov authored
Courtesy of sparse... Signed-off-by:
-
Dmitry Torokhov authored
Signed-off-by:
-
Dmitry Torokhov authored
Driver initialization was forgetting to remove EC address space handler in cases when parse_wdg() method failed. Signed-off-by:
-
Dmitry Torokhov authored
Instead of registering (and removing) every attribute individually switch to using sysfs attribute group. This makes sure that we properly unwind and do not try to remove non-existent attributes which may not be safe to do in the future. Signed-off-by:
-
Alan Cox authored
We need to include the SFI headers. This is fine as the SCU is only relevant to x86 platforms with SFI. Fixes the -next warning report. Signed-off-by:
-
Andy Shevchenko authored
In 2.6.35 the hex_to_bin() was introduced. Signed-off-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Cc: Carlos Corbacho <carlos@strangeworlds.co.uk> Cc: Matthew Garrett <mjg@redhat.com> Cc: platform-driver-x86@vger.kernel.org Signed-off-by:
-
Randy Dunlap authored
Fix kconfig recursive dependency error in ACPI_TOSHIBA: it uses both select and depends on for BACKLIGHT_CLASS_DEVICE. drivers/video/backlight/Kconfig:117:error: recursive dependency detected! drivers/video/backlight/Kconfig:117: symbol BACKLIGHT_CLASS_DEVICE is selected by ACPI_TOSHIBA drivers/platform/x86/Kconfig:490: symbol ACPI_TOSHIBA depends on LEDS_CLASS drivers/leds/Kconfig:12: symbol LEDS_CLASS is selected by BACKLIGHT_ADP8860 drivers/video/backlight/Kconfig:285: symbol BACKLIGHT_ADP8860 depends on BACKLIGHT_CLASS_DEVICE Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
-
Pascal de Bruijn authored
Signed-off-by: -
Dmitry Torokhov authored
The driver uses sparse keymap library and does not use this field anymore. Signed-off-by:
-
Corentin Chary authored
The GPS rfkill crappy code. The ops_data argument wasn't set, and was totally misused. The fix have been tested on an Asus R2H. Cc: stable@kernel.org Signed-off-by:
Corentin Chary <corentincj@iksaif.net> Signed-off-by:
-
Corentin Chary authored
Signed-off-by:
-
Corentin Chary authored
Makes asus-laptop and eeepc-laptop _init/_exit functions looks exactly the same as they do the same thing. Signed-off-by:
-
Dmitry Torokhov authored
Instead of implementing its own version of keymap hanlding switch over to using sparse keymap library. Also, install notify handler only after we allocated input device, otherwise we may risk getting event too early and crash. Similarly, notify handler should be removed before we unregister input device. Signed-off-by:
-
Dmitry Torokhov authored
Instead of implementing its own version of keymap hanlding switch over to using sparse keymap library. Also make sure that we install notify handler only after we allocated input device and that we remove notify handler before unregistering input device. Signed-off-by:
-
Dmitry Torokhov authored
Instead of implementing its own version of keymap hanlding switch over to using sparse keymap library. Signed-off-by:
-
Dmitry Torokhov authored
nstead of implementing its own version of keymap hanlding switch over to using sparse keymap library. Cc: Harald Welte <laforge@gnumonks.org> Signed-off-by:
-
Dmitry Torokhov authored
Instead of implementing its own version of keymap hanlding switch over to using sparse keymap library. Acked-by:
Herton Ronaldo Krzesinski <herton@mandriva.com.br> Signed-off-by:
-
- 20 Oct, 2010 1 commit
-
-
Linus Torvalds authored
-
