Searched full:descriptive (Results 1 – 25 of 67) sorted by relevance
123
| /Linux-v6.1/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-v6.1/include/uapi/linux/ |
| D | vfio_zdev.h | 20 * This capability provides a set of descriptive information about the
40 * This capability provides a set of descriptive information about the group of
|
| /Linux-v6.1/drivers/hid/ |
| D | hid-uclogic-params.h | 63 * Must use declarative (descriptive) language, not imperative, to simplify
107 * Must use declarative (descriptive) language, not imperative, to simplify
179 * Must use declarative (descriptive) language, not imperative, to simplify
|
| /Linux-v6.1/include/linux/ |
| D | aperture.h | 43 * @name: a descriptive name of the requesting driver
|
| /Linux-v6.1/include/linux/platform_data/ |
| D | gpio-htc-egpio.h | 9 /* Descriptive values for all-in or all-out htc_egpio_chip descriptors. */
|
| /Linux-v6.1/Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 28 /label ... (r/o) descriptive, not necessarily unique
|
| /Linux-v6.1/Documentation/devicetree/bindings/input/ |
| D | matrix-keymap.yaml | 19 for said properties are "linux,fn-keymap" or with another descriptive
|
| D | allwinner,sun4i-a10-lradc-keys.yaml | 51 description: Descriptive name of the key
|
| D | gpio-keys.yaml | 37 description: Descriptive name of the key.
|
| /Linux-v6.1/include/rdma/ |
| D | tid_rdma_defs.h | 103 * to be more descriptive.
|
| /Linux-v6.1/Documentation/devicetree/bindings/hwmon/ |
| D | ti,tmp421.yaml | 55 A descriptive name for this channel, like "ambient" or "psu".
|
| D | ti,tmp464.yaml | 54 A descriptive name for this channel, like "ambient" or "psu".
|
| D | national,lm90.yaml | 84 description: A descriptive name for this channel, like "ambient" or "psu".
|
| /Linux-v6.1/include/linux/mtd/ |
| D | qinfo.h | 34 * @id_str - descriptive string to access the record
|
| /Linux-v6.1/drivers/video/ |
| D | aperture.c | 278 * @name: a descriptive name of the requesting driver
316 * @name: a descriptive name of the requesting driver
|
| /Linux-v6.1/Documentation/power/regulator/ |
| D | machine.rst | 52 The name field should be set to something that is usefully descriptive
|
| /Linux-v6.1/include/linux/gpio/ |
| D | regmap.h | 22 * @label: (Optional) Descriptive name for GPIO controller.
|
| /Linux-v6.1/Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 43 is considered instructive, rather than descriptive. The reg property should
|
| /Linux-v6.1/Documentation/input/ |
| D | userio.rst | 49 returned by the character device and a more descriptive error will be printed
|
| /Linux-v6.1/Documentation/doc-guide/ |
| D | kernel-doc.rst | 150 #) The multi-line descriptive text you provide does *not* recognize
169 #) If the descriptive text you provide has lines that begin with
348 descriptive text and converted to proper reStructuredText markup and `Sphinx C
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 68 to give each blob a descriptive name. For example::
|
| /Linux-v6.1/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 35 name: Descriptive name that explains the command under test
|
| /Linux-v6.1/include/linux/iio/frequency/ |
| D | ad9523.h | 50 * @extended_name: Optional descriptive channel name.
|
| /Linux-v6.1/Documentation/devicetree/bindings/eeprom/ |
| D | at24.yaml | 129 description: Descriptive name of the EEPROM.
|
| /Linux-v6.1/Documentation/process/ |
| D | maintainer-tip.rst | 548 usage of descriptive function names often replaces these tiny comments.
672 Either use proper defines which have descriptive names or consider using
775 can have shorter descriptive names - our primary concern is greppability
|
123
