Home
last modified time | relevance | path

Searched refs:concrete (Results 1 – 12 of 12) sorted by relevance

/linux-6.15/Documentation/driver-api/
H A Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
/linux-6.15/tools/perf/Documentation/
H A Dcpu-and-latency-overheads.txt13 which one is useful in a concrete situation at hand. For example, the former
/linux-6.15/Documentation/usb/
H A Draw-gadget.rst10 any concrete USB functions itself but requires userspace to do that.
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
H A Dsifive,plic-1.0.0.yaml39 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
/linux-6.15/Documentation/filesystems/
H A Djournalling.rst174 The journalling layer uses typedefs to 'hide' the concrete definitions
/linux-6.15/Documentation/security/
H A Dsnp-tdx-threat-model.rst44 While the concrete implementation details differ between technologies, all
/linux-6.15/Documentation/fb/
H A Dframebuffer.rst100 thus doesn't need to know, for example, how the color registers of the concrete
/linux-6.15/Documentation/process/
H A Dbackporting.rst537 One concrete example of this was a pair of patches to the system call
600 For a more concrete example, see this video tutorial where two patches
/linux-6.15/drivers/usb/gadget/legacy/
H A DKconfig524 implement any concrete USB functions itself but requires userspace
/linux-6.15/drivers/auxdisplay/
H A DKconfig39 your concrete display.
/linux-6.15/drivers/net/ethernet/qlogic/qed/
H A Dqed_sriov.c431 u32 concrete; in qed_iov_setup_vfdb() local
449 concrete = qed_vfid_to_concrete(p_hwfn, vf->abs_vf_id); in qed_iov_setup_vfdb()
450 vf->concrete_fid = concrete; in qed_iov_setup_vfdb()
/linux-6.15/Documentation/trace/
H A Dhistogram.rst186 The examples below provide a more concrete illustration of the