![Bryan O'Donoghue](/assets/img/avatar_default.png)
Intel's Quark X1000 SoC contains a set of registers called Isolated Memory Regions. IMRs are accessed over the IOSF mailbox interface. IMRs are areas carved out of memory that define read/write access rights to the various system agents within the Quark system. For a given agent in the system it is possible to specify if that agent may read or write an area of memory defined by an IMR with a granularity of 1 KiB. Quark_SecureBootPRM_330234_001.pdf section 4.5 details the concept of IMRs quark-x1000-datasheet.pdf section 12.7.4 details the implementation of IMRs in silicon. eSRAM flush, CPU Snoop write-only, CPU SMM Mode, CPU non-SMM mode, RMU and PCIe Virtual Channels (VC0 and VC1) can have individual read/write access masks applied to them for a given memory region in Quark X1000. This enables IMRs to treat each memory transaction type listed above on an individual basis and to filter appropriately based on the IMR access mask for the memory region. Quark supports eight IMRs. Since all of the DMA capable SoC components in the X1000 are mapped to VC0 it is possible to define sections of memory as invalid for DMA write operations originating from Ethernet, USB, SD and any other DMA capable south-cluster component on VC0. Similarly it is possible to mark kernel memory as non-SMM mode read/write only or to mark BIOS runtime memory as SMM mode accessible only depending on the particular memory footprint on a given system. On an IMR violation Quark SoC X1000 systems are configured to reset the system, so ensuring that the IMR memory map is consistent with the EFI provided memory map is critical to ensure no IMR violations reset the system. The API for accessing IMRs is based on MTRR code but doesn't provide a /proc or /sys interface to manipulate IMRs. Defining the size and extent of IMRs is exclusively the domain of in-kernel code. Quark firmware sets up a series of locked IMRs around pieces of memory that firmware owns such as ACPI runtime data. During boot a series of unlocked IMRs are placed around items in memory to guarantee no DMA modification of those items can take place. Grub also places an unlocked IMR around the kernel boot params data structure and compressed kernel image. It is necessary for the kernel to tear down all unlocked IMRs in order to ensure that the kernel's view of memory passed via the EFI memory map is consistent with the IMR memory map. Without tearing down all unlocked IMRs on boot transitory IMRs such as those used to protect the compressed kernel image will cause IMR violations and system reboots. The IMR init code tears down all unlocked IMRs and sets a protective IMR around the kernel .text and .rodata as one contiguous block. This sanitizes the IMR memory map with respect to the EFI memory map and protects the read-only portions of the kernel from unwarranted DMA access. Tested-by: Ong, Boon Leong <boon.leong.ong@intel.com> Signed-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie> Reviewed-by: Andy Shevchenko <andy.schevchenko@gmail.com> Reviewed-by: Darren Hart <dvhart@linux.intel.com> Reviewed-by: Ong, Boon Leong <boon.leong.ong@intel.com> Cc: andy.shevchenko@gmail.com Cc: dvhart@infradead.org Link: http://lkml.kernel.org/r/1422635379-12476-2-git-send-email-pure.logic@nexus-software.ie Signed-off-by: Ingo Molnar <mingo@kernel.org>
888 lines
28 KiB
Plaintext
888 lines
28 KiB
Plaintext
#
|
|
# X86 Platform Specific Drivers
|
|
#
|
|
|
|
menuconfig X86_PLATFORM_DEVICES
|
|
bool "X86 Platform Specific Device Drivers"
|
|
default y
|
|
depends on X86
|
|
---help---
|
|
Say Y here to get to see options for device drivers for various
|
|
x86 platforms, including vendor-specific laptop extension drivers.
|
|
This option alone does not add any kernel code.
|
|
|
|
If you say N, all options in this submenu will be skipped and disabled.
|
|
|
|
if X86_PLATFORM_DEVICES
|
|
|
|
config ACER_WMI
|
|
tristate "Acer WMI Laptop Extras"
|
|
depends on ACPI
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on SERIO_I8042
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
depends on ACPI_WMI
|
|
select INPUT_SPARSEKMAP
|
|
# Acer WMI depends on ACPI_VIDEO when ACPI is enabled
|
|
select ACPI_VIDEO if ACPI
|
|
---help---
|
|
This is a driver for newer Acer (and Wistron) laptops. It adds
|
|
wireless radio and bluetooth control, and on some laptops,
|
|
exposes the mail LED and LCD backlight.
|
|
|
|
If you have an ACPI-WMI compatible Acer/ Wistron laptop, say Y or M
|
|
here.
|
|
|
|
config ACERHDF
|
|
tristate "Acer Aspire One temperature and fan driver"
|
|
depends on ACPI && THERMAL
|
|
select THERMAL_GOV_BANG_BANG
|
|
---help---
|
|
This is a driver for Acer Aspire One netbooks. It allows to access
|
|
the temperature sensor and to control the fan.
|
|
|
|
After loading this driver the BIOS is still in control of the fan.
|
|
To let the kernel handle the fan, do:
|
|
echo -n enabled > /sys/class/thermal/thermal_zone0/mode
|
|
|
|
For more information about this driver see
|
|
<http://piie.net/files/acerhdf_README.txt>
|
|
|
|
If you have an Acer Aspire One netbook, say Y or M
|
|
here.
|
|
|
|
config ALIENWARE_WMI
|
|
tristate "Alienware Special feature control"
|
|
depends on ACPI
|
|
depends on LEDS_CLASS
|
|
depends on NEW_LEDS
|
|
depends on ACPI_WMI
|
|
---help---
|
|
This is a driver for controlling Alienware BIOS driven
|
|
features. It exposes an interface for controlling the AlienFX
|
|
zones on Alienware machines that don't contain a dedicated AlienFX
|
|
USB MCU such as the X51 and X51-R2.
|
|
|
|
config ASUS_LAPTOP
|
|
tristate "Asus Laptop Extras"
|
|
depends on ACPI
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
select INPUT_SPARSEKMAP
|
|
select INPUT_POLLDEV
|
|
---help---
|
|
This is a driver for Asus laptops, Lenovo SL and the Pegatron
|
|
Lucid tablet. It may also support some MEDION, JVC or VICTOR
|
|
laptops. It makes all the extra buttons generate standard
|
|
ACPI events and input events, and on the Lucid the built-in
|
|
accelerometer appears as an input device. It also adds
|
|
support for video output switching, LCD backlight control,
|
|
Bluetooth and Wlan control, and most importantly, allows you
|
|
to blink those fancy LEDs.
|
|
|
|
For more information see <http://acpi4asus.sf.net>.
|
|
|
|
If you have an ACPI-compatible ASUS laptop, say Y or M here.
|
|
|
|
config DELL_LAPTOP
|
|
tristate "Dell Laptop Extras"
|
|
depends on X86
|
|
depends on DCDBAS
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on RFKILL || RFKILL = n
|
|
depends on SERIO_I8042
|
|
select POWER_SUPPLY
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
default n
|
|
---help---
|
|
This driver adds support for rfkill and backlight control to Dell
|
|
laptops (except for some models covered by the Compal driver).
|
|
|
|
config DELL_WMI
|
|
tristate "Dell WMI extras"
|
|
depends on ACPI_WMI
|
|
depends on INPUT
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
Say Y here if you want to support WMI-based hotkeys on Dell laptops.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called dell-wmi.
|
|
|
|
config DELL_WMI_AIO
|
|
tristate "WMI Hotkeys for Dell All-In-One series"
|
|
depends on ACPI_WMI
|
|
depends on INPUT
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
Say Y here if you want to support WMI-based hotkeys on Dell
|
|
All-In-One machines.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called dell-wmi-aio.
|
|
|
|
config DELL_SMO8800
|
|
tristate "Dell Latitude freefall driver (ACPI SMO88XX)"
|
|
depends on ACPI
|
|
---help---
|
|
Say Y here if you want to support SMO88XX freefall devices
|
|
on Dell Latitude laptops.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called dell-smo8800.
|
|
|
|
|
|
config FUJITSU_LAPTOP
|
|
tristate "Fujitsu Laptop Extras"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on LEDS_CLASS || LEDS_CLASS=n
|
|
---help---
|
|
This is a driver for laptops built by Fujitsu:
|
|
|
|
* P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks
|
|
* Possibly other Fujitsu laptop models
|
|
* Tested with S6410 and S7020
|
|
|
|
It adds support for LCD brightness control and some hotkeys.
|
|
|
|
If you have a Fujitsu laptop, say Y or M here.
|
|
|
|
config FUJITSU_LAPTOP_DEBUG
|
|
bool "Verbose debug mode for Fujitsu Laptop Extras"
|
|
depends on FUJITSU_LAPTOP
|
|
default n
|
|
---help---
|
|
Enables extra debug output from the fujitsu extras driver, at the
|
|
expense of a slight increase in driver size.
|
|
|
|
If you are not sure, say N here.
|
|
|
|
config FUJITSU_TABLET
|
|
tristate "Fujitsu Tablet Extras"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
---help---
|
|
This is a driver for tablets built by Fujitsu:
|
|
|
|
* Lifebook P1510/P1610/P1620/Txxxx
|
|
* Stylistic ST5xxx
|
|
* Possibly other Fujitsu tablet models
|
|
|
|
It adds support for the panel buttons, docking station detection,
|
|
tablet/notebook mode detection for convertible and
|
|
orientation detection for docked slates.
|
|
|
|
If you have a Fujitsu convertible or slate, say Y or M here.
|
|
|
|
config AMILO_RFKILL
|
|
tristate "Fujitsu-Siemens Amilo rfkill support"
|
|
depends on RFKILL
|
|
depends on SERIO_I8042
|
|
---help---
|
|
This is a driver for enabling wifi on some Fujitsu-Siemens Amilo
|
|
laptops.
|
|
|
|
config TC1100_WMI
|
|
tristate "HP Compaq TC1100 Tablet WMI Extras"
|
|
depends on !X86_64
|
|
depends on ACPI
|
|
depends on ACPI_WMI
|
|
---help---
|
|
This is a driver for the WMI extensions (wireless and bluetooth power
|
|
control) of the HP Compaq TC1100 tablet.
|
|
|
|
config HP_ACCEL
|
|
tristate "HP laptop accelerometer"
|
|
depends on INPUT && ACPI
|
|
depends on SERIO_I8042
|
|
select SENSORS_LIS3LV02D
|
|
select NEW_LEDS
|
|
select LEDS_CLASS
|
|
help
|
|
This driver provides support for the "Mobile Data Protection System 3D"
|
|
or "3D DriveGuard" feature of HP laptops. On such systems the driver
|
|
should load automatically (via ACPI alias).
|
|
|
|
Support for a led indicating disk protection will be provided as
|
|
hp::hddprotect. For more information on the feature, refer to
|
|
Documentation/misc-devices/lis3lv02d.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called hp_accel.
|
|
|
|
config HP_WIRELESS
|
|
tristate "HP wireless button"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
help
|
|
This driver provides supports for new HP wireless button for Windows 8.
|
|
On such systems the driver should load automatically (via ACPI alias).
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called hp-wireless.
|
|
|
|
config HP_WMI
|
|
tristate "HP WMI extras"
|
|
depends on ACPI_WMI
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
select INPUT_SPARSEKMAP
|
|
help
|
|
Say Y here if you want to support WMI-based hotkeys on HP laptops and
|
|
to read data from WMI such as docking or ambient light sensor state.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called hp-wmi.
|
|
|
|
config MSI_LAPTOP
|
|
tristate "MSI Laptop Extras"
|
|
depends on ACPI
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on RFKILL
|
|
depends on INPUT && SERIO_I8042
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
This is a driver for laptops built by MSI (MICRO-STAR
|
|
INTERNATIONAL):
|
|
|
|
MSI MegaBook S270 (MS-1013)
|
|
Cytron/TCM/Medion/Tchibo MD96100/SAM2000
|
|
|
|
It adds support for Bluetooth, WLAN and LCD brightness control.
|
|
|
|
More information about this driver is available at
|
|
<http://0pointer.de/lennart/tchibo.html>.
|
|
|
|
If you have an MSI S270 laptop, say Y or M here.
|
|
|
|
config PANASONIC_LAPTOP
|
|
tristate "Panasonic Laptop Extras"
|
|
depends on INPUT && ACPI
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
This driver adds support for access to backlight control and hotkeys
|
|
on Panasonic Let's Note laptops.
|
|
|
|
If you have a Panasonic Let's note laptop (such as the R1(N variant),
|
|
R2, R3, R5, T2, W2 and Y2 series), say Y.
|
|
|
|
config COMPAL_LAPTOP
|
|
tristate "Compal (and others) Laptop Extras"
|
|
depends on ACPI
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on RFKILL
|
|
depends on HWMON
|
|
depends on POWER_SUPPLY
|
|
---help---
|
|
This is a driver for laptops built by Compal, and some models by
|
|
other brands (e.g. Dell, Toshiba).
|
|
|
|
It adds support for rfkill, Bluetooth, WLAN and LCD brightness
|
|
control.
|
|
|
|
For a (possibly incomplete) list of supported laptops, please refer
|
|
to: Documentation/platform/x86-laptop-drivers.txt
|
|
|
|
config SONY_LAPTOP
|
|
tristate "Sony Laptop Extras"
|
|
depends on ACPI
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
depends on INPUT
|
|
depends on RFKILL
|
|
---help---
|
|
This mini-driver drives the SNC and SPIC devices present in the ACPI
|
|
BIOS of the Sony Vaio laptops.
|
|
|
|
It gives access to some extra laptop functionalities like Bluetooth,
|
|
screen brightness control, Fn keys and allows powering on/off some
|
|
devices.
|
|
|
|
Read <file:Documentation/laptops/sony-laptop.txt> for more information.
|
|
|
|
config SONYPI_COMPAT
|
|
bool "Sonypi compatibility"
|
|
depends on SONY_LAPTOP
|
|
---help---
|
|
Build the sonypi driver compatibility code into the sony-laptop driver.
|
|
|
|
config IDEAPAD_LAPTOP
|
|
tristate "Lenovo IdeaPad Laptop Extras"
|
|
depends on ACPI
|
|
depends on RFKILL && INPUT
|
|
depends on SERIO_I8042
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
select INPUT_SPARSEKMAP
|
|
help
|
|
This is a driver for Lenovo IdeaPad netbooks contains drivers for
|
|
rfkill switch, hotkey, fan control and backlight control.
|
|
|
|
config THINKPAD_ACPI
|
|
tristate "ThinkPad ACPI Laptop Extras"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
select BACKLIGHT_LCD_SUPPORT
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
select HWMON
|
|
select NVRAM
|
|
select NEW_LEDS
|
|
select LEDS_CLASS
|
|
---help---
|
|
This is a driver for the IBM and Lenovo ThinkPad laptops. It adds
|
|
support for Fn-Fx key combinations, Bluetooth control, video
|
|
output switching, ThinkLight control, UltraBay eject and more.
|
|
For more information about this driver see
|
|
<file:Documentation/laptops/thinkpad-acpi.txt> and
|
|
<http://ibm-acpi.sf.net/> .
|
|
|
|
This driver was formerly known as ibm-acpi.
|
|
|
|
Extra functionality will be available if the rfkill (CONFIG_RFKILL)
|
|
and/or ALSA (CONFIG_SND) subsystems are available in the kernel.
|
|
Note that if you want ThinkPad-ACPI to be built-in instead of
|
|
modular, ALSA and rfkill will also have to be built-in.
|
|
|
|
If you have an IBM or Lenovo ThinkPad laptop, say Y or M here.
|
|
|
|
config THINKPAD_ACPI_ALSA_SUPPORT
|
|
bool "Console audio control ALSA interface"
|
|
depends on THINKPAD_ACPI
|
|
depends on SND
|
|
depends on SND = y || THINKPAD_ACPI = SND
|
|
default y
|
|
---help---
|
|
Enables monitoring of the built-in console audio output control
|
|
(headphone and speakers), which is operated by the mute and (in
|
|
some ThinkPad models) volume hotkeys.
|
|
|
|
If this option is enabled, ThinkPad-ACPI will export an ALSA card
|
|
with a single read-only mixer control, which should be used for
|
|
on-screen-display feedback purposes by the Desktop Environment.
|
|
|
|
Optionally, the driver will also allow software control (the
|
|
ALSA mixer will be made read-write). Please refer to the driver
|
|
documentation for details.
|
|
|
|
All IBM models have both volume and mute control. Newer Lenovo
|
|
models only have mute control (the volume hotkeys are just normal
|
|
keys and volume control is done through the main HDA mixer).
|
|
|
|
config THINKPAD_ACPI_DEBUGFACILITIES
|
|
bool "Maintainer debug facilities"
|
|
depends on THINKPAD_ACPI
|
|
default n
|
|
---help---
|
|
Enables extra stuff in the thinkpad-acpi which is completely useless
|
|
for normal use. Read the driver source to find out what it does.
|
|
|
|
Say N here, unless you were told by a kernel maintainer to do
|
|
otherwise.
|
|
|
|
config THINKPAD_ACPI_DEBUG
|
|
bool "Verbose debug mode"
|
|
depends on THINKPAD_ACPI
|
|
default n
|
|
---help---
|
|
Enables extra debugging information, at the expense of a slightly
|
|
increase in driver size.
|
|
|
|
If you are not sure, say N here.
|
|
|
|
config THINKPAD_ACPI_UNSAFE_LEDS
|
|
bool "Allow control of important LEDs (unsafe)"
|
|
depends on THINKPAD_ACPI
|
|
default n
|
|
---help---
|
|
Overriding LED state on ThinkPads can mask important
|
|
firmware alerts (like critical battery condition), or misled
|
|
the user into damaging the hardware (undocking or ejecting
|
|
the bay while buses are still active), etc.
|
|
|
|
LED control on the ThinkPad is write-only (with very few
|
|
exceptions on very ancient models), which makes it
|
|
impossible to know beforehand if important information will
|
|
be lost when one changes LED state.
|
|
|
|
Users that know what they are doing can enable this option
|
|
and the driver will allow control of every LED, including
|
|
the ones on the dock stations.
|
|
|
|
Never enable this option on a distribution kernel.
|
|
|
|
Say N here, unless you are building a kernel for your own
|
|
use, and need to control the important firmware LEDs.
|
|
|
|
config THINKPAD_ACPI_VIDEO
|
|
bool "Video output control support"
|
|
depends on THINKPAD_ACPI
|
|
default y
|
|
---help---
|
|
Allows the thinkpad_acpi driver to provide an interface to control
|
|
the various video output ports.
|
|
|
|
This feature often won't work well, depending on ThinkPad model,
|
|
display state, video output devices in use, whether there is a X
|
|
server running, phase of the moon, and the current mood of
|
|
Schroedinger's cat. If you can use X.org's RandR to control
|
|
your ThinkPad's video output ports instead of this feature,
|
|
don't think twice: do it and say N here to save memory and avoid
|
|
bad interactions with X.org.
|
|
|
|
NOTE: access to this feature is limited to processes with the
|
|
CAP_SYS_ADMIN capability, to avoid local DoS issues in platforms
|
|
where it interacts badly with X.org.
|
|
|
|
If you are not sure, say Y here but do try to check if you could
|
|
be using X.org RandR instead.
|
|
|
|
config THINKPAD_ACPI_HOTKEY_POLL
|
|
bool "Support NVRAM polling for hot keys"
|
|
depends on THINKPAD_ACPI
|
|
default y
|
|
---help---
|
|
Some thinkpad models benefit from NVRAM polling to detect a few of
|
|
the hot key press events. If you know your ThinkPad model does not
|
|
need to do NVRAM polling to support any of the hot keys you use,
|
|
unselecting this option will save about 1kB of memory.
|
|
|
|
ThinkPads T40 and newer, R52 and newer, and X31 and newer are
|
|
unlikely to need NVRAM polling in their latest BIOS versions.
|
|
|
|
NVRAM polling can detect at most the following keys: ThinkPad/Access
|
|
IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute,
|
|
Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12).
|
|
|
|
If you are not sure, say Y here. The driver enables polling only if
|
|
it is strictly necessary to do so.
|
|
|
|
config SENSORS_HDAPS
|
|
tristate "Thinkpad Hard Drive Active Protection System (hdaps)"
|
|
depends on INPUT && X86
|
|
select INPUT_POLLDEV
|
|
default n
|
|
help
|
|
This driver provides support for the IBM Hard Drive Active Protection
|
|
System (hdaps), which provides an accelerometer and other misc. data.
|
|
ThinkPads starting with the R50, T41, and X40 are supported. The
|
|
accelerometer data is readable via sysfs.
|
|
|
|
This driver also provides an absolute input class device, allowing
|
|
the laptop to act as a pinball machine-esque joystick.
|
|
|
|
If your ThinkPad is not recognized by the driver, please update to latest
|
|
BIOS. This is especially the case for some R52 ThinkPads.
|
|
|
|
Say Y here if you have an applicable laptop and want to experience
|
|
the awesome power of hdaps.
|
|
|
|
config INTEL_MENLOW
|
|
tristate "Thermal Management driver for Intel menlow platform"
|
|
depends on ACPI_THERMAL
|
|
select THERMAL
|
|
---help---
|
|
ACPI thermal management enhancement driver on
|
|
Intel Menlow platform.
|
|
|
|
If unsure, say N.
|
|
|
|
config EEEPC_LAPTOP
|
|
tristate "Eee PC Hotkey Driver"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
depends on HOTPLUG_PCI
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
select HWMON
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
This driver supports the Fn-Fx keys on Eee PC laptops.
|
|
|
|
It also gives access to some extra laptop functionalities like
|
|
Bluetooth, backlight and allows powering on/off some other
|
|
devices.
|
|
|
|
If you have an Eee PC laptop, say Y or M here. If this driver
|
|
doesn't work on your Eee PC, try eeepc-wmi instead.
|
|
|
|
config ASUS_WMI
|
|
tristate "ASUS WMI Driver"
|
|
depends on ACPI_WMI
|
|
depends on INPUT
|
|
depends on HWMON
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on RFKILL || RFKILL = n
|
|
depends on HOTPLUG_PCI
|
|
depends on ACPI_VIDEO || ACPI_VIDEO = n
|
|
select INPUT_SPARSEKMAP
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
---help---
|
|
Say Y here if you have a WMI aware Asus laptop (like Eee PCs or new
|
|
Asus Notebooks).
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called asus-wmi.
|
|
|
|
config ASUS_NB_WMI
|
|
tristate "Asus Notebook WMI Driver"
|
|
depends on ASUS_WMI
|
|
---help---
|
|
This is a driver for newer Asus notebooks. It adds extra features
|
|
like wireless radio and bluetooth control, leds, hotkeys, backlight...
|
|
|
|
For more information, see
|
|
<file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
|
|
|
|
If you have an ACPI-WMI compatible Asus Notebook, say Y or M
|
|
here.
|
|
|
|
config EEEPC_WMI
|
|
tristate "Eee PC WMI Driver"
|
|
depends on ASUS_WMI
|
|
---help---
|
|
This is a driver for newer Eee PC laptops. It adds extra features
|
|
like wireless radio and bluetooth control, leds, hotkeys, backlight...
|
|
|
|
For more information, see
|
|
<file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
|
|
|
|
If you have an ACPI-WMI compatible Eee PC laptop (>= 1000), say Y or M
|
|
here.
|
|
|
|
config ACPI_WMI
|
|
tristate "WMI"
|
|
depends on ACPI
|
|
help
|
|
This driver adds support for the ACPI-WMI (Windows Management
|
|
Instrumentation) mapper device (PNP0C14) found on some systems.
|
|
|
|
ACPI-WMI is a proprietary extension to ACPI to expose parts of the
|
|
ACPI firmware to userspace - this is done through various vendor
|
|
defined methods and data blocks in a PNP0C14 device, which are then
|
|
made available for userspace to call.
|
|
|
|
The implementation of this in Linux currently only exposes this to
|
|
other kernel space drivers.
|
|
|
|
This driver is a required dependency to build the firmware specific
|
|
drivers needed on many machines, including Acer and HP laptops.
|
|
|
|
It is safe to enable this driver even if your DSDT doesn't define
|
|
any ACPI-WMI devices.
|
|
|
|
config MSI_WMI
|
|
tristate "MSI WMI extras"
|
|
depends on ACPI_WMI
|
|
depends on INPUT
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
select INPUT_SPARSEKMAP
|
|
help
|
|
Say Y here if you want to support WMI-based hotkeys on MSI laptops.
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
be called msi-wmi.
|
|
|
|
config TOPSTAR_LAPTOP
|
|
tristate "Topstar Laptop Extras"
|
|
depends on ACPI
|
|
depends on INPUT
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
This driver adds support for hotkeys found on Topstar laptops.
|
|
|
|
If you have a Topstar laptop, say Y or M here.
|
|
|
|
config ACPI_TOSHIBA
|
|
tristate "Toshiba Laptop Extras"
|
|
depends on ACPI
|
|
depends on ACPI_WMI
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on INPUT
|
|
depends on RFKILL || RFKILL = n
|
|
depends on SERIO_I8042 || SERIO_I8042 = n
|
|
select INPUT_POLLDEV
|
|
select INPUT_SPARSEKMAP
|
|
---help---
|
|
This driver adds support for access to certain system settings
|
|
on "legacy free" Toshiba laptops. These laptops can be recognized by
|
|
their lack of a BIOS setup menu and APM support.
|
|
|
|
On these machines, all system configuration is handled through the
|
|
ACPI. This driver is required for access to controls not covered
|
|
by the general ACPI drivers, such as LCD brightness, video output,
|
|
etc.
|
|
|
|
This driver differs from the non-ACPI Toshiba laptop driver (located
|
|
under "Processor type and features") in several aspects.
|
|
Configuration is accessed by reading and writing text files in the
|
|
/proc tree instead of by program interface to /dev. Furthermore, no
|
|
power management functions are exposed, as those are handled by the
|
|
general ACPI drivers.
|
|
|
|
More information about this driver is available at
|
|
<http://memebeam.org/toys/ToshibaAcpiDriver>.
|
|
|
|
If you have a legacy free Toshiba laptop (such as the Libretto L1
|
|
series), say Y.
|
|
|
|
config TOSHIBA_BT_RFKILL
|
|
tristate "Toshiba Bluetooth RFKill switch support"
|
|
depends on ACPI
|
|
---help---
|
|
This driver adds support for Bluetooth events for the RFKill
|
|
switch on modern Toshiba laptops with full ACPI support and
|
|
an RFKill switch.
|
|
|
|
This driver handles RFKill events for the TOS6205 Bluetooth,
|
|
and re-enables it when the switch is set back to the 'on'
|
|
position.
|
|
|
|
If you have a modern Toshiba laptop with a Bluetooth and an
|
|
RFKill switch (such as the Portege R500), say Y.
|
|
|
|
config TOSHIBA_HAPS
|
|
tristate "Toshiba HDD Active Protection Sensor"
|
|
depends on ACPI
|
|
---help---
|
|
This driver adds support for the built-in accelerometer
|
|
found on recent Toshiba laptops equiped with HID TOS620A
|
|
device.
|
|
|
|
This driver receives ACPI notify events 0x80 when the sensor
|
|
detects a sudden move or a harsh vibration, as well as an
|
|
ACPI notify event 0x81 whenever the movement or vibration has
|
|
been stabilized.
|
|
|
|
Also provides sysfs entries to get/set the desired protection
|
|
level and reseting the HDD protection interface.
|
|
|
|
If you have a recent Toshiba laptop with a built-in accelerometer
|
|
device, say Y.
|
|
|
|
config ACPI_CMPC
|
|
tristate "CMPC Laptop Extras"
|
|
depends on X86 && ACPI
|
|
depends on RFKILL || RFKILL=n
|
|
select INPUT
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
default n
|
|
help
|
|
Support for Intel Classmate PC ACPI devices, including some
|
|
keys as input device, backlight device, tablet and accelerometer
|
|
devices.
|
|
|
|
config INTEL_SCU_IPC
|
|
bool "Intel SCU IPC Support"
|
|
depends on X86_INTEL_MID
|
|
default y
|
|
---help---
|
|
IPC is used to bridge the communications between kernel and SCU on
|
|
some embedded Intel x86 platforms. This is not needed for PC-type
|
|
machines.
|
|
|
|
config INTEL_SCU_IPC_UTIL
|
|
tristate "Intel SCU IPC utility driver"
|
|
depends on INTEL_SCU_IPC
|
|
default y
|
|
---help---
|
|
The IPC Util driver provides an interface with the SCU enabling
|
|
low level access for debug work and updating the firmware. Say
|
|
N unless you will be doing this on an Intel MID platform.
|
|
|
|
config GPIO_INTEL_PMIC
|
|
bool "Intel PMIC GPIO support"
|
|
depends on INTEL_SCU_IPC && GPIOLIB
|
|
---help---
|
|
Say Y here to support GPIO via the SCU IPC interface
|
|
on Intel MID platforms.
|
|
|
|
config INTEL_MID_POWER_BUTTON
|
|
tristate "power button driver for Intel MID platforms"
|
|
depends on INTEL_SCU_IPC && INPUT
|
|
help
|
|
This driver handles the power button on the Intel MID platforms.
|
|
|
|
If unsure, say N.
|
|
|
|
config INTEL_MFLD_THERMAL
|
|
tristate "Thermal driver for Intel Medfield platform"
|
|
depends on MFD_INTEL_MSIC && THERMAL
|
|
help
|
|
Say Y here to enable thermal driver support for the Intel Medfield
|
|
platform.
|
|
|
|
config INTEL_IPS
|
|
tristate "Intel Intelligent Power Sharing"
|
|
depends on ACPI
|
|
---help---
|
|
Intel Calpella platforms support dynamic power sharing between the
|
|
CPU and GPU, maximizing performance in a given TDP. This driver,
|
|
along with the CPU frequency and i915 drivers, provides that
|
|
functionality. If in doubt, say Y here; it will only load on
|
|
supported platforms.
|
|
|
|
config INTEL_IMR
|
|
bool "Intel Isolated Memory Region support"
|
|
default n
|
|
depends on X86_INTEL_QUARK && IOSF_MBI
|
|
---help---
|
|
This option provides a means to manipulate Isolated Memory Regions.
|
|
IMRs are a set of registers that define read and write access masks
|
|
to prohibit certain system agents from accessing memory with 1 KiB
|
|
granularity.
|
|
|
|
IMRs make it possible to control read/write access to an address
|
|
by hardware agents inside the SoC. Read and write masks can be
|
|
defined for:
|
|
- eSRAM flush
|
|
- Dirty CPU snoop (write only)
|
|
- RMU access
|
|
- PCI Virtual Channel 0/Virtual Channel 1
|
|
- SMM mode
|
|
- Non SMM mode
|
|
|
|
Quark contains a set of eight IMR registers and makes use of those
|
|
registers during its bootup process.
|
|
|
|
If you are running on a Galileo/Quark say Y here.
|
|
|
|
config IBM_RTL
|
|
tristate "Device driver to enable PRTL support"
|
|
depends on X86 && PCI
|
|
---help---
|
|
Enable support for IBM Premium Real Time Mode (PRTM).
|
|
This module will allow you the enter and exit PRTM in the BIOS via
|
|
sysfs on platforms that support this feature. System in PRTM will
|
|
not receive CPU-generated SMIs for recoverable errors. Use of this
|
|
feature without proper support may void your hardware warranty.
|
|
|
|
If the proper BIOS support is found the driver will load and create
|
|
/sys/devices/system/ibm_rtl/. The "state" variable will indicate
|
|
whether or not the BIOS is in PRTM.
|
|
state = 0 (BIOS SMIs on)
|
|
state = 1 (BIOS SMIs off)
|
|
|
|
config XO1_RFKILL
|
|
tristate "OLPC XO-1 software RF kill switch"
|
|
depends on OLPC || COMPILE_TEST
|
|
depends on RFKILL
|
|
---help---
|
|
Support for enabling/disabling the WLAN interface on the OLPC XO-1
|
|
laptop.
|
|
|
|
config XO15_EBOOK
|
|
tristate "OLPC XO-1.5 ebook switch"
|
|
depends on OLPC || COMPILE_TEST
|
|
depends on ACPI && INPUT
|
|
---help---
|
|
Support for the ebook switch on the OLPC XO-1.5 laptop.
|
|
|
|
This switch is triggered as the screen is rotated and folded down to
|
|
convert the device into ebook form.
|
|
|
|
config SAMSUNG_LAPTOP
|
|
tristate "Samsung Laptop driver"
|
|
depends on X86
|
|
depends on RFKILL || RFKILL = n
|
|
depends on ACPI_VIDEO || ACPI_VIDEO = n
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
select LEDS_CLASS
|
|
select NEW_LEDS
|
|
---help---
|
|
This module implements a driver for a wide range of different
|
|
Samsung laptops. It offers control over the different
|
|
function keys, wireless LED, LCD backlight level.
|
|
|
|
It may also provide some sysfs files described in
|
|
<file:Documentation/ABI/testing/sysfs-platform-samsung-laptop>
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called samsung-laptop.
|
|
|
|
config MXM_WMI
|
|
tristate "WMI support for MXM Laptop Graphics"
|
|
depends on ACPI_WMI
|
|
---help---
|
|
MXM is a standard for laptop graphics cards, the WMI interface
|
|
is required for switchable nvidia graphics machines
|
|
|
|
config INTEL_OAKTRAIL
|
|
tristate "Intel Oaktrail Platform Extras"
|
|
depends on ACPI
|
|
depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI
|
|
---help---
|
|
Intel Oaktrail platform need this driver to provide interfaces to
|
|
enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y
|
|
here; it will only load on supported platforms.
|
|
|
|
config SAMSUNG_Q10
|
|
tristate "Samsung Q10 Extras"
|
|
depends on ACPI
|
|
select BACKLIGHT_CLASS_DEVICE
|
|
---help---
|
|
This driver provides support for backlight control on Samsung Q10
|
|
and related laptops, including Dell Latitude X200.
|
|
|
|
config APPLE_GMUX
|
|
tristate "Apple Gmux Driver"
|
|
depends on ACPI
|
|
depends on PNP
|
|
depends on BACKLIGHT_CLASS_DEVICE
|
|
depends on BACKLIGHT_APPLE=n || BACKLIGHT_APPLE
|
|
depends on ACPI_VIDEO=n || ACPI_VIDEO
|
|
---help---
|
|
This driver provides support for the gmux device found on many
|
|
Apple laptops, which controls the display mux for the hybrid
|
|
graphics as well as the backlight. Currently only backlight
|
|
control is supported by the driver.
|
|
|
|
config INTEL_RST
|
|
tristate "Intel Rapid Start Technology Driver"
|
|
depends on ACPI
|
|
---help---
|
|
This driver provides support for modifying paramaters on systems
|
|
equipped with Intel's Rapid Start Technology. When put in an ACPI
|
|
sleep state, these devices will wake after either a configured
|
|
timeout or when the system battery reaches a critical state,
|
|
automatically copying memory contents to disk. On resume, the
|
|
firmware will copy the memory contents back to RAM and resume the OS
|
|
as usual.
|
|
|
|
config INTEL_SMARTCONNECT
|
|
tristate "Intel Smart Connect disabling driver"
|
|
depends on ACPI
|
|
---help---
|
|
Intel Smart Connect is a technology intended to permit devices to
|
|
update state by resuming for a short period of time at regular
|
|
intervals. If a user enables this functionality under Windows and
|
|
then reboots into Linux, the system may remain configured to resume
|
|
on suspend. In the absence of any userspace to support it, the system
|
|
will then remain awake until something triggers another suspend.
|
|
|
|
This driver checks to determine whether the device has Intel Smart
|
|
Connect enabled, and if so disables it.
|
|
|
|
config PVPANIC
|
|
tristate "pvpanic device support"
|
|
depends on ACPI
|
|
---help---
|
|
This driver provides support for the pvpanic device. pvpanic is
|
|
a paravirtualized device provided by QEMU; it lets a virtual machine
|
|
(guest) communicate panic events to the host.
|
|
|
|
endif # X86_PLATFORM_DEVICES
|