Home
last modified time | relevance | path

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

/linux-5.19.10/Documentation/driver-api/
Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
/linux-5.19.10/Documentation/devicetree/bindings/interrupt-controller/
Dsifive,plic-1.0.0.yaml34 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
/linux-5.19.10/Documentation/usb/
Draw-gadget.rst10 any concrete USB functions itself but requires userspace to do that.
/linux-5.19.10/Documentation/filesystems/
Djournalling.rst176 The journalling layer uses typedefs to 'hide' the concrete definitions
/linux-5.19.10/Documentation/fb/
Dframebuffer.rst100 thus doesn't need to know, for example, how the color registers of the concrete
/linux-5.19.10/drivers/auxdisplay/
DKconfig42 your concrete display.
/linux-5.19.10/drivers/usb/gadget/legacy/
DKconfig524 implement any concrete USB functions itself but requires userspace
/linux-5.19.10/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-5.19.10/Documentation/trace/
Dhistogram.rst177 The examples below provide a more concrete illustration of the