Home
last modified time | relevance | path

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

/Linux-v6.1/Documentation/driver-api/
Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
/Linux-v6.1/Documentation/usb/
Draw-gadget.rst10 any concrete USB functions itself but requires userspace to do that.
/Linux-v6.1/Documentation/filesystems/
Djournalling.rst176 The journalling layer uses typedefs to 'hide' the concrete definitions
/Linux-v6.1/Documentation/fb/
Dframebuffer.rst100 thus doesn't need to know, for example, how the color registers of the concrete
/Linux-v6.1/drivers/auxdisplay/
DKconfig42 your concrete display.
/Linux-v6.1/drivers/usb/gadget/legacy/
DKconfig524 implement any concrete USB functions itself but requires userspace
/Linux-v6.1/drivers/net/ethernet/qlogic/qed/
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-v6.1/Documentation/trace/
Dhistogram.rst177 The examples below provide a more concrete illustration of the