Searched full:describe (Results 1 – 25 of 319) sorted by relevance
12345678910>>...13
| /Documentation/PCI/ |
| D | acpi-info.rst | 7 The general rule is that the ACPI namespace should describe everything the
11 host bridges, so the ACPI namespace must describe each host bridge, the
19 devices and read and size their BARs. However, ACPI may describe PCI
22 controllers and a _PRT is needed to describe those connections.
45 describe all the address space they consume. This includes all the windows
49 range below the bridge, window registers that describe the apertures, etc.
64 Consumer/Producer meant there was no way to describe bridge registers in
65 the PNP0A03/PNP0A08 device itself. The workaround was to describe the
76 describe bridge registers this way on those architectures.
92 The MCFG table must describe the ECAM space of non-hot pluggable host
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-nilfs2 | 14 Describe attributes of /sys/fs/nilfs2/features group.
58 Describe attributes of /sys/fs/nilfs2/<device> group.
90 Describe attributes of /sys/fs/nilfs2/<device>/superblock
180 Describe attributes of /sys/fs/nilfs2/<device>/segctor
211 Describe attributes of /sys/fs/nilfs2/<device>/segments
242 Describe attributes of /sys/fs/nilfs2/<device>/checkpoints
249 Describe content of /sys/fs/nilfs2/<device>/mounted_snapshots
268 Describe attributes of /sys/fs/nilfs2/<device>/mounted_snapshots/<id>
|
| D | sysfs-bus-event_source-devices-format | 6 Attribute group to describe the magic bits that go into
|
| D | sysfs-bus-iio-adc-max9611 | 15 These attributes describe a single physical component, exposed as two distinct
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-fsi.txt | 11 - child nodes : Nodes to describe busses off the I2C
18 - child nodes : Nodes to describe devices on the I2C
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
24 configured in this periph mode. All the periph and bank need to be describe.
41 For each peripheral/bank we will describe in a u32 if a pin can be
112 name describe the pin function and group hierarchy.
118 4. The gpio controller must be describe in the pinctrl simple-bus.
|
| D | nvidia,tegra124-dpaux-padctl.txt | 21 needed to describe the pin mux'ing options for the DPAUX pads.
23 single set of pads, the child nodes only need to describe the pad group
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 11 FSI masters may require their own DT nodes (to describe the master HW itself);
15 Under the masters' nodes, we can describe the bus topology using nodes to
52 Since the master nodes describe the top-level of the FSI topology, they also
116 additional engines, but they don't necessarily need to be describe in the
135 * it's an I2C master controller, so subnodes describe the
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | led-backlight.yaml | 15 This binding is used to describe a basic backlight device made of LEDs. It
16 can also be used to describe a backlight device controlled by the output of
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb3503.txt | 11 '1' or '2' or '3' are available for this property to describe the port
13 Do not describe this property if all ports have to be enabled.
|
| /Documentation/input/ |
| D | event-codes.rst | 41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
183 EV_REL events describe relative changes in a property. For example, a mouse may
217 EV_ABS events describe absolute changes in a property. For example, a touchpad
224 - Used to describe the distance of a tool from an interaction surface. This
236 - Used to describe multitouch input events. Please see
242 EV_SW events describe stateful binary switches. For example, the SW_LID code is
|
| /Documentation/devicetree/bindings/ufs/ |
| D | ufs-hisi.txt | 3 UFS nodes are defined to describe on-chip UFS hardware macro.
22 - resets : describe reset node register
|
| D | tc-dwc-g210-pltfrm.txt | 3 DWC_UFS nodes are defined to describe on-chip UFS host controllers and MPHY.
|
| /Documentation/devicetree/bindings/arm/stm32/ |
| D | st,mlahb.yaml | 14 These bindings describe the STM32 SoCs ML-AHB interconnect bus which connects
33 Describe memory addresses translation between the local CPU and the
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 6 The hierarchical organisation of the device tree is well suited to describe
11 phandle properties pointing to other nodes to describe connections that
23 Here the ports describe data interfaces, and the links between them are
|
| /Documentation/driver-api/80211/ |
| D | mac80211.rst | 49 This chapter should describe PHY handling including start/stop callbacks
62 This chapter should describe virtual interface basics that are relevant
85 This should describe the receive and transmit paths in mac80211/the
|
| /Documentation/devicetree/bindings/mtd/ |
| D | common.txt | 7 and/or describe what they are used for.
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-sensor.yaml | 18 The following node types are used to completely describe a thermal management
22 - thermal-zones: a container of the following node types used to describe all
|
| /Documentation/devicetree/bindings/opp/ |
| D | qcom-opp.txt | 1 Qualcomm OPP bindings to describe OPP nodes
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | sii902x.txt | 8 - interrupts: describe the interrupt line used to inform the host
40 documents on how to describe the way the sii902x device is
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | watchdog.yaml | 15 describe watchdog devices in a device tree.
|
| /Documentation/devicetree/bindings/i3c/ |
| D | i3c.txt | 4 This document describes generic bindings that should be used to describe I3C
14 For other required properties e.g. to describe register sets,
76 means we have to describe I3C devices.
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom-ipq806x-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
| D | qcom-apq8064-sata-phy.txt | 4 SATA PHY nodes are defined to describe on-chip SATA Physical layer controllers.
|
| /Documentation/devicetree/bindings/ata/ |
| D | fsl-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
12345678910>>...13