Searched full:descriptive (Results 1 – 21 of 21) sorted by relevance
| /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
|
| /Documentation/devicetree/bindings/input/ |
| D | adc-keys.txt | 18 - label: Descriptive name of the key.
|
| D | matrix-keymap.yaml | 19 for said properties are "linux,fn-keymap" or with another descriptive
|
| D | allwinner,sun4i-a10-lradc-keys.yaml | 38 description: Descriptive name of the key
|
| D | gpio-keys.yaml | 33 description: Descriptive name of the key.
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 28 /label ... (r/o) descriptive, not necessarily unique
|
| /Documentation/power/regulator/ |
| D | machine.rst | 52 The name field should be set to something that is usefully descriptive
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 43 is considered instructive, rather than descriptive. The reg property should
|
| /Documentation/input/ |
| D | userio.rst | 49 returned by the character device and a more descriptive error will be printed
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 67 to give each blob a descriptive name. For example::
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at24.yaml | 118 description: Descriptive name of the EEPROM.
|
| /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
|
| /Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 167 a descriptive name.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 15 description: A string used as a descriptive name for regulator outputs
|
| /Documentation/trace/ |
| D | mmiotrace.rst | 73 which action. It is recommended to place descriptive markers about what you
|
| /Documentation/process/ |
| D | coding-style.rst | 298 HOWEVER, while mixed-case names are frowned upon, descriptive names for
303 have descriptive names, as do global functions. If you have a function
444 descriptive names (you can ask the compiler to in-line them if you think
|
| D | submitting-patches.rst | 606 succinct and descriptive, but that is what a well-written summary
646 well as descriptive.
|
| /Documentation/driver-api/media/ |
| D | v4l2-dev.rst | 45 - :c:type:`video_device`->name: set to something descriptive and unique.
|
| /Documentation/devicetree/bindings/arm/ |
| D | idle-states.yaml | 318 A string used as a descriptive name for the idle state.
|
| /Documentation/driver-api/gpio/ |
| D | legacy.rst | 759 a descriptive name.
|
| /Documentation/driver-api/ |
| D | pinctl.rst | 503 As already described above, pin groups are in turn self-descriptive, so
|