Home
last modified time | relevance | path

Searched full:interpretation (Results 1 – 25 of 148) sorted by relevance

123456

/linux/Documentation/misc-devices/
H A Dad525x_dpot.rst10 interpretation of this settings is required by the end application according to
24 and may vary greatly on a part-by-part basis. For exact interpretation of
/linux/drivers/accel/amdxdna/
H A Damdxdna_ctx.h35 * Interpretation of the beginning of data payload for ERT_START_NPU in
46 * Interpretation of the beginning of data payload for ERT_CMD_CHAIN in
/linux/Documentation/userspace-api/
H A Dcheck_exec.rst118 Deny script interpretation if they are not executable, but allow
136 Deny script interpretation if they are not executable, and also deny
/linux/tools/perf/util/
H A Dsample-raw.c12 * specific interpretation.
/linux/drivers/scsi/libsas/
H A DKconfig27 bool "Support for SMP interpretation for SAS hosts"
/linux/Documentation/userspace-api/media/v4l/
H A Dfourcc.rst8 the pixel format, compression and colour space. The interpretation of the
H A Dmetafmt-uvc.rst18 timing information, required for precise interpretation of timestamps, contained
/linux/Documentation/translations/zh_TW/process/
H A Dindex.rst31 code-of-conduct-interpretation
H A Dcode-of-conduct-interpretation.rst5 :Original: :ref:`Documentation/process/code-of-conduct-interpretation.rst <code_of_conduct_interpre…
/linux/drivers/net/phy/
H A Dopen_alliance_helpers.h30 * of 1 meter, ranging from 0 to 31 meters. The exact interpretation of the
/linux/Documentation/translations/zh_CN/process/
H A Dcode-of-conduct-interpretation.rst3 :Original: :ref:`Documentation/process/code-of-conduct-interpretation.rst <code_of_conduct_interpre…
H A Dindex.rst30 code-of-conduct-interpretation
/linux/drivers/usb/serial/
H A Dkl5kusb105.h44 /* Interpretation of modem status lines */
/linux/Documentation/hwmon/
H A Dlm70.rst48 driver for interpretation. This driver makes use of the kernel's in-core
/linux/Documentation/translations/
H A Dindex.rst29 doubts about its interpretation. Additionally, some people prefer to read
/linux/include/linux/
H A Dcoresight-pmu.h49 * Interpretation of the PERF_RECORD_AUX_OUTPUT_HW_ID payload.
/linux/tools/include/linux/
H A Dcoresight-pmu.h49 * Interpretation of the PERF_RECORD_AUX_OUTPUT_HW_ID payload.
/linux/Documentation/netlabel/
H A Ddraft-ietf-cipso-ipsecurity-01.txt77 systems within a single Domain of Interpretation (DOI). A DOI is a
96 LENGTH INTERPRETATION
114 3.3 Domain of Interpretation Identifier
159 only be meaningful in certain Domains of Interpretation. For these tag
H A Dcipso_ipv4.rst47 Domain Of Interpretation (DOI) definition and are configured through the
/linux/Documentation/devicetree/bindings/hwmon/
H A Dti,tmp513.yaml62 See datasheet Table 11 for n-Factor range list and value interpretation.
/linux/Documentation/process/
H A Dcode-of-conduct.rst82 Interpretation chapter
/linux/arch/s390/kvm/
H A Dkvm-s390.h541 * Without SIGP interpretation, only SRS interpretation (if available) in kvm_s390_use_sca_entries()
574 * interpretation as well as adapter interruption forwarding.
/linux/Documentation/arch/arm64/
H A Dtagged-pointers.rst22 All interpretation of userspace memory addresses by the kernel assumes
/linux/drivers/hwtracing/coresight/
H A Dcoresight-syscfg.h92 * @type: type of owner - allows interpretation of owner_handle.
/linux/Documentation/devicetree/bindings/mtd/
H A Draw-nand-chip.yaml21 The interpretation of these parameters is implementation-defined, so

123456