Home
last modified time | relevance | path

Searched full:descriptive (Results 1 – 25 of 60) sorted by relevance

123

/Linux-v5.15/Documentation/devicetree/bindings/display/panel/
Dpanel-common.yaml23 # Descriptive Properties
43 non-descriptive information. For instance an LCD panel in a system that
45 inscribed on the system or used in a descriptive fashion in system
/Linux-v5.15/include/uapi/linux/
Dvfio_zdev.h20 * This capability provides a set of descriptive information about the
37 * This capability provides a set of descriptive information about the group of
/Linux-v5.15/drivers/hid/
Dhid-uclogic-params.h39 * Must use declarative (descriptive) language, not imperative, to simplify
70 * Must use declarative (descriptive) language, not imperative, to simplify
108 * Must use declarative (descriptive) language, not imperative, to simplify
/Linux-v5.15/include/linux/platform_data/
Dgpio-htc-egpio.h9 /* Descriptive values for all-in or all-out htc_egpio_chip descriptors. */
/Linux-v5.15/Documentation/ABI/obsolete/
Dsysfs-gpio28 /label ... (r/o) descriptive, not necessarily unique
/Linux-v5.15/Documentation/devicetree/bindings/input/
Dmatrix-keymap.yaml19 for said properties are "linux,fn-keymap" or with another descriptive
Dallwinner,sun4i-a10-lradc-keys.yaml40 description: Descriptive name of the key
Dgpio-keys.yaml33 description: Descriptive name of the key.
Dadc-keys.txt19 - label: Descriptive name of the key.
/Linux-v5.15/include/rdma/
Dtid_rdma_defs.h103 * to be more descriptive.
/Linux-v5.15/include/linux/mtd/
Dqinfo.h34 * @id_str - descriptive string to access the record
/Linux-v5.15/Documentation/power/regulator/
Dmachine.rst52 The name field should be set to something that is usefully descriptive
/Linux-v5.15/Documentation/input/
Duserio.rst49 returned by the character device and a more descriptive error will be printed
/Linux-v5.15/include/linux/gpio/
Dregmap.h22 * @label: (Optional) Descriptive name for GPIO controller.
/Linux-v5.15/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt43 is considered instructive, rather than descriptive. The reg property should
/Linux-v5.15/Documentation/doc-guide/
Dkernel-doc.rst144 #) The multi-line descriptive text you provide does *not* recognize
163 #) If the descriptive text you provide has lines that begin with
342 descriptive text and converted to proper reStructuredText markup and `Sphinx C
/Linux-v5.15/arch/x86/include/asm/
Dsetup.h112 * the file, and somewhat descriptive. The size is in bytes. Must be
/Linux-v5.15/Documentation/ABI/testing/
Dsysfs-firmware-qemu_fw_cfg67 to give each blob a descriptive name. For example::
/Linux-v5.15/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt35 name: Descriptive name that explains the command under test
/Linux-v5.15/include/linux/iio/frequency/
Dad9523.h50 * @extended_name: Optional descriptive channel name.
/Linux-v5.15/Documentation/devicetree/bindings/eeprom/
Dat24.yaml120 description: Descriptive name of the EEPROM.
/Linux-v5.15/Documentation/admin-guide/gpio/
Dsysfs.rst167 a descriptive name.
/Linux-v5.15/Documentation/trace/
Dmmiotrace.rst73 which action. It is recommended to place descriptive markers about what you
/Linux-v5.15/drivers/gpio/
Dgpiolib.h36 * @label: a descriptive name for the GPIO device, such as the part number
/Linux-v5.15/tools/perf/tests/
Dvmlinux-kallsyms.c190 * so use the short name, less descriptive but the same ("[kernel]" in in test__vmlinux_matches_kallsyms()

123