Searched full:describe (Results 1 – 25 of 913) sorted by relevance
12345678910>>...37
| /linux-6.12.1/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
|
| /linux-6.12.1/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-6.12.1/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)
439 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
451 * 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)
677 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
688 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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-6.12.1/scripts/ |
| D | setlocalversion | 70 desc=$(git describe --match=$tag 2>/dev/null)
79 desc=$(git describe --match=$tag 2>/dev/null)
85 desc=$(git describe --match=$tag 2>/dev/null)
115 # You cannot use 'git describe --dirty' because it tries to create
178 # signed tagged state (as git describe only looks at signed
|
| /linux-6.12.1/drivers/interconnect/imx/ |
| D | imx.h | 55 * struct imx_icc_node_adj - Describe a dynamic adjustable node
64 * struct imx_icc_node - Describe an interconnect node
79 * struct imx_icc_noc_setting - Describe an interconnect node setting
|
| /linux-6.12.1/drivers/pinctrl/renesas/ |
| D | sh_pfc.h | 118 * Describe a config register consisting of several fields of the same width
136 * Describe a config register consisting of several fields of different widths
191 * Describe a data register
209 * Describe the mapping from GPIOs to a single IRQ
349 * Describe generic pinmux data
356 * Describe a pinmux configuration without GPIO function that needs
365 * Describe a pinmux configuration with GPIO function that needs configuration
375 * Describe a pinmux configuration without GPIO function that needs
386 * Describe a pinmux configuration with GPIO function where the pinmux function
397 * Describe a pinmux configuration with GPIO function that needs configuration
[all …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/Documentation/process/ |
| D | submitting-patches.rst | 45 Describe your changes
48 Describe your problem. Whether your patch is a one-line bug fix or
54 Describe user-visible impact. Straight up crashes and lockups are
56 problem was spotted during code review, describe the impact you think
66 include numbers that back them up. But also describe non-obvious
69 different workloads. Describe the expected downsides of your
72 Once the problem is established, describe what you are actually doing
73 about it in technical detail. It's important to describe the change
94 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
623 be copied to the permanent changelog to describe this patch.
[all …]
|
| /linux-6.12.1/Documentation/translations/sp_SP/process/ |
| D | howto.rst | 91 describe lo que es necesario hacer para configurar y compilar el
100 Esto describe el estilo de código del kernel de Linux y algunas de los
107 Este archivo describe en gran detalle cómo crear con éxito y enviar un
126 Este archivo describe la lógica detrás de la decisión consciente de
144 Este documento describe cómo operan los maintainers del kernel de Linux
152 Este archivo describe las reglas sobre cómo se suceden las versiones
162 Una buena introducción que describe exactamente qué es un parche y cómo
202 También describe alguna información logística básica, como cómo compilar
211 Es un gran lugar para comenzar. Describe una lista de problemas
348 directorio principal del kernel describe cómo informar un posible bug del
|
| /linux-6.12.1/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-6.12.1/security/keys/ |
| D | user_defined.c | 31 .describe = user_describe,
51 .describe = user_describe,
156 * describe the user key
|
| /linux-6.12.1/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-6.12.1/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
|
| /linux-6.12.1/tools/include/uapi/linux/ |
| D | btf.h | 162 /* BTF_KIND_VAR is followed by a single "struct btf_var" to describe
170 * to describe all BTF_KIND_VAR types it contains along with it's
179 /* BTF_KIND_DECL_TAG is followed by a single "struct btf_decl_tag" to describe
|
| /linux-6.12.1/include/uapi/linux/ |
| D | btf.h | 162 /* BTF_KIND_VAR is followed by a single "struct btf_var" to describe
170 * to describe all BTF_KIND_VAR types it contains along with it's
179 /* BTF_KIND_DECL_TAG is followed by a single "struct btf_decl_tag" to describe
|
| /linux-6.12.1/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-6.12.1/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
|
| /linux-6.12.1/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
|
12345678910>>...37