Searched full:describe (Results 1 – 25 of 371) sorted by relevance
12345678910>>...15
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 8 CPU hotplug in the arm64 world is commonly used to describe the kernel taking
26 while the system is running, and ACPI is not able to sufficiently describe
35 structures can describe a redistributor associated with a disabled CPU, but
36 can't describe whether the redistributor is accessible, only that it is not
62 The ACPI tables must describe all the resources of the virtual machine. CPUs
66 ``enabled``. The 'always on' GICR structure must be used to describe the
77 may malfunction if these no longer describe the running system. Linux will
|
| /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-nvdimm | 14 Description: (RO) Attribute group to describe the magic bits
32 Description: (RO) Attribute group to describe performance monitoring events
|
| D | sysfs-bus-event_source-devices-uncore | 5 Description: Read-only. An attribute to describe the alias name of
|
| D | sysfs-bus-event_source-devices-format | 6 Attribute group to describe the magic bits that go into
|
| D | sysfs-bus-event_source-devices-caps | 6 Attribute group to describe the capabilities exposed
|
| /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/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/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.
187 EV_REL events describe relative changes in a property. For example, a mouse may
221 EV_ABS events describe absolute changes in a property. For example, a touchpad
228 - Used to describe the distance of a tool from an interaction surface. This
240 - Used to describe the state of a multi-value profile switch. An event is
246 - Used to describe multitouch input events. Please see
[all …]
|
| /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/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/ABI/stable/ |
| D | sysfs-platform-wmi-bmof | 5 Binary MOF metadata used to describe the details of available ACPI WMI interfaces.
|
| /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
|
| D | thermal-cooling-devices.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/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 29 The global configuration data describe how the pixels in a particular image are
40 As the ISP processes images in tiles, each set of tiles parameters describe how
|
| /Documentation/devicetree/bindings/opp/ |
| D | ti,omap-opp-supply.yaml | 13 needed to describe such a hardware values and relate them to program
21 the OPP core to describe both regulators the platform needs. The
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra124-dpaux.yaml | 83 nodes are needed to describe the pin mux'ing options for the
86 to describe the pad group the functions are being applied to
|
| /Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.yaml | 30 The generic 'iommus' property is insufficient to describe the relationship
121 to describe the MSI controller used by the devices on the
131 The fsl-mc node may optionally have dpmac sub-nodes that describe
|
| /Documentation/devicetree/bindings/sound/ |
| D | armada-370db-audio.txt | 4 These Device Tree bindings are used to describe the audio complex
|
| /Documentation/devicetree/bindings/ata/ |
| D | fsl-sata.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | watchdog.yaml | 15 describe watchdog devices in a device tree.
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | nvmem-layout.yaml | 18 perform their parsing. The nvmem-layout container is here to describe these.
|
| /Documentation/devicetree/bindings/net/ |
| D | apm-xgene-mdio.txt | 3 MDIO node is defined to describe on-chip MDIO controller.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | mti,cpu-interrupt-controller.yaml | 13 With the irq_domain in place we can describe how the 8 IRQs are wired to the
|
12345678910>>...15