Home
last modified time | relevance | path

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

1234

/linux-6.12.1/Documentation/filesystems/bcachefs/
Derrorcodes.rst27 Try to give error codes names that are as reasonably descriptive of the error
30 descriptive and useful error messages.
/linux-6.12.1/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-6.12.1/include/uapi/linux/
Dvfio_zdev.h20 * This capability provides a set of descriptive information about the
40 * This capability provides a set of descriptive information about the group of
/linux-6.12.1/drivers/hid/
Dhid-uclogic-params.h67 * Must use declarative (descriptive) language, not imperative, to simplify
111 * Must use declarative (descriptive) language, not imperative, to simplify
194 * Must use declarative (descriptive) language, not imperative, to simplify
/linux-6.12.1/Documentation/devicetree/bindings/hwmon/
Dhwmon-common.yaml14 description: A descriptive name for this device.
Dti,tmp421.yaml55 A descriptive name for this channel, like "ambient" or "psu".
Dti,tmp464.yaml54 A descriptive name for this channel, like "ambient" or "psu".
/linux-6.12.1/Documentation/devicetree/bindings/gpio/
Dgpio-pca9570.yaml32 description: A descriptive name for this device.
/linux-6.12.1/include/linux/
Daperture.h49 * @name: a descriptive name of the requesting driver
/linux-6.12.1/include/linux/platform_data/
Dgpio-htc-egpio.h9 /* Descriptive values for all-in or all-out htc_egpio_chip descriptors. */
/linux-6.12.1/Documentation/ABI/obsolete/
Dsysfs-gpio28 /label ... (r/o) descriptive, not necessarily unique
/linux-6.12.1/Documentation/devicetree/bindings/input/
Dmatrix-keymap.yaml19 for said properties are "linux,fn-keymap" or with another descriptive
Dallwinner,sun4i-a10-lradc-keys.yaml54 description: Descriptive name of the key
/linux-6.12.1/include/rdma/
Dtid_rdma_defs.h103 * to be more descriptive.
/linux-6.12.1/Documentation/devicetree/bindings/spi/
Dspi-cadence.yaml56 description: Descriptive name of the SPI controller.
/linux-6.12.1/include/linux/mtd/
Dqinfo.h34 * @id_str - descriptive string to access the record
/linux-6.12.1/Documentation/power/regulator/
Dmachine.rst52 The name field should be set to something that is usefully descriptive
/linux-6.12.1/Documentation/input/
Duserio.rst49 returned by the character device and a more descriptive error will be printed
/linux-6.12.1/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt43 is considered instructive, rather than descriptive. The reg property should
/linux-6.12.1/include/linux/gpio/
Dregmap.h22 * @label: (Optional) Descriptive name for GPIO controller.
/linux-6.12.1/drivers/platform/x86/hp/hp-bioscfg/
Denum-attributes.c318 * user nane is generated to make the name more descriptive in hp_populate_enumeration_package_data()
418 * user nane is generated to make the name more descriptive in hp_populate_enumeration_buffer_data()
/linux-6.12.1/drivers/video/
Daperture.c277 * @name: a descriptive name of the requesting driver
338 * @name: a descriptive name of the requesting driver
/linux-6.12.1/Documentation/doc-guide/
Dkernel-doc.rst150 #) The multi-line descriptive text you provide does *not* recognize
169 #) If the descriptive text you provide has lines that begin with
393 descriptive text and converted to proper reStructuredText markup and `Sphinx C
/linux-6.12.1/tools/testing/selftests/net/tcp_ao/lib/
Dkconfig.c86 * anything more descriptive. Oh well. in has_tcp_md5()
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-firmware-qemu_fw_cfg68 to give each blob a descriptive name. For example::

1234