aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/acpi/enumeration.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/acpi/enumeration.txt')
-rw-r--r--Documentation/acpi/enumeration.txt8
1 files changed, 1 insertions, 7 deletions
diff --git a/Documentation/acpi/enumeration.txt b/Documentation/acpi/enumeration.txt
index 2a1519b87177..e182be5e3c83 100644
--- a/Documentation/acpi/enumeration.txt
+++ b/Documentation/acpi/enumeration.txt
@@ -60,12 +60,6 @@ If the driver needs to perform more complex initialization like getting and
60configuring GPIOs it can get its ACPI handle and extract this information 60configuring GPIOs it can get its ACPI handle and extract this information
61from ACPI tables. 61from ACPI tables.
62 62
63Currently the kernel is not able to automatically determine from which ACPI
64device it should make the corresponding platform device so we need to add
65the ACPI device explicitly to acpi_platform_device_ids list defined in
66drivers/acpi/acpi_platform.c. This limitation is only for the platform
67devices, SPI and I2C devices are created automatically as described below.
68
69DMA support 63DMA support
70~~~~~~~~~~~ 64~~~~~~~~~~~
71DMA controllers enumerated via ACPI should be registered in the system to 65DMA controllers enumerated via ACPI should be registered in the system to
@@ -296,7 +290,7 @@ specifies the path to the controller. In order to use these GPIOs in Linux
296we need to translate them to the corresponding Linux GPIO descriptors. 290we need to translate them to the corresponding Linux GPIO descriptors.
297 291
298There is a standard GPIO API for that and is documented in 292There is a standard GPIO API for that and is documented in
299Documentation/gpio.txt. 293Documentation/gpio/.
300 294
301In the above example we can get the corresponding two GPIO descriptors with 295In the above example we can get the corresponding two GPIO descriptors with
302a code like this: 296a code like this: