| /linux-4.4.14/drivers/input/joystick/ |
| H A D | interact.c | 53 struct interact { struct
130 struct interact *interact = gameport_get_drvdata(gameport); interact_poll() local
131 struct input_dev *dev = interact->dev; interact_poll()
135 interact->reads++; interact_poll()
137 if (interact_read_packet(interact->gameport, interact->length, data) < interact->length) { interact_poll()
138 interact->bads++; interact_poll()
142 data[i] <<= INTERACT_MAX_LENGTH - interact->length; interact_poll()
144 switch (interact->type) { interact_poll()
185 struct interact *interact = input_get_drvdata(dev); interact_open() local
187 gameport_start_polling(interact->gameport); interact_open()
197 struct interact *interact = input_get_drvdata(dev); interact_close() local
199 gameport_stop_polling(interact->gameport); interact_close()
208 struct interact *interact; interact_connect() local
214 interact = kzalloc(sizeof(struct interact), GFP_KERNEL); interact_connect()
216 if (!interact || !input_dev) { interact_connect()
221 interact->gameport = gameport; interact_connect()
222 interact->dev = input_dev; interact_connect()
224 gameport_set_drvdata(gameport, interact); interact_connect()
242 printk(KERN_WARNING "interact.c: Unknown joystick on %s. [len %d d0 %08x d1 %08x i2 %08x]\n", interact_connect()
251 snprintf(interact->phys, sizeof(interact->phys), "%s/input0", gameport->phys); interact_connect()
253 interact->type = i; interact_connect()
254 interact->length = interact_type[i].length; interact_connect()
257 input_dev->phys = interact->phys; interact_connect()
264 input_set_drvdata(input_dev, interact); interact_connect()
271 for (i = 0; (t = interact_type[interact->type].abs[i]) >= 0; i++) { interact_connect()
272 if (i < interact_type[interact->type].b8) interact_connect()
278 for (i = 0; (t = interact_type[interact->type].btn[i]) >= 0; i++) interact_connect()
281 err = input_register_device(interact->dev); interact_connect()
290 kfree(interact); interact_connect()
296 struct interact *interact = gameport_get_drvdata(gameport); interact_disconnect() local
298 input_unregister_device(interact->dev); interact_disconnect()
301 kfree(interact); interact_disconnect()
306 .name = "interact",
|
| /linux-4.4.14/drivers/media/usb/pvrusb2/ |
| H A D | pvrusb2-cs53l32a.h | 30 interact through the interface provided by pvrusb2-hdw.h.
|
| H A D | pvrusb2-cx2584x-v4l.h | 30 should only interact through the interface provided by
|
| H A D | pvrusb2-video-v4l.h | 30 interact through the interface provided by pvrusb2-hdw.h.
|
| H A D | pvrusb2-wm8775.h | 30 driver; higher level code should only interact through the
|
| /linux-4.4.14/include/acpi/ |
| H A D | cppc_acpi.h | 133 /* Methods to interact with the PCC mailbox controller. */
|
| /linux-4.4.14/arch/powerpc/platforms/cell/ |
| H A D | spu_callbacks.c | 21 * 1. They interact with the way SPU syscalls are handled
|
| /linux-4.4.14/tools/include/linux/ |
| H A D | compiler.h | 107 * mutilate accesses that either do not require ordering or that interact
|
| /linux-4.4.14/drivers/scsi/bfa/ |
| H A D | bfa_modules.h | 92 * Structure used to interact between different BFA sub modules
|
| /linux-4.4.14/drivers/misc/vmw_vmci/ |
| H A D | vmci_context.h | 123 * to interact. If one of them is restricted, the other one must
|
| H A D | vmci_context.c | 229 * interact. ctx_fire_notification()
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/mvm/ |
| H A D | fw-api-tof.h | 210 * 0 Initiator interact with regular AP
211 * 1 Initiator interact with Responder machine: need to send the
|
| /linux-4.4.14/include/linux/ |
| H A D | compiler.h | 272 * mutilate accesses that either do not require ordering or that interact
504 * mutilate accesses that either do not require ordering or that interact
|
| H A D | vmw_vmci_defs.h | 310 * allowed to interact with the hypervisor and trusted entities.
|
| H A D | kernel.h | 530 * file, which gives a means for the kernel and userspace to interact.
|
| /linux-4.4.14/drivers/misc/sgi-xp/ |
| H A D | xp_main.c | 12 * XP provides a base from which its users can interact
|
| /linux-4.4.14/drivers/net/irda/ |
| H A D | irda-usb.h | 57 * in term of latency and will interact with the link management in IrLAP...
|
| /linux-4.4.14/drivers/mfd/ |
| H A D | wm831x-irq.c | 453 * we can interact with the device over I2C or SPI. */ wm831x_irq_thread()
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/ |
| H A D | iwl-op-mode.h | 110 * interact with it. The driver layer typically calls the start and stop
|
| /linux-4.4.14/drivers/net/ethernet/dlink/ |
| H A D | dl2k.h | 45 Unlike software-only systems, device drivers interact with complex hardware.
|
| H A D | sundance.c | 236 Unlike software-only systems, device drivers interact with complex hardware.
|
| /linux-4.4.14/drivers/gpu/drm/radeon/ |
| H A D | radeon_acpi.h | 38 * ATIF provides an entry point for the gfx driver to interact with the sbios.
|
| /linux-4.4.14/drivers/gpu/drm/amd/amdgpu/ |
| H A D | amdgpu_acpi.h | 38 * ATIF provides an entry point for the gfx driver to interact with the sbios.
|
| /linux-4.4.14/drivers/usb/chipidea/ |
| H A D | otg_fsm.c | 33 /* Add for otg: interact with user space app */
|
| /linux-4.4.14/drivers/gpu/drm/i915/ |
| H A D | intel_audio.c | 54 * The struct i915_audio_component is used to interact between the graphics
|
| /linux-4.4.14/arch/mips/include/asm/octeon/ |
| H A D | cvmx-cmd-queue.h | 45 * Even though most software will never directly interact with
|
| /linux-4.4.14/net/irda/irnet/ |
| H A D | irnet.h | 406 /* "pppd" interact directly with us on a /dev/ file */
|
| /linux-4.4.14/include/linux/spi/ |
| H A D | spi.h | 233 * interact with the hardware at the other end of a SPI link. It's called
563 /* Calls the driver make to interact with the message queue */
|
| /linux-4.4.14/drivers/scsi/ |
| H A D | aha1542.c | 872 * We need to do this too before the 1542 can interact with aha1542_reset()
|
| /linux-4.4.14/drivers/block/ |
| H A D | xsysace.c | 35 * request function need to interact with the hardware, then they
|
| /linux-4.4.14/include/xen/interface/ |
| H A D | xen.h | 486 * consistent set of values. The correct way to interact with
|
| /linux-4.4.14/arch/arm/mach-omap2/ |
| H A D | omap_hwmod.h | 276 * interface to interact with the hwmod. Used to add sleep dependencies
|
| /linux-4.4.14/drivers/base/regmap/ |
| H A D | regmap.c | 2604 * useful for devices with a cache which do not need to interact with
2665 * useful for devices with a cache which do not need to interact with
|
| /linux-4.4.14/drivers/staging/lustre/lustre/llite/ |
| H A D | llite_internal.h | 1207 * In fact, one dentry should has only one chance to interact with the d_need_statahead()
|
| /linux-4.4.14/block/ |
| H A D | blk-throttle.c | 368 * Limits of a group don't interact with limits of other groups throtl_pd_init()
|
| /linux-4.4.14/kernel/ |
| H A D | exit.c | 1404 * is used and the two don't interact with each other. wait_consider_task()
|
| H A D | signal.c | 1842 * for the two don't interact with each other. Notify
|
| /linux-4.4.14/kernel/trace/ |
| H A D | trace.h | 362 * struct tracer - a specific tracer and its callbacks to interact with tracefs
|
| H A D | ftrace.c | 137 * are simply leaked, so there is no need to interact with a grace-period
|
| /linux-4.4.14/drivers/usb/gadget/udc/ |
| H A D | pxa25x_udc.c | 70 * by the host to interact with this device, and allocates endpoints to
|
| H A D | pxa27x_udc.c | 45 * by the host to interact with this device, and allocates endpoints to
|
| /linux-4.4.14/drivers/tty/hvc/ |
| H A D | hvcs.c | 1314 * NOTE: This is almost always from_user since user level apps interact with the
|
| /linux-4.4.14/drivers/scsi/libfc/ |
| H A D | fc_rport.c | 25 * There should be no other places in libfc that interact directly with the
|
| /linux-4.4.14/drivers/scsi/bnx2fc/ |
| H A D | bnx2fc_hwi.c | 2 * This file contains the code that low level functions that interact
|
| /linux-4.4.14/drivers/net/ethernet/adaptec/ |
| H A D | starfire.c | 304 Unlike software-only systems, device drivers interact with complex hardware.
|
| /linux-4.4.14/net/irda/ |
| H A D | irlap_event.c | 489 * 2.95 sec) and to see how it interact with discovery. irlap_state_ndm()
|
| /linux-4.4.14/net/openvswitch/ |
| H A D | datapath.c | 108 * synchronization but they nest under all of above and don't interact with
|
| /linux-4.4.14/include/net/ |
| H A D | cfg80211.h | 4347 * also need to interact with the rfkill subsystem, via cfg80211.
4496 * interact with driver-specific tools to aid, for instance,
4499 * This chapter describes how drivers interact with it, for more
|
| /linux-4.4.14/drivers/usb/misc/ |
| H A D | usbtest.c | 2064 * different sequences. Nothing here should interact with other devices,
|
| /linux-4.4.14/drivers/scsi/cxgbi/ |
| H A D | libcxgbi.c | 1777 * pdu receive, interact with libiscsi_tcp
|
| /linux-4.4.14/drivers/net/ethernet/packetengines/ |
| H A D | hamachi.c | 370 03/13/2000 KDU Added a patch to make the Rx Checksum code interact
|
| /linux-4.4.14/fs/jbd2/ |
| H A D | transaction.c | 2541 * File truncate and transaction commit interact with each other in a
|
| /linux-4.4.14/net/unix/ |
| H A D | af_unix.c | 748 * AF_UNIX sockets do not interact with hardware, hence they
|
| /linux-4.4.14/fs/ceph/ |
| H A D | mds_client.c | 41 * We maintain a stateful "session" with each MDS we interact with.
|
| /linux-4.4.14/drivers/net/ethernet/natsemi/ |
| H A D | natsemi.c | 258 Unlike software-only systems, device drivers interact with complex hardware.
|
| /linux-4.4.14/kernel/events/ |
| H A D | core.c | 925 * interact.
|