Home
last modified time | relevance | path

Searched refs:chardev (Results 1 – 13 of 13) sorted by relevance

/Linux-v5.4/tools/virtio/virtio-trace/
DREADME59 -chardev pipe,id=charchannel0,path=/tmp/virtio-trace/agent-ctl-path\
60 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,\
63 -chardev pipe,id=charchannel1,path=/tmp/virtio-trace/trace-path-cpu0\
64 -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,\
82 Here, chardev names are restricted to trace-path-cpuX and agent-ctl-path. For
83 example, if a guest use three CPUs, chardev names should be trace-path-cpu0,
87 You can find some chardev in /dev/virtio-ports/ in the guest.
109 the guest will stop by specification of chardev in QEMU. This blocking mode may
/Linux-v5.4/tools/testing/selftests/gpio/
D.gitignore1 gpio-mockup-chardev
DMakefile14 TEST_PROGS_EXTENDED := gpio-mockup-chardev
Dgpio-mockup.sh89 $BASE/gpio-mockup-chardev $*
/Linux-v5.4/Documentation/media/uapi/rc/
Dlirc-write.rst57 the chardev is a pulse/space sequence of integer values. Pulses and spaces
65 ``struct lirc_scancode`` must be written to the chardev at a time, else
Dlirc-read.rst60 read from the chardev.
Dlirc-dev-intro.rst18 data between userspace and kernelspace. Fundamentally, it is just a chardev
33 What you should see for a chardev:
/Linux-v5.4/drivers/scsi/cxlflash/
Dcommon.h121 struct device *chardev; member
Dmain.c936 device_unregister(cfg->chardev); in cxlflash_release_chrdev()
937 cfg->chardev = NULL; in cxlflash_release_chrdev()
3638 cfg->chardev = char_dev; in init_chrdev()
/Linux-v5.4/drivers/misc/cxl/
Dfile.c565 struct device **chardev, char *postfix, char *desc, in cxl_add_chardev() argument
585 *chardev = dev; in cxl_add_chardev()
/Linux-v5.4/Documentation/
Dnommu-mmap.txt97 (#) Memory backed chardev, MAP_SHARED, PROT_READ / PROT_EXEC / PROT_WRITE
177 support futexes (such as an I/O chardev mapping).
220 The vm_ops->close() routine will be invoked when the last mapping on a chardev
/Linux-v5.4/Documentation/driver-api/usb/
Dhotplug.rst137 if using the usb chardev framework:
/Linux-v5.4/Documentation/powerpc/
Dcxl.rst461 most logical chardev to use in any programming mode (afuX.Yd for