Home
last modified time | relevance | path

Searched refs:exported (Results 1 – 14 of 14) sorted by relevance

/drivers/usb/usbip/
Dusbip_protocol.txt5 USB devices and the clients imports them. The device driver for the exported
8 The client may ask for the list of the exported USB devices. To get the list the
12 the OP_REP_DEVLIST packet which lists the exported USB devices. Finally the
26 Once the client knows the list of exported USB devices it may decide to use one
91 OP_REQ_DEVLIST: Retrieve the list of exported USB devices.
97 2 | 2 | 0x8005 | Command code: Retrieve the list of exported USB
102 OP_REP_DEVLIST: Reply with the list of exported USB devices.
108 2 | 2 | 0x0005 | Reply code: The list of exported USB devices.
112 8 | 4 | n | Number of exported devices: 0 means no exported
115 0x0C | | | From now on the exported n devices are described,
[all …]
/drivers/gpio/
Dgpiolib-sysfs.c545 if (!chip || !chip->exported) { in gpiod_export()
765 chip->exported = (status == 0); in gpiochip_export()
787 chip->exported = false; in gpiochip_unexport()
822 if (chip->exported) in gpiolib_sysfs_init()
DKconfig87 exported to userspace; this can be useful when debugging.
/drivers/firmware/google/
DKconfig28 the EBDA on Google servers. If found, this log is exported to
/drivers/scsi/aic7xxx/aicasm/
Daicasm_symbol.h103 int exported; member
Daicasm_symbol.c524 if (cursym->info.linfo->exported == 0) in symtable_dump()
Daicasm_gram.y1049 $2->info.linfo->exported = $1;
/drivers/gpu/drm/
DREADME.drm25 that rely extensively on the API exported by the DRM module.
/drivers/misc/
DKconfig406 bool "UID based statistics tracking exported to /proc/uid_stat"
526 Per UID based cpu time statistics exported to /proc/uid_cputime
527 Per UID based io statistics exported to /proc/uid_io
534 Per TASK based io statistics exported to /proc/uid_io
540 Memory time statistics exported to /sys/kernel/memory_state_time
/drivers/staging/speakup/
DTODO25 functions should get exported from drivers/char/selection.c (clear_selection
/drivers/tty/hvc/
DKconfig120 will depend on arch specific APIs exported from hvcserver.ko
/drivers/firmware/
DKconfig14 BIOS tries boot from. This information is then exported via sysfs.
/drivers/net/
DKconfig175 at runtime through a userspace interface exported using configfs.
321 devices exported by a Xen network driver domain (often
/drivers/block/
DKconfig291 block devices, i.e. it will be able to use block devices exported by