Searched full:describe (Results 1 – 25 of 769) sorted by relevance
12345678910>>...31
| /Linux-v5.10/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
|
| /Linux-v5.10/drivers/scsi/pm8001/ |
| D | pm8001_hwi.h | 151 * use to describe enable the phy (64 bytes)
214 * use to describe the sata task response (64 bytes)
239 * use to describe MPI REGISTER DEVICE Command (64 bytes)
292 * use to describe MPI Local Phy Control Response (64 bytes)
377 * use to describe MPI General Event Notification Response (64 bytes)
390 * use to describe MPI SMP REQUEST Command (64 bytes)
416 * use to describe MPI SMP Completion Response (64 bytes)
427 * use to describe MPI SSP SMP & SATA Abort Command (64 bytes)
444 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
456 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
|
| D | pm80xx_hwi.h | 349 * use to describe enable the phy (128 bytes)
411 * use to describe the sata task response (64 bytes)
445 * use to describe MPI REGISTER DEVICE Command (64 bytes)
493 * use to describe MPI Local Phy Control Response (64 bytes)
615 * use to describe MPI General Event Notification Response (64 bytes)
627 * use to describe MPI SMP REQUEST Command (64 bytes)
654 * use to describe MPI SMP Completion Response (64 bytes)
665 * use to describe MPI SSP SMP & SATA Abort Command (64 bytes)
682 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
693 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
|
| /Linux-v5.10/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>
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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
|
| /Linux-v5.10/drivers/pinctrl/renesas/ |
| D | sh_pfc.h | 62 * VIN_DATA_PIN_GROUP() is a macro used to describe the VIN pin groups
131 * Describe a config register consisting of several fields of the same width
150 * Describe a config register consisting of several fields of different widths
204 * Describe a data register
222 * Describe the mapping from GPIOs to a single IRQ
355 * Describe generic pinmux data
362 * Describe a pinmux configuration without GPIO function that needs
371 * Describe a pinmux configuration with GPIO function that needs configuration
381 * Describe a pinmux configuration without GPIO function that needs
392 * Describe a pinmux configuration with GPIO function where the pinmux function
[all …]
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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
|
| /Linux-v5.10/fs/nfs/ |
| D | fscache-index.c | 49 * Define the server object for FS-Cache. This is used to describe a server
59 * Define the superblock object for FS-Cache. This is used to describe a
126 * Define the inode object for FS-Cache. This is used to describe an inode
|
| /Linux-v5.10/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.
|
| /Linux-v5.10/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
|
| /Linux-v5.10/drivers/interconnect/imx/ |
| D | imx.h | 18 * struct imx_icc_node_adj - Describe a dynamic adjustable node
27 * struct imx_icc_node - Describe an interconnect node
|
| /Linux-v5.10/Documentation/process/ |
| D | submitting-patches.rst | 40 Describe your changes
43 Describe your problem. Whether your patch is a one-line bug fix or
49 Describe user-visible impact. Straight up crashes and lockups are
51 problem was spotted during code review, describe the impact you think
61 include numbers that back them up. But also describe non-obvious
64 different workloads. Describe the expected downsides of your
67 Once the problem is established, describe what you are actually doing
68 about it in technical detail. It's important to describe the change
89 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
571 be copied to the permanent changelog to describe this patch.
[all …]
|
| /Linux-v5.10/include/keys/ |
| D | asymmetric-subtype.h | 29 /* Describe a key of this subtype for /proc/keys */
30 void (*describe)(const struct key *key, struct seq_file *m); member
|
| /Linux-v5.10/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
|
| /Linux-v5.10/tools/perf/util/ |
| D | PERF-VERSION-GEN | 14 # First check if there is a .git to get the version from git describe
21 TAG=$(git describe --abbrev=0 --match "v[0-9].[0-9]*" 2>/dev/null )
|
| /Linux-v5.10/tools/power/cpupower/utils/ |
| D | version-gen.sh | 12 # First check if there is a .git to get the version from git describe
15 VN=$(git describe --abbrev=4 HEAD 2>/dev/null) &&
|
| /Linux-v5.10/security/keys/ |
| D | user_defined.c | 31 .describe = user_describe,
51 .describe = user_describe,
156 * describe the user key
|
| /Linux-v5.10/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
|
| /Linux-v5.10/include/linux/extcon/ |
| D | extcon-adc-jack.h | 28 * Note that you don't need to describe condition for "no cable attached"
50 * describe such delays with @handling_delay_ms, which
|
| /Linux-v5.10/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.
|
12345678910>>...31
