Searched full:describe (Results 1 – 25 of 1451) sorted by relevance
12345678910>>...59
| /kernel/liteos_a/ |
| D | OAT.xml | 37 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
38 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
42 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
43 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
47 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
48 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
52 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
53 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
57 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
58 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
[all …]
|
| /kernel/liteos_m/ |
| D | OAT.xml | 39 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
40 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
44 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
45 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
49 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
50 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
54 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
55 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
59 …<!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan result…
60 …<!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering sc…
[all …]
|
| /kernel/linux/linux-4.19/drivers/android/ |
| D | binder_alloc.h | 34 * @allow_user_free: describe the second member of struct blah,
35 * @async_transaction: describe the second member of struct blah,
36 * @debug_id: describe the second member of struct blah,
37 * @transaction: describe the second member of struct blah,
38 * @target_node: describe the second member of struct blah,
39 * @data_size: describe the second member of struct blah,
40 * @offsets_size: describe the second member of struct blah,
41 * @extra_buffers_size: describe the second member of struct blah,
42 * @data:i describe the second member of struct blah,
|
| /kernel/linux/linux-4.19/Documentation/PCI/ |
| D | acpi-info.txt | 3 The general rule is that the ACPI namespace should describe everything the
7 host bridges, so the ACPI namespace must describe each host bridge, the
15 devices and read and size their BARs. However, ACPI may describe PCI
18 controllers and a _PRT is needed to describe those connections.
41 describe all the address space they consume. This includes all the windows
45 range below the bridge, window registers that describe the apertures, etc.
60 Consumer/Producer meant there was no way to describe bridge registers in
61 the PNP0A03/PNP0A08 device itself. The workaround was to describe the
72 describe bridge registers this way on those architectures.
88 The MCFG table must describe the ECAM space of non-hot pluggable host
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/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>
|
| /kernel/linux/linux-5.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>
|
| /kernel/linux/linux-4.19/drivers/scsi/pm8001/ |
| D | pm8001_hwi.h | 155 * use to describe enable the phy (64 bytes)
218 * use to describe the sata task response (64 bytes)
243 * use to describe MPI REGISTER DEVICE Command (64 bytes)
296 * use to describe MPI Local Phy Control Response (64 bytes)
381 * use to describe MPI General Event Notification Response (64 bytes)
394 * use to describe MPI SMP REQUEST Command (64 bytes)
420 * use to describe MPI SMP Completion Response (64 bytes)
431 * use to describe MPI SSP SMP & SATA Abort Command (64 bytes)
448 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
460 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
|
| D | pm80xx_hwi.h | 344 * use to describe enable the phy (128 bytes)
406 * use to describe the sata task response (64 bytes)
440 * use to describe MPI REGISTER DEVICE Command (64 bytes)
488 * use to describe MPI Local Phy Control Response (64 bytes)
610 * use to describe MPI General Event Notification Response (64 bytes)
622 * use to describe MPI SMP REQUEST Command (64 bytes)
649 * use to describe MPI SMP Completion Response (64 bytes)
660 * 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 …]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/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
198 EV_ABS events describe absolute changes in a property. For example, a touchpad
205 - Used to describe the distance of a tool from an interaction surface. This
217 - Used to describe multitouch input events. Please see
223 EV_SW events describe stateful binary switches. For example, the SW_LID code is
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-4.19/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.
111 name describe the pin function and group hierarchy.
117 4. The gpio controller must be describe in the pinctrl simple-bus.
|
| /kernel/linux/linux-4.19/drivers/pinctrl/sh-pfc/ |
| D | sh_pfc.h | 60 * VIN_DATA_PIN_GROUP() is a macro used to describe the VIN pin groups
107 * Describe a config register consisting of several fields of the same width
121 * Describe a config register consisting of several fields of different widths
174 * Describe a data register
190 * Describe the mapping from GPIOs to a single IRQ
316 * Describe generic pinmux data
323 * Describe a pinmux configuration without GPIO function that needs
332 * Describe a pinmux configuration with GPIO function that needs configuration
342 * Describe a pinmux configuration without GPIO function that needs
353 * Describe a pinmux configuration with GPIO function where the pinmux function
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 9 The target of device tree thermal descriptors is to describe only
14 There are five types of nodes involved to describe thermal bindings:
18 - trip points: describe key temperatures at which cooling is recommended. The
20 - cooling maps: used to describe links between trip points and cooling devices;
21 - thermal zones: used to describe thermal data within the hardware;
73 The trip node is a node to describe a point in the temperature domain
95 The cooling device maps node is a node to describe how cooling devices
143 Type: sub-node required to describe the thermal zone.
146 Type: sub-node map nodes, used to describe the relation between trips
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | submitting-patches.rst | 21 Many of these steps describe the default behavior of the ``git`` version
102 2) Describe your changes
105 Describe your problem. Whether your patch is a one-line bug fix or
111 Describe user-visible impact. Straight up crashes and lockups are
113 problem was spotted during code review, describe the impact you think
123 include numbers that back them up. But also describe non-obvious
126 different workloads. Describe the expected downsides of your
129 Once the problem is established, describe what you are actually doing
130 about it in technical detail. It's important to describe the change
151 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
[all …]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/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
|
12345678910>>...59