blob: 9b121a569ab4397841ac9611aad90502fefb16b7 [file] [log] [blame]
Mika Westerberg59c39872012-12-07 23:11:51 +01001ACPI based device enumeration
2~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3ACPI 5 introduced a set of new resources (UartTSerialBus, I2cSerialBus,
4SpiSerialBus, GpioIo and GpioInt) which can be used in enumerating slave
5devices behind serial bus controllers.
6
7In addition we are starting to see peripherals integrated in the
8SoC/Chipset to appear only in ACPI namespace. These are typically devices
9that are accessed through memory-mapped registers.
10
11In order to support this and re-use the existing drivers as much as
12possible we decided to do following:
13
14 o Devices that have no bus connector resource are represented as
15 platform devices.
16
17 o Devices behind real busses where there is a connector resource
18 are represented as struct spi_device or struct i2c_device
19 (standard UARTs are not busses so there is no struct uart_device).
20
21As both ACPI and Device Tree represent a tree of devices (and their
22resources) this implementation follows the Device Tree way as much as
23possible.
24
25The ACPI implementation enumerates devices behind busses (platform, SPI and
26I2C), creates the physical devices and binds them to their ACPI handle in
27the ACPI namespace.
28
29This means that when ACPI_HANDLE(dev) returns non-NULL the device was
30enumerated from ACPI namespace. This handle can be used to extract other
31device-specific configuration. There is an example of this below.
32
33Platform bus support
34~~~~~~~~~~~~~~~~~~~~
35Since we are using platform devices to represent devices that are not
36connected to any physical bus we only need to implement a platform driver
37for the device and add supported ACPI IDs. If this same IP-block is used on
38some other non-ACPI platform, the driver might work out of the box or needs
39some minor changes.
40
41Adding ACPI support for an existing driver should be pretty
42straightforward. Here is the simplest example:
43
44 #ifdef CONFIG_ACPI
45 static struct acpi_device_id mydrv_acpi_match[] = {
46 /* ACPI IDs here */
47 { }
48 };
49 MODULE_DEVICE_TABLE(acpi, mydrv_acpi_match);
50 #endif
51
52 static struct platform_driver my_driver = {
53 ...
54 .driver = {
55 .acpi_match_table = ACPI_PTR(mydrv_acpi_match),
56 },
57 };
58
59If the driver needs to perform more complex initialization like getting and
60configuring GPIOs it can get its ACPI handle and extract this information
61from ACPI tables.
62
Andy Shevchenko1b2e98b2013-04-09 14:05:43 +030063DMA support
64~~~~~~~~~~~
65DMA controllers enumerated via ACPI should be registered in the system to
66provide generic access to their resources. For example, a driver that would
67like to be accessible to slave devices via generic API call
68dma_request_slave_channel() must register itself at the end of the probe
69function like this:
70
71 err = devm_acpi_dma_controller_register(dev, xlate_func, dw);
72 /* Handle the error if it's not a case of !CONFIG_ACPI */
73
74and implement custom xlate function if needed (usually acpi_dma_simple_xlate()
75is enough) which converts the FixedDMA resource provided by struct
76acpi_dma_spec into the corresponding DMA channel. A piece of code for that case
77could look like:
78
79 #ifdef CONFIG_ACPI
80 struct filter_args {
81 /* Provide necessary information for the filter_func */
82 ...
83 };
84
85 static bool filter_func(struct dma_chan *chan, void *param)
86 {
87 /* Choose the proper channel */
88 ...
89 }
90
91 static struct dma_chan *xlate_func(struct acpi_dma_spec *dma_spec,
92 struct acpi_dma *adma)
93 {
94 dma_cap_mask_t cap;
95 struct filter_args args;
96
97 /* Prepare arguments for filter_func */
98 ...
99 return dma_request_channel(cap, filter_func, &args);
100 }
101 #else
102 static struct dma_chan *xlate_func(struct acpi_dma_spec *dma_spec,
103 struct acpi_dma *adma)
104 {
105 return NULL;
106 }
107 #endif
108
109dma_request_slave_channel() will call xlate_func() for each registered DMA
110controller. In the xlate function the proper channel must be chosen based on
111information in struct acpi_dma_spec and the properties of the controller
112provided by struct acpi_dma.
113
114Clients must call dma_request_slave_channel() with the string parameter that
115corresponds to a specific FixedDMA resource. By default "tx" means the first
116entry of the FixedDMA resource array, "rx" means the second entry. The table
117below shows a layout:
118
119 Device (I2C0)
120 {
121 ...
122 Method (_CRS, 0, NotSerialized)
123 {
124 Name (DBUF, ResourceTemplate ()
125 {
126 FixedDMA (0x0018, 0x0004, Width32bit, _Y48)
127 FixedDMA (0x0019, 0x0005, Width32bit, )
128 })
129 ...
130 }
131 }
132
133So, the FixedDMA with request line 0x0018 is "tx" and next one is "rx" in
134this example.
135
136In robust cases the client unfortunately needs to call
137acpi_dma_request_slave_chan_by_index() directly and therefore choose the
138specific FixedDMA resource by its index.
139
Mika Westerberg59c39872012-12-07 23:11:51 +0100140SPI serial bus support
141~~~~~~~~~~~~~~~~~~~~~~
142Slave devices behind SPI bus have SpiSerialBus resource attached to them.
143This is extracted automatically by the SPI core and the slave devices are
144enumerated once spi_register_master() is called by the bus driver.
145
146Here is what the ACPI namespace for a SPI slave might look like:
147
148 Device (EEP0)
149 {
150 Name (_ADR, 1)
151 Name (_CID, Package() {
152 "ATML0025",
153 "AT25",
154 })
155 ...
156 Method (_CRS, 0, NotSerialized)
157 {
158 SPISerialBus(1, PolarityLow, FourWireMode, 8,
159 ControllerInitiated, 1000000, ClockPolarityLow,
160 ClockPhaseFirst, "\\_SB.PCI0.SPI1",)
161 }
162 ...
163
164The SPI device drivers only need to add ACPI IDs in a similar way than with
165the platform device drivers. Below is an example where we add ACPI support
166to at25 SPI eeprom driver (this is meant for the above ACPI snippet):
167
168 #ifdef CONFIG_ACPI
169 static struct acpi_device_id at25_acpi_match[] = {
170 { "AT25", 0 },
171 { },
172 };
173 MODULE_DEVICE_TABLE(acpi, at25_acpi_match);
174 #endif
175
176 static struct spi_driver at25_driver = {
177 .driver = {
178 ...
179 .acpi_match_table = ACPI_PTR(at25_acpi_match),
180 },
181 };
182
183Note that this driver actually needs more information like page size of the
184eeprom etc. but at the time writing this there is no standard way of
185passing those. One idea is to return this in _DSM method like:
186
187 Device (EEP0)
188 {
189 ...
190 Method (_DSM, 4, NotSerialized)
191 {
192 Store (Package (6)
193 {
194 "byte-len", 1024,
195 "addr-mode", 2,
196 "page-size, 32
197 }, Local0)
198
199 // Check UUIDs etc.
200
201 Return (Local0)
202 }
203
Stefan Huber2d6674b2013-06-27 12:54:52 +0200204Then the at25 SPI driver can get this configuration by calling _DSM on its
Mika Westerberg59c39872012-12-07 23:11:51 +0100205ACPI handle like:
206
207 struct acpi_buffer output = { ACPI_ALLOCATE_BUFFER, NULL };
208 struct acpi_object_list input;
209 acpi_status status;
210
211 /* Fill in the input buffer */
212
213 status = acpi_evaluate_object(ACPI_HANDLE(&spi->dev), "_DSM",
214 &input, &output);
215 if (ACPI_FAILURE(status))
216 /* Handle the error */
217
218 /* Extract the data here */
219
220 kfree(output.pointer);
221
222I2C serial bus support
223~~~~~~~~~~~~~~~~~~~~~~
224The slaves behind I2C bus controller only need to add the ACPI IDs like
Mika Westerberg55e71ed2013-08-21 17:28:23 +0300225with the platform and SPI drivers. The I2C core automatically enumerates
226any slave devices behind the controller device once the adapter is
227registered.
Mika Westerberg59c39872012-12-07 23:11:51 +0100228
229Below is an example of how to add ACPI support to the existing mpu3050
230input driver:
231
232 #ifdef CONFIG_ACPI
233 static struct acpi_device_id mpu3050_acpi_match[] = {
234 { "MPU3050", 0 },
235 { },
236 };
237 MODULE_DEVICE_TABLE(acpi, mpu3050_acpi_match);
238 #endif
239
240 static struct i2c_driver mpu3050_i2c_driver = {
241 .driver = {
242 .name = "mpu3050",
243 .owner = THIS_MODULE,
244 .pm = &mpu3050_pm,
245 .of_match_table = mpu3050_of_match,
Yaowei Baide14da22015-01-15 21:59:16 +0800246 .acpi_match_table = ACPI_PTR(mpu3050_acpi_match),
Mika Westerberg59c39872012-12-07 23:11:51 +0100247 },
248 .probe = mpu3050_probe,
Greg Kroah-Hartman63a29f72012-12-21 15:15:02 -0800249 .remove = mpu3050_remove,
Mika Westerberg59c39872012-12-07 23:11:51 +0100250 .id_table = mpu3050_ids,
251 };
252
253GPIO support
254~~~~~~~~~~~~
255ACPI 5 introduced two new resources to describe GPIO connections: GpioIo
256and GpioInt. These resources are used be used to pass GPIO numbers used by
257the device to the driver. For example:
258
259 Method (_CRS, 0, NotSerialized)
260 {
261 Name (SBUF, ResourceTemplate()
262 {
Mika Westerberg12028d22013-04-03 13:56:54 +0300263 ...
264 // Used to power on/off the device
Mika Westerberg59c39872012-12-07 23:11:51 +0100265 GpioIo (Exclusive, PullDefault, 0x0000, 0x0000,
266 IoRestrictionOutputOnly, "\\_SB.PCI0.GPI0",
267 0x00, ResourceConsumer,,)
268 {
269 // Pin List
270 0x0055
271 }
Mika Westerberg12028d22013-04-03 13:56:54 +0300272
273 // Interrupt for the device
274 GpioInt (Edge, ActiveHigh, ExclusiveAndWake, PullNone,
275 0x0000, "\\_SB.PCI0.GPI0", 0x00, ResourceConsumer,,)
276 {
277 // Pin list
278 0x0058
279 }
280
Mika Westerberg59c39872012-12-07 23:11:51 +0100281 ...
282
Mika Westerberg59c39872012-12-07 23:11:51 +0100283 }
Mika Westerberg12028d22013-04-03 13:56:54 +0300284
285 Return (SBUF)
Mika Westerberg59c39872012-12-07 23:11:51 +0100286 }
287
288These GPIO numbers are controller relative and path "\\_SB.PCI0.GPI0"
289specifies the path to the controller. In order to use these GPIOs in Linux
Mika Westerbergccb6fbb2014-01-08 12:40:57 +0200290we need to translate them to the corresponding Linux GPIO descriptors.
Mika Westerberg59c39872012-12-07 23:11:51 +0100291
Mika Westerbergccb6fbb2014-01-08 12:40:57 +0200292There is a standard GPIO API for that and is documented in
Jarkko Nikula51caa052014-05-21 16:58:25 +0300293Documentation/gpio/.
Mika Westerberg12028d22013-04-03 13:56:54 +0300294
Mika Westerbergccb6fbb2014-01-08 12:40:57 +0200295In the above example we can get the corresponding two GPIO descriptors with
296a code like this:
Mika Westerberg45f39432013-10-10 11:01:11 +0300297
298 #include <linux/gpio/consumer.h>
299 ...
300
301 struct gpio_desc *irq_desc, *power_desc;
302
303 irq_desc = gpiod_get_index(dev, NULL, 1);
304 if (IS_ERR(irq_desc))
305 /* handle error */
306
307 power_desc = gpiod_get_index(dev, NULL, 0);
308 if (IS_ERR(power_desc))
309 /* handle error */
310
311 /* Now we can use the GPIO descriptors */
312
Mika Westerbergccb6fbb2014-01-08 12:40:57 +0200313There are also devm_* versions of these functions which release the
314descriptors once the device is released.
Mika Westerberg6ab34302014-09-16 14:52:36 +0300315
316MFD devices
317~~~~~~~~~~~
318The MFD devices register their children as platform devices. For the child
319devices there needs to be an ACPI handle that they can use to reference
320parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
321we provide two ways:
322
323 o The children share the parent ACPI handle.
324 o The MFD cell can specify the ACPI id of the device.
325
326For the first case, the MFD drivers do not need to do anything. The
327resulting child platform device will have its ACPI_COMPANION() set to point
328to the parent device.
329
330If the ACPI namespace has a device that we can match using an ACPI id,
331the id should be set like:
332
333 static struct mfd_cell my_subdevice_cell = {
334 .name = "my_subdevice",
335 /* set the resources relative to the parent */
336 .acpi_pnpid = "XYZ0001",
337 };
338
339The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
340the MFD device and if found, that ACPI companion device is bound to the
341resulting child platform device.