Home
last modified time | relevance | path

Searched refs:skeleton (Results 1 – 25 of 25) sorted by relevance

/Linux-v5.4/samples/v4l/
Dv4l2-pci-skeleton.c64 struct skeleton { struct
133 struct skeleton *skel = dev_id; in skeleton_irq()
169 struct skeleton *skel = vb2_get_drv_priv(vq); in queue_setup()
198 struct skeleton *skel = vb2_get_drv_priv(vb->vb2_queue); in buffer_prepare()
217 struct skeleton *skel = vb2_get_drv_priv(vb->vb2_queue); in buffer_queue()
229 static void return_all_buffers(struct skeleton *skel, in return_all_buffers()
251 struct skeleton *skel = vb2_get_drv_priv(vq); in start_streaming()
274 struct skeleton *skel = vb2_get_drv_priv(vq); in stop_streaming()
304 struct skeleton *skel = video_drvdata(file); in skeleton_querycap()
319 static void skeleton_fill_pix_format(struct skeleton *skel, in skeleton_fill_pix_format()
[all …]
DMakefile2 obj-$(CONFIG_VIDEO_PCI_SKELETON) := v4l2-pci-skeleton.o
/Linux-v5.4/Documentation/driver-api/usb/
Dwriting_usb_driver.rst30 have written a generic USB driver skeleton, modelled after the
31 pci-skeleton.c file in the kernel source tree upon which many PCI
32 network drivers have been based. This USB skeleton can be found at
33 drivers/usb/usb-skeleton.c in the kernel source tree. In this article I
34 will walk through the basics of the skeleton driver, explaining the
54 structure. The skeleton driver declares a :c:type:`usb_driver` as::
57 .name = "skeleton",
80 this user-space interaction. The skeleton driver needs this kind of
150 In the skeleton driver, we determine what end points are marked as
291 This usb-skeleton driver does not have any examples of interrupt or
[all …]
Dpower-management.rst118 usblp, usblcd, and usb-skeleton (which doesn't count). If a
/Linux-v5.4/arch/m68k/fpsp040/
DMakefile12 x_unfl.o x_unimp.o x_unsupp.o bugfix.o skeleton.o
Dskeleton.S2 | skeleton.sa 3.2 4/26/91
25 | In the following skeleton code, some typical 'real_xxxx' handling
/Linux-v5.4/Documentation/media/kapi/
Dv4l2-intro.rst32 A good example to look at as a reference is the v4l2-pci-skeleton.c
33 source that is available in samples/v4l/. It is a skeleton driver for
/Linux-v5.4/arch/arc/boot/dts/
Dnsim_700.dts7 /include/ "skeleton.dtsi"
Dnsimosci.dts7 /include/ "skeleton.dtsi"
Daxc001.dtsi11 /include/ "skeleton.dtsi"
/Linux-v5.4/drivers/media/v4l2-core/
DKconfig41 Enable build of the skeleton PCI driver, used as a reference
/Linux-v5.4/Documentation/target/
Dtcm_mod_builder.rst10 fabric skeleton, by simply using::
21 using a skeleton struct target_core_fabric_ops API template.
/Linux-v5.4/arch/arm/boot/dts/
Dpxa27x.dtsi2 /* The pxa3xx skeleton simply augments the 2xx version */
Dpxa3xx.dtsi2 /* The pxa3xx skeleton simply augments the 2xx version */
/Linux-v5.4/Documentation/ia64/
Dmca.rst172 skeleton struct pt_regs and switch_stack to the original stack, fills
173 in the skeleton structures from the PAL minstate area and updates the
/Linux-v5.4/tools/perf/Documentation/
Dperf-script-python.txt210 with this minimalistic skeleton:
325 generate a skeleton script using 'perf script -g python' and modify the
418 trace data by generating a skeleton script using 'perf script -g
/Linux-v5.4/drivers/input/
DKconfig56 tristate "Polled input device skeleton"
/Linux-v5.4/arch/mips/boot/dts/cavium-octeon/
Docteon_3xxx.dts3 * OCTEON 3XXX, 5XXX, 63XX device tree skeleton.
Docteon_68xx.dts4 * OCTEON 68XX device tree skeleton.
/Linux-v5.4/Documentation/input/devices/
Dxpad.rst209 His useful info and both the usb-skeleton as well as the iforce input driver
/Linux-v5.4/arch/arc/
DKconfig534 Leaving it blank selects the minimal "skeleton" dtb
/Linux-v5.4/drivers/usb/gadget/legacy/
DKconfig35 Gadget Zero also works with the host-side "usb-skeleton" driver,
/Linux-v5.4/Documentation/crypto/
Ddescore-readme.txt43 and then move on to the common abstract skeleton with this one in mind.
/Linux-v5.4/Documentation/networking/
Dz8530drv.txt228 will print a skeleton z8530drv.conf for the OptoSCC to stdout.
/Linux-v5.4/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst1187 shows only the skeleton, how to build up the PCM interfaces.