Lines Matching refs:devices

31 connections, and peripheral devices.
40 binding was created without first investigating how i2c devices were
50 information (assuming drivers were available for all devices).
246 instead of hard coding static devices for each platform, the list of
247 devices can be obtained by parsing the DT, and allocating device
252 used by Linux for memory or I/O mapped devices which cannot be detected
253 by hardware, and for 'composite' or 'virtual' devices (more on those
255 platform devices roughly correspond to device nodes at the root of the
328 nodes that don't describe devices (although arguably memory could be
330 devices, but the codec@1a is an i2c device, and the sound node
331 represents not a device, but rather how other devices are connected
346 Well, for the way that Linux models devices, just about all bus_types
347 assume that its devices are children of a bus controller.  For
352 etc.  The only devices which do not require a specific type of parent
354 later), which will happily live at the base of the Linux /sys/devices
359 to kick off discovery of devices at the root of the tree.  The
363 table (yet).  For a board that only needs to register devices,
369 as platform devices too?  For Linux DT support, the generic behaviour
370 is for child devices to be registered by the parent's device driver at
401 [Need to add discussion of adding i2c/spi/etc child devices]
403 Appendix A: AMBA devices
409 used to represent Primecell devices.  However, the fiddly bit is that
410 not all devices on an AMBA bus are Primecells, and for Linux it is