Searched full:appear (Results 1 – 25 of 2481) sorted by relevance
12345678910>>...100
| /kernel/linux/linux-5.10/arch/arm/include/uapi/asm/ |
| D | byteorder.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| D | swab.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| /kernel/linux/linux-4.19/arch/arm/include/uapi/asm/ |
| D | byteorder.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| D | swab.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| /kernel/linux/linux-4.19/arch/arm/include/asm/ |
| D | swab.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | swab.h | 6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
|
| /kernel/linux/linux-4.19/Documentation/filesystems/configfs/ |
| D | configfs.txt | 21 appear in sysfs, allowing userspace to read the attributes via
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
47 subsystems. Once a client subsystem is loaded, it will appear as a
52 appear at this time. readdir(3) can determine what the attributes are,
167 By itself, a config_item cannot do much more than appear in configfs.
205 When a config_item wants an attribute to appear as a file in the item's
209 attribute file will appear with the configfs_attribute->ca_name
226 appear as the contents of a file in the item's configfs directory.
229 attribute file will appear with the configfs_bin_attribute->cb_attr.ca_name
325 tells configfs to make the subsystem appear in the file tree.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | configfs.rst | 23 appear in sysfs, allowing userspace to read the attributes via
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
50 subsystems. Once a client subsystem is loaded, it will appear as a
55 appear at this time. readdir(3) can determine what the attributes are,
175 By itself, a config_item cannot do much more than appear in configfs.
219 When a config_item wants an attribute to appear as a file in the item's
223 attribute file will appear with the configfs_attribute->ca_name
243 appear as the contents of a file in the item's configfs directory.
246 attribute file will appear with the configfs_bin_attribute->cb_attr.ca_name
346 tells configfs to make the subsystem appear in the file tree::
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/stable/ |
| D | sysfs-driver-aspeed-vuart | 5 will appear on the host <-> BMC LPC bus.
13 the UART will appear on the host <-> BMC LPC bus.
|
| /kernel/linux/linux-4.19/arch/unicore32/include/uapi/asm/ |
| D | byteorder.h | 14 * that byte accesses appear as:
16 * and word accesses (data or instruction) appear as:
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-driver-aspeed-vuart | 5 will appear on the host <-> BMC LPC bus.
13 the UART will appear on the host <-> BMC LPC bus.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ptp/ |
| D | timestamper.txt | 41 appear on time stamp channel 0 (zero), and those from phy@2 appear on
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_modeset_helper.h | 6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
|
| D | drm_blend.h | 6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
|
| /kernel/linux/linux-4.19/include/drm/ |
| D | drm_modeset_helper.h | 6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
|
| D | drm_blend.h | 6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
|
| D | drm_color_mgmt.h | 6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
|
| /kernel/linux/linux-5.10/include/asm-generic/bitops/ |
| D | instrumented-non-atomic.h | 91 * can appear to succeed but actually fail.
105 * can appear to succeed but actually fail.
119 * can appear to succeed but actually fail.
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | coda.h | 33 notice and this permission notice appear in all copies of the
35 thereof, and that both notices appear in supporting documentation, and
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | coda.h | 33 notice and this permission notice appear in all copies of the
35 thereof, and that both notices appear in supporting documentation, and
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | cm3xxx.h | 26 * These registers appear once per CM module.
38 * These register offsets generally appear in more than one PRCM submodule.
|
| /kernel/linux/linux-4.19/arch/arm/mach-omap2/ |
| D | cm3xxx.h | 29 * These registers appear once per CM module.
41 * These register offsets generally appear in more than one PRCM submodule.
|
| /kernel/linux/linux-4.19/include/acpi/ |
| D | acnames.h | 13 /* Method names - these methods can appear anywhere in the namespace */
43 /* Method names - these methods must appear at the namespace root */
|
| /kernel/linux/linux-5.10/include/acpi/ |
| D | acnames.h | 13 /* Method names - these methods can appear anywhere in the namespace */
43 /* Method names - these methods must appear at the namespace root */
|
| /kernel/linux/linux-4.19/Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 50 appear as any other I2C bus to the system and makes it possible to connect
55 GPIO hammering (bitbang). It will appear as any other SPI bus on the system
84 bus, data and clock line, by bit banging two GPIO lines. It will appear as
|
12345678910>>...100