Searched full:descriptive (Results 1 – 25 of 60) sorted by relevance
123
| /Linux-v5.4/Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 23 # 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.4/drivers/hid/ |
| D | hid-uclogic-params.h | 39 * 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.4/Documentation/devicetree/bindings/input/ |
| D | matrix-keymap.txt | 20 for said properties are "linux,fn-keymap" or with another descriptive
|
| D | adc-keys.txt | 18 - label: Descriptive name of the key.
|
| D | gpio-keys-polled.txt | 15 - label: Descriptive name of the key.
|
| D | gpio-keys.txt | 16 - label: Descriptive name of the key.
|
| D | allwinner,sun4i-a10-lradc-keys.yaml | 38 description: Descriptive name of the key
|
| /Linux-v5.4/include/linux/platform_data/ |
| D | gpio-htc-egpio.h | 9 /* Descriptive values for all-in or all-out htc_egpio_chip descriptors. */
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 26 /label ... (r/o) descriptive, not necessarily unique
|
| /Linux-v5.4/samples/kdb/ |
| D | kdb_hello.c | 40 * 4: Descriptive text when you run help in kdb_hello_cmd_init()
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | anatop-regulator.txt | 5 - regulator-name: A string used as a descriptive name for regulator outputs
|
| D | regulator.yaml | 15 description: A string used as a descriptive name for regulator outputs
|
| /Linux-v5.4/include/rdma/ |
| D | tid_rdma_defs.h | 103 * to be more descriptive.
|
| /Linux-v5.4/include/linux/mtd/ |
| D | qinfo.h | 34 * @id_str - descriptive string to access the record
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | machine.rst | 52 The name field should be set to something that is usefully descriptive
|
| /Linux-v5.4/Documentation/input/ |
| D | userio.rst | 49 returned by the character device and a more descriptive error will be printed
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 43 is considered instructive, rather than descriptive. The reg property should
|
| /Linux-v5.4/Documentation/doc-guide/ |
| D | kernel-doc.rst | 144 #) 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.4/include/linux/ |
| D | ioc3.h | 57 char *name; /* descriptive submodule name */
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 65 to give each blob a descriptive name. For example:
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | setup.h | 98 * the file, and somewhat descriptive. The size is in bytes. Must be
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 35 name: Descriptive name that explains the command under test
|
| /Linux-v5.4/include/linux/iio/frequency/ |
| D | ad9523.h | 50 * @extended_name: Optional descriptive channel name.
|
| /Linux-v5.4/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 167 a descriptive name.
|
| /Linux-v5.4/drivers/gpio/ |
| D | gpiolib.h | 34 * @label: a descriptive name for the GPIO device, such as the part number
|
123
