22 Feb, 2011
1 commit
-
Most platform/x86 drivers that use INPUT_SPARSEKMAP also depend on INPUT,
so do the same for ideapad-laptop. This fixes a kconfig warning and
subsequent build errors when CONFIG_INPUT is disabled.warning: (ACER_WMI && ASUS_LAPTOP && DELL_WMI && HP_WMI && PANASONIC_LAPTOP && IDEAPAD_LAPTOP && EEEPC_LAPTOP && EEEPC_WMI && MSI_WMI && TOPSTAR_LAPTOP && ACPI_TOSHIBA) selects INPUT_SPARSEKMAP which has unmet direct dependencies (!S390 && INPUT)
ERROR: "input_free_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "input_register_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "sparse_keymap_setup" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "input_allocate_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "input_unregister_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "sparse_keymap_free" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "sparse_keymap_report_event" [drivers/platform/x86/ideapad-laptop.ko] undefined!Signed-off-by: Randy Dunlap
Cc: David Woodhouse
Cc: Matthew Garrett
Cc: platform-driver-x86@vger.kernel.org
Signed-off-by: Matthew Garrett
11 Jan, 2011
1 commit
-
Currently the x86 platform devices are not consistent about selecting
or depending on the LEDs Kconfig variables, and this inconsistency
leads to Kconfig getting upset and refusing to offer LEDs (even on
non-x86 platforms):drivers/platform/x86/Kconfig:422:error: recursive dependency detected!
drivers/platform/x86/Kconfig:422: symbol EEEPC_WMI depends on ACPI_WMI
drivers/platform/x86/Kconfig:438: symbol ACPI_WMI is selected by ACER_WMI
drivers/platform/x86/Kconfig:18: symbol ACER_WMI depends on LEDS_CLASS
drivers/leds/Kconfig:10: symbol LEDS_CLASS is selected by EEEPC_WMIFix this by always selecting rather than depending on the symbols as
slightly more drivers use this approach already and it seems more
user friendly.Signed-off-by: Mark Brown
Signed-off-by: Matthew Garrett
08 Jan, 2011
6 commits
-
Add acer wmi hotkey event support. Install a wmi notify handler to
transfer wmi event key to key code, then send out keycode through acer
wmi input device to userland.Signed-off-by: Lee, Chun-Yi
Acked-by: Dmitry Torokhov
Acked-by: Thomas Renninger
Acked-by: Jiri Benc
Signed-off-by: Carlos Corbacho
Cc: Corentin Chary
Signed-off-by: Matthew Garrett -
With 'make oldnoconfig' I see these warnings in linux-next (next-20101208):
drivers/platform/x86/Kconfig:422:error: recursive dependency detected!
drivers/platform/x86/Kconfig:422: symbol EEEPC_WMI depends on ACPI_WMI
drivers/platform/x86/Kconfig:438: symbol ACPI_WMI is selected by ACER_WMI
drivers/platform/x86/Kconfig:18: symbol ACER_WMI depends on LEDS_CLASS
drivers/leds/Kconfig:10: symbol LEDS_CLASS is selected by EEEPC_WMIThis patch replaces all "select on ACPI_WMI" by "depends on ACPI_WMI".
Quote from David Woodhouse:
"A better policy is: "NEVER USE SELECT"."Reported-and-tested-by: Sedat Dilek
Signed-off-by: Sedat Dilek
Acked-by: Randy Dunlap
Signed-off-by: Matthew Garrett -
Hotkey enabled by this patch:
Fn+F3: Video mode switch
Fn+F5: software rfkill for wifiFor some ideapad when push Fn+F3, hardware generates Super-P keys, those key
will not be enabled by this patch.Thanks for Dave Hansen report the problem. If CONFIG_INPUT_SPARSEKMAP is not
set, when building, you will have error message:ERROR: "sparse_keymap_setup" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "sparse_keymap_free" [drivers/platform/x86/ideapad-laptop.ko] undefined!
ERROR: "sparse_keymap_report_event" [drivers/platform/x86/ideapad-laptop.ko] undefined!To select INPUT_SPARSEKMAP solve this issue.
Ref: http://lkml.org/lkml/2010/12/2/340
Signed-off-by: Ike Panhc
Signed-off-by: Matthew Garrett -
wimax support is missing because I don't have any DSDT
with WMI and wimax support.Most of the code comes from eeepc-laptop.
Signed-off-by: Corentin Chary
Signed-off-by: Matthew Garrett -
Most of the code comes from eeepc-laptop.
Signed-off-by: Corentin Chary
Signed-off-by: Matthew Garrett -
This driver implements ioctl and interfaces with intel scu ipc driver. It
is used to access pmic/msic registers from user space and firmware update
utility.Signed-off-by: Sreedhara DS
[Extensive clean up and debug]
Signed-off-by: Alan Cox
Signed-off-by: Matthew Garrett
21 Oct, 2010
10 commits
-
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
Signed-off-by: Matthew Garrett -
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
Signed-off-by: Matthew Garrett -
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
Cc: Guenter Roeck
Cc: Matthew Garrett
Cc: Frank Seidel
Signed-off-by: Matthew Garrett -
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/154
Signed-off-by: Ike Panhc
Acked-by: Len Brown
Signed-off-by: Matthew Garrett -
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_DEVICESigned-off-by: Randy Dunlap
Signed-off-by: Matthew Garrett -
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
Signed-off-by: Matthew Garrett -
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
Signed-off-by: Matthew Garrett -
Instead of implementing its own version of keymap hanlding switch over to
using sparse keymap library.Signed-off-by: Dmitry Torokhov
Signed-off-by: Matthew Garrett -
nstead of implementing its own version of keymap hanlding switch over to
using sparse keymap library.Cc: Harald Welte
Signed-off-by: Dmitry Torokhov
Signed-off-by: Matthew Garrett -
Instead of implementing its own version of keymap hanlding switch over to
using sparse keymap library.Acked-by: Herton Ronaldo Krzesinski
Signed-off-by: Dmitry Torokhov
Signed-off-by: Matthew Garrett
24 Aug, 2010
1 commit
-
Don't ask how ACPI_TOSHIBA got enabled on in desktop system's .config -
I don't know. But it has silently been there until I tried 2.6.36-rc2,
where it broke the build because I don't have LED support turned on.
Attached patch fixes things up.(I had to change BACKLIGHT_CLASS_DEVICE to "depends" because otherwise
I get unsightly core dumps out of scripts/kconfig/conf).jon
--
toshiba: make sure we pull in LED supportThe Toshiba extras driver uses the LED module, so make sure we have it
configure in.Signed-off-by: Jonathan Corbet
Signed-off-by: Matthew Garrett
11 Aug, 2010
1 commit
-
Signed-off-by: David Woodhouse
03 Aug, 2010
8 commits
-
My .config contains ACER_WMI=m. On SPARC. That does not make sense.
Restrict the x86 platform driver menu to x86.Signed-off-by: Jan Engelhardt
Signed-off-by: Matthew Garrett -
compal-laptop uses power_supply interfaces so it should depend
on POWER_SUPPLY.ERROR: "power_supply_register" [drivers/platform/x86/compal-laptop.ko] undefined!
ERROR: "power_supply_unregister" [drivers/platform/x86/compal-laptop.ko] undefined!Signed-off-by: Randy Dunlap
Cc: Cezary Jackiewicz
Cc: Matthew Garrett
Cc: platform-driver-x86@vger.kernel.org
Signed-off-by: Matthew Garrett -
Moorestown has PMIC chip which contains GPIO blocks. The PMIC chip is
connected to Langwell by SPI interface. So this GPIO driver will be regarded
as SPI GPIO expander though the actual GPIO access is through IPC and SRAM.
The SPI master contoller will probe this device driver by parsing SPIB table.Cleaned up for new IPC, GPE removed and some printk and other tidying by
Alan Cox. Fixes for points noted by Matthew GarrettSigned-off-by: Alek Du
Signed-off-by: Alan Cox
Signed-off-by: Matthew Garrett -
compal-laptop uses hwmon interfaces, so it should depend on HWMON.
compal-laptop.c:(.devinit.text+0x4071f): undefined reference to `hwmon_device_register'
compal-laptop.c:(.devexit.text+0x6ec0): undefined reference to `hwmon_device_unregister'Signed-off-by: Randy Dunlap
Cc: Roald Frederickx
Cc: Matthew Garrett
Signed-off-by: Andrew Morton
Signed-off-by: Matthew Garrett -
We exit staging rar! rar! rar!...
Signed-off-by: Alan Cox
Signed-off-by: Matthew Garrett
Acked-by: Greg Kroah-Hartman -
Intel Core i3/5 platforms with integrated graphics support both CPU and
GPU turbo mode. CPU turbo mode is opportunistic: the CPU will use any
available power to increase core frequencies if thermal headroom is
available. The GPU side is more manual however; the graphics driver
must monitor GPU power and temperature and coordinate with a core
thermal driver to take advantage of available thermal and power headroom
in the package.The intelligent power sharing (IPS) driver is intended to coordinate
this activity by monitoring MCP (multi-chip package) temperature and
power, allowing the CPU and/or GPU to increase their power consumption,
and thus performance, when possible. The goal is to maximize
performance within a given platform's TDP (thermal design point).Signed-off-by: Jesse Barnes
Signed-off-by: Matthew Garrett -
msi-laptop uses i8042_*() interfaces, so it should depend on
SERIO_I8042. E.g., when SERIO_I8042=m and MSI_LAPTOP=y:msi-laptop.c:(.text+0x18a7fe): undefined reference to `i8042_install_filter'
msi-laptop.c:(.init.text+0xd69d): undefined reference to `i8042_remove_filter'
msi-laptop.c:(.exit.text+0x19c3): undefined reference to `i8042_remove_filter'Signed-off-by: Randy Dunlap
Signed-off-by: Matthew Garrett
Cc: Lennart Poettering -
Randy Dunlap has reported that building classmate-laptop fails when
CONFIG_RFKILL=m and CONFIG_ACPI_CMPC=y. He suggested depending on
RFKILL, but, then, it will not be possible to select classmate-laptop
when RFKILL is off. There's no known problem with building and using
classmate-laptop with RFKILL off. So depend on RFKILL or RFKILL=n.Signed-off-by: Thadeu Lima de Souza Cascardo
Signed-off-by: Matthew Garrett
Reported-by: Randy Dunlap
Cc: Randy Dunlap
Cc: platform-driver-x86@vger.kernel.org
Cc: Daniel Oliveira Nascimento
18 May, 2010
3 commits
-
Make it clear that this driver is only needed for embedded hardware,
not PCs.Signed-off-by: Matthew Garrett
-
eeepc-wmi uses backlight*() interfaces so it should depend on
BACKLIGHT_CLASS_DEVICE.eeepc-wmi.c:(.text+0x2d7f54): undefined reference to `backlight_force_update'
eeepc-wmi.c:(.text+0x2d8012): undefined reference to `backlight_device_register'
eeepc-wmi.c:(.devinit.text+0x1c31c): undefined reference to `backlight_device_unregister'
eeepc-wmi.c:(.devexit.text+0x2f8b): undefined reference to `backlight_device_unregister'Signed-off-by: Randy Dunlap
Cc: stable@kernel.org -
The IPC (inter processor communications) is used to provide the
communications between kernel and system control units on some embedded
Intel x86 platforms.(Various bits of clean up and restructuring by Alan Cox)
Signed-off-by: Sreedhara DS
Signed-off-by: Alan Cox
13 Apr, 2010
1 commit
-
-tip testing found:
eeepc-wmi.c:(.text+0x36673c): undefined reference to `sparse_keymap_report_event'
drivers/built-in.o: In function `eeepc_wmi_init':
eeepc-wmi.c:(.init.text+0x19cd0): undefined reference to `sparse_keymap_setup'
eeepc-wmi.c:(.init.text+0x19cf0): undefined reference to `sparse_keymap_free'
eeepc-wmi.c:(.init.text+0x19d0b): undefined reference to `sparse_keymap_free'
drivers/built-in.o: In function `eeepc_wmi_exit':
eeepc-wmi.c:(.exit.text+0x2e87): undefined reference to `sparse_keymap_free'To fix this select INPUT_SPARSEKMAP, like the ASUS driver does.
Signed-off-by: Ingo Molnar
Signed-off-by: Matthew Garrett
01 Apr, 2010
1 commit
-
Add a WMI driver for Eee PC laptops. Currently it only supports hotkeys.
Signed-off-by: Yong Wang
Signed-off-by: Matthew Garrett
Acked-by: Dmitry Torokhov
08 Mar, 2010
1 commit
-
msi-laptop uses rfkill*() interfaces so it should depend on RFKILL.
msi-laptop.c:(.text+0x1fcd1b): undefined reference to `rfkill_alloc'
msi-laptop.c:(.text+0x1fcd76): undefined reference to `rfkill_register'
msi-laptop.c:(.text+0x1fcdc8): undefined reference to `rfkill_destroy'
msi-laptop.c:(.text+0x1fcdd9): undefined reference to `rfkill_unregister'This repairs "msi-laptop: Detect 3G device exists by standard ec command",
which is in some gregkh tree.Signed-off-by: Randy Dunlap
Cc: Lennart Poettering
Cc: Lee, Chun-Yi
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman
02 Mar, 2010
2 commits
-
-tip testing found this build failure (x86 randconfig):
drivers/built-in.o: In function `setup_rfkill':
compal-laptop.c:(.text+0x36abe8): undefined reference to `rfkill_alloc'
compal-laptop.c:(.text+0x36abfc): undefined reference to `rfkill_register'
compal-laptop.c:(.text+0x36ac30): undefined reference to `rfkill_alloc'
compal-laptop.c:(.text+0x36ac44): undefined reference to `rfkill_register'Which can happen with CONFIG_COMPAL_LAPTOP=y but COMPAL_LAPTOP=m.
Signed-off-by: Ingo Molnar
-
…nux-acpi-2.6/ibm-acpi-2.6 into x86-platform
01 Mar, 2010
3 commits
-
The rfkill subsystem will enable gps by default.
Signed-off-by: Corentin Chary
-
This patch is based on Dmitry Torokhov's patch with
some modifications and cleanups.Signed-off-by: Corentin Chary
26 Feb, 2010
1 commit
-
Given the right combination of ThinkPad and X.org, just reading the
video output control state is enough to hard-crash X.org.Until the day I somehow find out a model or BIOS cut date to not
provide this feature to ThinkPads that can do video switching through
X RandR, change permissions so that only processes with CAP_SYS_ADMIN
can access any sort of video output control state.This bug could be considered a local DoS I suppose, as it allows any
non-privledged local user to cause some versions of X.org to
hard-crash some ThinkPads.Reported-by: Jidanni
Signed-off-by: Henrique de Moraes Holschuh
Cc: stable@kernel.org
