Home
last modified time | relevance | path

Searched full:interpret (Results 1 – 25 of 260) sorted by relevance

1234567891011

/Linux-v6.6/include/crypto/
Dsig.h113 * how to decode and interpret the encoded key and parameters
129 * how to decode and interpret the encoded key and parameters
Dakcipher.h96 * function, which knows how to decode and interpret
99 * function, which knows how to decode and interpret
462 * how to decode and interpret the encoded key and parameters
484 * how to decode and interpret the encoded key and parameters
/Linux-v6.6/Documentation/userspace-api/media/v4l/
Dext-ctrls-camera.rst54 is limited by the frame interval. Drivers should interpret the
68 terms of EV, drivers should interpret the values as 0.001 EV units,
132 interpret the values as arc seconds, with valid values between -180
138 should interpret the values as arc seconds, with valid values
338 Applications should interpret the values as standard ISO values
Dpixfmt-intro.rst9 interpret the same way. V4L2 includes several such formats, and this
/Linux-v6.6/Documentation/process/
Dcode-of-conduct-interpretation.rst10 community will interpret it. We also do not expect this interpretation
156 Because how we interpret and enforce the Code of Conduct will evolve over
/Linux-v6.6/drivers/gpu/drm/vboxvideo/
Dvboxvideo.h106 /* The value for port IO to let the adapter to interpret the adapter memory. */
109 /* The value for port IO to let the adapter to interpret the adapter memory. */
113 * The value for port IO to let the adapter to interpret the display memory.
/Linux-v6.6/drivers/staging/media/atomisp/pci/runtime/isys/interface/
Dia_css_isys_comm.h35 * communication channel to interpret that opaque handle(this handle is
/Linux-v6.6/arch/x86/platform/olpc/
Dolpc_dt.c189 if (olpc_ofw("interpret", args, res)) { in olpc_dt_interpret()
190 pr_err("olpc_dt: interpret failed!\n"); in olpc_dt_interpret()
/Linux-v6.6/Documentation/security/tpm/
Dtpm_event_log.rst24 to a challenger. However, PCR contents are difficult to interpret;
/Linux-v6.6/arch/x86/include/asm/
Duser.h40 * xstate_hdr bytes and interpret what states the processor/OS supports
/Linux-v6.6/arch/arm/include/asm/
Dkgdb.h69 * otherwise gdb will not be able to correctly interpret stepping over
/Linux-v6.6/arch/arm64/include/asm/
Dtraps.h86 /* Not a RAS error, we can't interpret the ESR. */ in arm64_ras_serror_get_severity()
/Linux-v6.6/arch/powerpc/platforms/embedded6xx/
Dstorcenter.c58 /* Interpret the "ranges" property */ in storcenter_add_bridge()
/Linux-v6.6/fs/smb/client/
Ddns_resolve.c59 /* Try to interpret hostname as an IPv4 or IPv6 address */ in dns_resolve_server_name_to_ip()
/Linux-v6.6/arch/sparc/kernel/
Didprom.c4 * interpret the data contained within.
/Linux-v6.6/Documentation/devicetree/bindings/i2c/
Di2c-pxa-pci-ce4100.txt26 in a way that the OS can interpret without
/Linux-v6.6/tools/testing/selftests/ftrace/test.d/dynevent/
Dtprobe_syntax_errors.tc74 # Explicitly use printf "%s" to not interpret \1
/Linux-v6.6/include/uapi/linux/
Dfsi.h14 * HW status information and interpret it themselves, so this
/Linux-v6.6/arch/x86/include/uapi/asm/
Dkvm_para.h42 /* The last 8 bits are used to indicate how to interpret the flags field
/Linux-v6.6/include/dt-bindings/clock/
Dtegra20-car.h9 * this issue. Implementations that interpret these clock IDs as bit values
/Linux-v6.6/arch/parisc/include/uapi/asm/
Dmman.h15 #define MAP_FIXED 0x04 /* Interpret addr exactly */
/Linux-v6.6/arch/alpha/include/uapi/asm/
Dmman.h15 #define MAP_FIXED 0x100 /* Interpret addr exactly */
/Linux-v6.6/include/uapi/asm-generic/
Dmman-common.h22 #define MAP_FIXED 0x10 /* Interpret addr exactly */
/Linux-v6.6/tools/include/uapi/asm-generic/
Dmman-common.h22 #define MAP_FIXED 0x10 /* Interpret addr exactly */
/Linux-v6.6/Documentation/filesystems/
Dntfs3.rst45 - This option informs the driver how to interpret path strings and

1234567891011