Home
last modified time | relevance | path

Searched refs:handles (Results 1 – 200 of 207) sorted by relevance

12

/linux-4.4.14/drivers/xen/xenbus/
Dxenbus_client.c68 grant_handle_t handles[XENBUS_MAX_RING_GRANTS]; member
482 grant_handle_t *handles, in __xenbus_map_ring() argument
499 handles[i] = INVALID_GRANT_HANDLE; in __xenbus_map_ring()
512 handles[i] = map[i].handle; in __xenbus_map_ring()
519 if (handles[i] != INVALID_GRANT_HANDLE) { in __xenbus_map_ring()
522 GNTMAP_host_map, handles[i]); in __xenbus_map_ring()
572 err = __xenbus_map_ring(dev, gnt_refs, nr_grefs, node->handles, in xenbus_map_ring_valloc_pv()
653 err = __xenbus_map_ring(dev, gnt_ref, nr_grefs, node->handles, in xenbus_map_ring_valloc_hvm()
678 xenbus_unmap_ring(dev, node->handles, nr_grefs, info.addrs); in xenbus_map_ring_valloc_hvm()
711 unsigned int nr_grefs, grant_handle_t *handles, in xenbus_map_ring() argument
[all …]
/linux-4.4.14/drivers/gpu/drm/armada/
Darmada_fb.c117 (mode->handles[0] != mode->handles[1] || in armada_fb_create()
118 mode->handles[0] != mode->handles[2])) { in armada_fb_create()
123 obj = armada_gem_object_lookup(dev, dfile, mode->handles[0]); in armada_fb_create()
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_uvd.c198 atomic_set(&adev->uvd.handles[i], 0); in amdgpu_uvd_sw_init()
241 uint32_t handle = atomic_read(&adev->uvd.handles[i]); in amdgpu_uvd_suspend()
257 atomic_set(&adev->uvd.handles[i], 0); in amdgpu_uvd_suspend()
297 uint32_t handle = atomic_read(&adev->uvd.handles[i]); in amdgpu_uvd_free_handles()
313 atomic_set(&adev->uvd.handles[i], 0); in amdgpu_uvd_free_handles()
563 if (atomic_read(&adev->uvd.handles[i]) == handle) { in amdgpu_uvd_cs_msg()
568 if (!atomic_cmpxchg(&adev->uvd.handles[i], 0, handle)) { in amdgpu_uvd_cs_msg()
586 if (atomic_read(&adev->uvd.handles[i]) == handle) { in amdgpu_uvd_cs_msg()
601 atomic_cmpxchg(&adev->uvd.handles[i], handle, 0); in amdgpu_uvd_cs_msg()
1016 unsigned i, fences, handles = 0; in amdgpu_uvd_idle_work_handler() local
[all …]
Damdgpu_vce.c174 atomic_set(&adev->vce.handles[i], 0); in amdgpu_vce_sw_init()
217 if (atomic_read(&adev->vce.handles[i])) in amdgpu_vce_suspend()
335 uint32_t handle = atomic_read(&adev->vce.handles[i]); in amdgpu_vce_free_handles()
346 atomic_set(&adev->vce.handles[i], 0); in amdgpu_vce_free_handles()
579 if (atomic_read(&p->adev->vce.handles[i]) == handle) { in amdgpu_vce_validate_handle()
590 if (!atomic_cmpxchg(&p->adev->vce.handles[i], 0, handle)) { in amdgpu_vce_validate_handle()
740 atomic_cmpxchg(&p->adev->vce.handles[i], handle, 0); in amdgpu_vce_ring_parse_cs()
Damdgpu_display.c556 obj = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[0]); in amdgpu_user_framebuffer_create()
559 "can't create framebuffer\n", mode_cmd->handles[0]); in amdgpu_user_framebuffer_create()
Damdgpu.h1677 atomic_t handles[AMDGPU_MAX_UVD_HANDLES]; member
1700 atomic_t handles[AMDGPU_MAX_VCE_HANDLES]; member
/linux-4.4.14/drivers/gpu/drm/radeon/
Dradeon_uvd.c176 atomic_set(&rdev->uvd.handles[i], 0); in radeon_uvd_init()
213 uint32_t handle = atomic_read(&rdev->uvd.handles[i]); in radeon_uvd_suspend()
230 atomic_set(&rdev->uvd.handles[i], 0); in radeon_uvd_suspend()
288 uint32_t handle = atomic_read(&rdev->uvd.handles[i]); in radeon_uvd_free_handles()
305 atomic_set(&rdev->uvd.handles[i], 0); in radeon_uvd_free_handles()
473 if (atomic_read(&p->rdev->uvd.handles[i]) == handle) { in radeon_uvd_cs_msg()
478 if (!atomic_cmpxchg(&p->rdev->uvd.handles[i], 0, handle)) { in radeon_uvd_cs_msg()
499 if (atomic_read(&p->rdev->uvd.handles[i]) == handle) { in radeon_uvd_cs_msg()
514 atomic_cmpxchg(&p->rdev->uvd.handles[i], handle, 0); in radeon_uvd_cs_msg()
811 if (!atomic_read(&rdev->uvd.handles[i])) in radeon_uvd_count_handles()
Dradeon_vce.c167 atomic_set(&rdev->vce.handles[i], 0); in radeon_vce_init()
205 if (atomic_read(&rdev->vce.handles[i])) in radeon_vce_suspend()
320 uint32_t handle = atomic_read(&rdev->vce.handles[i]); in radeon_vce_free_handles()
332 atomic_set(&rdev->vce.handles[i], 0); in radeon_vce_free_handles()
528 if (atomic_read(&p->rdev->vce.handles[i]) == handle) { in radeon_vce_validate_handle()
539 if (!atomic_cmpxchg(&p->rdev->vce.handles[i], 0, handle)) { in radeon_vce_validate_handle()
680 atomic_cmpxchg(&p->rdev->vce.handles[i], handle, 0); in radeon_vce_cs_parse()
Dradeon_display.c1370 obj = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[0]); in radeon_user_framebuffer_create()
1373 "can't create framebuffer\n", mode_cmd->handles[0]); in radeon_user_framebuffer_create()
Dradeon.h1680 atomic_t handles[RADEON_MAX_UVD_HANDLES]; member
1722 atomic_t handles[RADEON_MAX_VCE_HANDLES]; member
/linux-4.4.14/Documentation/devicetree/bindings/display/ti/
Dti,omap5-dss.txt47 - clocks: handles to fclk and iclk
65 - clocks: handles to fclk and pll clock
88 - clocks: handles to fclk and pll clock
Dti,omap4-dss.txt47 - clocks: handles to fclk and iclk
84 - clocks: handles to fclk and pll clock
107 - clocks: handles to fclk and pll clock
Dti,omap3-dss.txt48 - clocks: handles to fclk and iclk
78 - clocks: handles to fclk and pll clock
Dti,dra7-dss.txt61 - clocks: handles to fclk and pll clock
/linux-4.4.14/Documentation/sysctl/
Dfs.txt96 handles that the Linux kernel will allocate. When you get lots
97 of error messages about running out of file handles, you might
100 Historically,the kernel was able to allocate file handles
102 file-nr denote the number of allocated file handles, the number
103 of allocated but unused file handles, and the maximum number of
104 file handles. Linux 2.6 always reports 0 as the number of free
105 file handles -- this is not an error, it just means that the
106 number of allocated file handles exactly matches the number of
107 used file handles.
116 This denotes the maximum number of file-handles a process can
[all …]
/linux-4.4.14/Documentation/scsi/
Dufs.txt57 * UCS: It handles SCSI commands supported by UFS specification.
58 * Task manager: It handles task management functions defined by the
60 * Device manager: It handles device level operations and device
83 UIC is the lowest layer of UFS layered architecture. It handles
116 Error handling module handles Host controller fatal errors,
Dmegaraid.txt42 handles registering the /dev/megaraid node dynamically. In this case,
61 applications into uioc_t. After driver handles the uioc_t, the common module
Dcxgb3i.txt8 (DDP) where the hardware handles the expensive byte touching operations, such
31 the TCP segments onto the wire. It handles TCP retransmission if
DChangeLog.sym53c8xx_256 - Add optionnal code that handles IO timeouts from the driver.
DChangeLog.megaraid_sas637 ii. Defined MEGASAS_IOC_FIRMWARE32 for code paths that handles 32 bit applications in 64 bit system…
DChangeLog.megaraid574 handles registering the /dev/megaraid node dynamically. In this case,
DChangeLog.sym53c8xx495 With a 896 that handles MA from SCRIPTS, this can be a great win,
Dsym53c8xx_2.txt124 LOAD/STORE and handles PHASE MISMATCH from SCRIPTS for devices that
Dscsi_mid_low_api.txt1190 that handles both ISA and PCI cards and has a separate instance of
/linux-4.4.14/arch/c6x/kernel/
Dvectors.S11 ; This section handles all the interrupt vector routines.
13 ; branches to the label _c_int00 which handles initialization for the C code.
/linux-4.4.14/drivers/platform/x86/
Dsony-laptop.c835 static struct sony_nc_handles *handles; variable
843 for (i = 0; i < ARRAY_SIZE(handles->cap); i++) { in sony_nc_handles_show()
845 handles->cap[i]); in sony_nc_handles_show()
856 handles = kzalloc(sizeof(*handles), GFP_KERNEL); in sony_nc_handles_setup()
857 if (!handles) in sony_nc_handles_setup()
860 for (i = 0; i < ARRAY_SIZE(handles->cap); i++) { in sony_nc_handles_setup()
867 handles->cap[i] = result; in sony_nc_handles_setup()
872 sysfs_attr_init(&handles->devattr.attr); in sony_nc_handles_setup()
873 handles->devattr.attr.name = "handles"; in sony_nc_handles_setup()
874 handles->devattr.attr.mode = S_IRUGO; in sony_nc_handles_setup()
[all …]
DKconfig678 This driver handles RFKill events for the TOS6205 Bluetooth,
763 This driver handles the power button on the Intel MID platforms.
946 This driver handles the power/home/volume buttons on the Microsoft Surface Pro 3 tablet.
/linux-4.4.14/arch/x86/boot/compressed/
Deboot.c381 u32 *handles = (u32 *)(unsigned long)pci_handle; in setup_efi_pci32() local
395 u32 h = handles[i]; in setup_efi_pci32()
488 u64 *handles = (u64 *)(unsigned long)pci_handle; in setup_efi_pci64() local
502 u64 h = handles[i]; in setup_efi_pci64()
658 u32 *handles = (u32 *)(unsigned long)gop_handle; in setup_gop32() local
670 u32 h = handles[i]; in setup_gop32()
771 u64 *handles = (u64 *)(unsigned long)gop_handle; in setup_gop64() local
783 u64 h = handles[i]; in setup_gop64()
886 u32 *handles = (u32 *)uga_handle;; in setup_uga32() local
896 u32 handle = handles[i]; in setup_uga32()
[all …]
/linux-4.4.14/include/xen/
Dxenbus.h212 grant_handle_t *handles, unsigned long *vaddrs,
217 grant_handle_t *handles, unsigned int nr_handles,
/linux-4.4.14/drivers/gpu/drm/sti/
DNOTES12 - The cursor handles ... a cursor.
15 - DVO (Digital Video Output) handles a 24bits parallel signal
/linux-4.4.14/drivers/thermal/samsung/
DKconfig7 the TMU, reports temperature and handles cooling action if defined.
/linux-4.4.14/drivers/scsi/qla2xxx/
Dqla_isr.c584 uint32_t handles[5]; in qla2x00_async_event() local
599 handles[0] = le32_to_cpu((uint32_t)((mb[2] << 16) | mb[1])); in qla2x00_async_event()
603 handles[0] = mb[1]; in qla2x00_async_event()
608 handles[0] = mb[1]; in qla2x00_async_event()
609 handles[1] = mb[2]; in qla2x00_async_event()
614 handles[0] = mb[1]; in qla2x00_async_event()
615 handles[1] = mb[2]; in qla2x00_async_event()
616 handles[2] = mb[3]; in qla2x00_async_event()
621 handles[0] = mb[1]; in qla2x00_async_event()
622 handles[1] = mb[2]; in qla2x00_async_event()
[all …]
Dqla_mr.h88 __le32 handles[MAX_HANDLE_COUNT]; member
Dqla_mr.c2647 handle_ptr = &stsmfx->handles[0]; in qlafx00_multistatus_entry()
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dts3a227e.txt6 handles key press detection in accordance with the Android audio
/linux-4.4.14/arch/arm/crypto/
Dsha512-core.S_shipped543 vld1.64 {d0},[r1]! @ handles unaligned
580 vld1.64 {d1},[r1]! @ handles unaligned
617 vld1.64 {d2},[r1]! @ handles unaligned
654 vld1.64 {d3},[r1]! @ handles unaligned
691 vld1.64 {d4},[r1]! @ handles unaligned
728 vld1.64 {d5},[r1]! @ handles unaligned
765 vld1.64 {d6},[r1]! @ handles unaligned
802 vld1.64 {d7},[r1]! @ handles unaligned
839 vld1.64 {d8},[r1]! @ handles unaligned
876 vld1.64 {d9},[r1]! @ handles unaligned
[all …]
Dsha1-armv4-large.S83 ldr r9,[r1],#4 @ handles unaligned
108 ldr r9,[r1],#4 @ handles unaligned
133 ldr r9,[r1],#4 @ handles unaligned
158 ldr r9,[r1],#4 @ handles unaligned
183 ldr r9,[r1],#4 @ handles unaligned
211 ldr r9,[r1],#4 @ handles unaligned
/linux-4.4.14/drivers/staging/android/ion/
Dion.c86 struct rb_root handles; member
372 rb_erase(&handle->node, &client->handles); in ion_handle_destroy()
405 struct rb_node *n = client->handles.rb_node; in ion_handle_lookup()
444 struct rb_node **p = &client->handles.rb_node; in ion_handle_add()
467 rb_insert_color(&handle->node, &client->handles); in ion_handle_add()
689 for (n = rb_first(&client->handles); n; n = rb_next(n)) { in ion_debug_client_show()
773 client->handles = RB_ROOT; in ion_client_create()
835 while ((n = rb_first(&client->handles))) { in ion_client_destroy()
1386 for (n = rb_first(&client->handles); n; n = rb_next(n)) { in ion_debug_heap_total()
/linux-4.4.14/Documentation/power/
Dswsusp-and-swap-files.txt4 The Linux kernel handles swap files almost in the same way as it handles swap
/linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/
Dexynos-adc.txt6 New driver handles the following
39 - clocks From common clock bindings: handles to clocks specified
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmarvell-orion-mdio.txt5 an interface with the MDIO bus. This driver handles this MDIO
/linux-4.4.14/drivers/accessibility/
DKconfig4 Accessibility handles all special kinds of hardware devices or
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dti,cdce706.txt11 handles, shall be reference clock(s) connected to CLK_IN0
Dsilabs,si5351.txt19 handles, shall be xtal reference clock or xtal and clkin for
/linux-4.4.14/drivers/gpu/drm/omapdrm/
Domap_drv.h251 struct drm_gem_object **bos, uint32_t *handles) in objects_lookup() argument
256 bos[i] = drm_gem_object_lookup(dev, filp, handles[i]); in objects_lookup()
Domap_fb.c374 bos, mode_cmd->handles); in omap_framebuffer_create()
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-class-rfkill29 Values: 0: Kernel handles events
/linux-4.4.14/drivers/gpu/drm/nouveau/
Dnouveau_abi16.h33 u64 handles; member
Dnouveau_display.c281 gem = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[0]); in nouveau_user_framebuffer_create()
/linux-4.4.14/Documentation/cpuidle/
Ddriver.txt10 cpuidle driver hooks into the cpuidle infrastructure and handles the
/linux-4.4.14/net/l2tp/
DKconfig28 The kernel component handles only L2TP data packets: a
29 userland daemon handles L2TP the control protocol (tunnel
/linux-4.4.14/drivers/staging/most/Documentation/
Ddriver_usage.txt28 module only. This module handles the communication flow through all three
34 HDM (hardware dependent module). Each module of this layer handles exactly
51 that handles the interface.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Drockchip-dw-mshc.txt19 specified in clock-names, should contain handles to these clocks.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmfd.txt10 silicon) that handles analog drivers for things like audio amplifiers, LED
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-firmware-dmi-entries45 assigned entry handles as the kernel itself makes no
46 guarantees that handles as exported are unique, and
Dsysfs-firmware-acpi67 special driver support. So while the SCI handles a few
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset77 first disabling all VFs attached to that PF. s-Par handles this
96 first disabling all VFs attached to that PF. s-Par handles this
/linux-4.4.14/Documentation/usb/
Dohci.txt23 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
Ddwc3.txt39 handles the remaining EP work which might sleep such as waiting
DURB.txt33 data to an endpoint while your driver handles completion of another.
/linux-4.4.14/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt7 binary to accomplish this. The wkup_m3 remoteproc driver handles the loading of
/linux-4.4.14/tools/thermal/tmon/
DREADME27 tui.c : handles ncurses based user interface
/linux-4.4.14/Documentation/arm/SA1100/
Dserial_UART11 > tty device layer handles this just fine, so you don't have to worry about
/linux-4.4.14/drivers/gpu/drm/exynos/
Dexynos_drm_ipp.h90 unsigned long handles[EXYNOS_DRM_PLANAR_MAX]; member
Dexynos_drm_fb.c167 mode_cmd->handles[i]); in exynos_user_fb_create()
Dexynos_drm_ipp.c491 if (m_node->buf_info.handles[i]) { in ipp_validate_mem_node()
493 m_node->buf_info.handles[i], in ipp_validate_mem_node()
532 unsigned long handle = m_node->buf_info.handles[i]; in ipp_put_mem_node()
583 buf_info->handles[i] = qbuf->handle[i]; in ipp_get_mem_node()
586 buf_info->base[i], buf_info->handles[i]); in ipp_get_mem_node()
Dexynos_drm_g2d.c182 unsigned long handles[MAX_REG_TYPE_NR]; member
757 buf_info->handles[reg_type] = handle; in g2d_map_cmdlist_gem()
783 handle = buf_info->handles[reg_type]; in g2d_unmap_cmdlist_gem()
793 buf_info->handles[reg_type] = 0; in g2d_unmap_cmdlist_gem()
/linux-4.4.14/drivers/fmc/
DKconfig32 The driver also handles interrupts (we used it with a real carrier
/linux-4.4.14/Documentation/fb/
Dcmap_xfbdev.txt34 Somewhere in X's callchain, this results in a call to X code that handles the
/linux-4.4.14/drivers/gpu/drm/rockchip/
Drockchip_drm_fb.c127 mode_cmd->handles[i]); in rockchip_user_fb_create()
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dpd-samsung.txt15 - clocks: List of clock handles. The parent clocks of the input clocks to the
Drockchip-io-domain.txt13 Said another way, this driver simply handles keeping bits in the SoC's
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dshdma.txt77 where MID/RID values are fixed handles, specified in the SoC
/linux-4.4.14/drivers/uio/
DKconfig20 driver requires a userspace component called cif that handles
34 handles interrupts in a special way. Userspace is responsible
/linux-4.4.14/drivers/misc/vmw_vmci/
Dvmci_host.c203 struct vmci_handle *handles; in drv_cp_harray_to_user() local
208 if (array_size * sizeof(*handles) > *user_buf_size) in drv_cp_harray_to_user()
211 *user_buf_size = array_size * sizeof(*handles); in drv_cp_harray_to_user()
/linux-4.4.14/drivers/acpi/
Dthermal.c791 handle = tz->trips.passive.devices.handles[i]; in acpi_thermal_cooling_device_cb()
817 handle = tz->trips.active[i].devices.handles[j]; in acpi_thermal_cooling_device_cb()
835 handle = tz->devices.handles[i]; in acpi_thermal_cooling_device_cb()
1160 tz->trips.active[i].devices.handles[j], in acpi_thermal_resume()
Dutils.c384 list->handles[i] = element->reference.handle; in acpi_evaluate_reference()
386 list->handles[i])); in acpi_evaluate_reference()
Dscan.c1580 status = acpi_get_object_info(dep_devices.handles[i], &info); in acpi_device_dep_initialize()
1602 dep->master = dep_devices.handles[i]; in acpi_device_dep_initialize()
DKconfig161 This driver handles events on the power, sleep, and lid buttons.
/linux-4.4.14/Documentation/dvb/
Dci.txt11 For the Twinhan/Twinhan clones, the dst_ca module handles the CI
107 This means that this CI interface handles the EN50221 style tags in the
/linux-4.4.14/drivers/sbus/char/
DKconfig27 on the Tadpole Sparcbook 3. This device handles power-management
/linux-4.4.14/Documentation/hwmon/
Dadm102544 the driver handles that is to preserve this bit through the initialization
Dvia686a71 This driver handles sensors integrated in some VIA south bridges. It is
Dit87196 The driver handles this transparently so user-space doesn't have to care.
/linux-4.4.14/Documentation/i2c/
Di2c-stub16 handles.
Dslave-interface127 * write the slave_callback which handles the above slave events
Dwriting-clients152 Remember that the i2c_driver does not create those client handles. The
/linux-4.4.14/drivers/usb/phy/
DKconfig147 handles PHY initialization, clock management, and workarounds
162 It handles PHY initialization, clock management, power management,
/linux-4.4.14/drivers/soc/ti/
Dknav_qmss.h267 struct list_head handles; member
Dknav_qmss_queue.c64 list_for_each_entry_rcu(qh, &inst->handles, list)
152 return !list_empty(&inst->handles); in knav_queue_is_busy()
246 list_add_tail_rcu(&qh->list, &inst->handles); in __knav_queue_open()
1641 INIT_LIST_HEAD(&inst->handles); in knav_queue_init_queue()
/linux-4.4.14/drivers/gpu/drm/msm/
Dmsm_fb.c149 mode_cmd->handles[i]); in msm_framebuffer_create()
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt8 - The dynamic loader handles LD_* environment variables differently if
/linux-4.4.14/Documentation/input/
Dinput.txt103 handles all HID devices, and because there is a very wide variety of them,
106 Currently, it handles USB mice, joysticks, gamepads, steering wheels
129 usbmouse driver. It handles USB mice only. It uses a simpler HIDBP
Diforce-protocol.txt25 The 2B, LEN and CS fields have disappeared, probably because USB handles frames and
Djoystick.txt391 provide an "Enhanced Game Port" mode where the soundcard handles polling the
/linux-4.4.14/Documentation/misc-devices/
Dapds990x.txt25 Driver makes necessary conversions to both directions so that user handles
/linux-4.4.14/drivers/gpu/drm/cirrus/
Dcirrus_main.c64 obj = drm_gem_object_lookup(dev, filp, mode_cmd->handles[0]); in cirrus_user_framebuffer_create()
/linux-4.4.14/Documentation/infiniband/
Duser_verbs.txt36 between kernel pointers and opaque userspace handles, so that kernel
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio.txt30 A single IRQ that handles error conditions is specified by this
Dsrio-rmu.txt124 A single IRQ that handles port-write conditions is
/linux-4.4.14/arch/x86/crypto/
Dcrc32c-pcl-intel-asm_64.S64 # efficient "by-1" code. This "by-1" code only handles up to 255 bytes, so
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt28 - clocks: phandle to dma instances clocks. The clock handles can be as
/linux-4.4.14/Documentation/virtual/kvm/devices/
Ds390_flic.txt4 FLIC handles floating (non per-cpu) interrupts, i.e. I/O, service and some
/linux-4.4.14/Documentation/networking/
Drds.txt255 The general layer handles the socket API, congestion handling,
258 The transport layer handles the details of the transport. The IB
259 transport, for example, handles all the queue pairs, work requests,
Dphy.txt75 1) The PAL handles everything, and only calls the network driver when
78 2) The PAL handles everything except interrupts (usually because the
81 3) The PAL handles everything, but checks in with the driver every second,
Daltera_tse.txt69 interrupt is driven by the transmit DMA logic. The driver handles the transmit
78 received, the DMA logic generates an interrupt. The driver handles a receive
Dbatman-adv.txt110 longer because batman handles them for you. Basically, one "hands
Dtuntap.txt212 the kernel handles the packet like it came from real physical device.
Dl2tp.txt62 pppd, handles all PPP interaction with the peer. PPP network
Dstmmac.txt78 Driver handles both normal and alternate descriptors. The latter has been only
Dscaling.txt245 a single application thread handles flows with many different flow hashes.
/linux-4.4.14/Documentation/crypto/
Dasync-tx-api.txt48 API automatically handles cases where the transition from one operation
104 it polls for the completion of the operation. It handles dependency
/linux-4.4.14/Documentation/ptp/
Dptp.txt29 class driver handles all of the dealings with user space. The
/linux-4.4.14/drivers/s390/net/
DKconfig55 uevents. The driver handles only those special messages that
/linux-4.4.14/include/uapi/drm/
Ddrm_mode.h386 __u32 handles[4]; member
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra20-emc.txt58 might exist on the system. The Tegra20 platform handles this during
/linux-4.4.14/arch/arc/kernel/
Dentry-arcv2.S97 ; - Unlike ARCompact, handles Bus errors for both User/Kernel mode,
/linux-4.4.14/arch/m68k/fpsp040/
Dsgetem.S7 | precision number in fp0. sGETEXPD handles denormalized
Dres_func.S110 | cu_norm handles fmove in instructions with normalized inputs.
473 | Inst is fmove. This code also handles all result writes.
757 | This code handles the case of the instruction resulting in
1217 | This code handles the case of the instruction resulting in
/linux-4.4.14/drivers/gpu/drm/mgag200/
Dmgag200_main.c56 obj = drm_gem_object_lookup(dev, filp, mode_cmd->handles[0]); in mgag200_user_framebuffer_create()
/linux-4.4.14/Documentation/sound/alsa/soc/
Doverview.txt67 "sound card device". It handles any machine specific controls and
Dcodec.txt140 This function is a callback that handles codec domain PM calls and system
/linux-4.4.14/drivers/gpu/drm/
Ddrm_ioc32.c1024 u32 handles[4]; member
1052 if (__put_user(req32.handles[i], &req64->handles[i])) in compat_drm_mode_addfb2()
Ddrm_fb_cma_helper.c128 obj = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[i]); in drm_fb_cma_create()
Ddrm_crtc.c2812 .handles = { req->handle }, in drm_mode_cursor_universal()
3052 r.handles[0] = or->handle; in drm_mode_addfb()
3166 if (!r->handles[i]) { in framebuffer_check()
3217 if (r->handles[i]) { in framebuffer_check()
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt59 The visorbus driver handles the virtual busses on which all of the virtual
252 while the guest driver handles sending commands and handling responses. Each
285 service partition; the guest driver handles communication and link
/linux-4.4.14/Documentation/
Drobust-futex-ABI.txt21 mechanism, which handles uncontested locking without needing a system
22 call, and handles contested locking by maintaining a list of waiting
DSubmittingDrivers94 that your driver correctly handles the suspend and resume, but
Dkref.txt99 data, the kref_put() handles knowing when the data is not referenced
Dpinctrl.txt291 which pin controller handles control of a certain GPIO pin. Since a single
1185 handling of the pinctrl handles and states.
1287 requested pinctrl handles, for example if the pinctrl driver has not yet
Dbcache.txt17 great lengths to protect your data - it reliably handles unclean shutdown. (It
Dkobject.txt39 safely ignore that implementation detail as the kset core code handles
Ddma-buf-sharing.txt353 handles, too). So it's beneficial to support this in a similar fashion on
Dparport-lowlevel.txt64 accesses. Each low-level driver handles a particular style of port
DIPMI.txt96 system. It handles all messages, message timing, and responses. The
/linux-4.4.14/drivers/gpu/drm/tegra/
Dfb.c150 gem = drm_gem_object_lookup(drm, file, cmd->handles[i]); in tegra_fb_create()
/linux-4.4.14/Documentation/acpi/
Dscan_handlers.txt76 All scan handles must be added to the list before acpi_bus_scan() is run for the
/linux-4.4.14/Documentation/filesystems/
Ddlmfs.txt66 dlmfs handles lock caching automatically for the user, so a lock
Dqnx6.txt21 The Linux driver handles endianness transparently. (LE and BE)
Dhpfs.txt181 crashes when the tree is not balanced. This driver handles unbalanced trees
Dcoda.txt203 Generally the operating system handles the request in a virtual
255 kernel FS driver handles such requests synchronously.
1436 internal file handles (called vnodes in BSD, inodes in Linux and
Df2fs.txt134 device handles the cache_flush command relatively slowly,
/linux-4.4.14/drivers/gpu/drm/ast/
Dast_main.c336 obj = drm_gem_object_lookup(dev, filp, mode_cmd->handles[0]); in ast_user_framebuffer_create()
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt94 - CFSERVL General CAIF Service Layer functionality; handles flow
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Drenesas,pfc-pinctrl.txt34 IRQ pins. This property is mandatory when the PFC handles GPIOs and
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt166 the given GPU platforms. This means a driver needs to expose tons of handles
186 * Think about uniqueness requirements for userspace handles. E.g. for most drm
/linux-4.4.14/drivers/gpu/drm/virtio/
Dvirtgpu_display.c475 obj = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[0]); in virtio_gpu_user_framebuffer_create()
/linux-4.4.14/arch/m68k/q40/
DREADME101 q40 master chip handles only a subset of level triggered interrupts.
/linux-4.4.14/include/acpi/
Dacpi_bus.h32 acpi_handle handles[ACPI_MAX_HANDLES]; member
/linux-4.4.14/drivers/gpu/drm/bochs/
Dbochs_mm.c521 obj = drm_gem_object_lookup(dev, filp, mode_cmd->handles[0]); in bochs_user_framebuffer_create()
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt190 Only when llc_shdlc is used: handles shdlc rx & tx queues.
227 handles shdlc framing in and out. It uses the driver xmit to send frames and
/linux-4.4.14/Documentation/arm/
DIXP4xx99 Currently the code only handles level-sensitive GPIO interrupts
Dcluster-pm-race-avoidance.txt174 the kernel. The kernel handles the rest of the resume
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt87 Note that if you want to have a dedicated thread which handles
/linux-4.4.14/include/net/bluetooth/
Dhci.h1617 struct hci_comp_pkts_info handles[0]; member
1850 struct hci_comp_blocks_info handles[0]; member
/linux-4.4.14/drivers/gpu/drm/udl/
Dudl_fb.c634 obj = drm_gem_object_lookup(dev, file, mode_cmd->handles[0]); in udl_fb_user_fb_create()
/linux-4.4.14/drivers/gpu/drm/gma500/
Dframebuffer.c500 obj = drm_gem_object_lookup(dev, filp, cmd->handles[0]); in psb_user_framebuffer_create()
/linux-4.4.14/Documentation/virtual/kvm/
Dppc-pv.txt113 MAGIC_PAGE_FLAG_NOT_MAPPED_NX Guest handles NX bits correctly wrt magic page
/linux-4.4.14/Documentation/isdn/
DsyncPPP.FAQ25 The ipppd handles PPP packets coming in HDLC
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt62 handles this internally by maintaining request queues for the applications.
/linux-4.4.14/Documentation/blockdev/
Dfloppy.txt159 driver handles both.)
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt106 object. configfs handles the filesystem representation of that object
113 handles that. The group has a set of operations to perform these tasks
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-cache.txt23 The common code handles such things as:
/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt319 and handles interrupts for container events such as hot plug.
/linux-4.4.14/Documentation/virtual/kvm/arm/
Dvgic-mapped-irqs.txt14 host OS initially handles the interrupt and must somehow signal this
/linux-4.4.14/Documentation/ide/
Dide.txt76 The IDE driver automatically detects and handles this. However, this may
DChangeLog.ide-cd.1994-2004187 * handles resets fine now. <axboe@image.dk>
/linux-4.4.14/Documentation/sh/
Dnew-machine.txt160 handles).
/linux-4.4.14/Documentation/x86/
Dintel_mpx.txt112 present. The kernel handles those #BR exceptions for not-present tables
/linux-4.4.14/drivers/mtd/
DKconfig99 Due to the way Linux handles the command line, no spaces are
/linux-4.4.14/drivers/base/
DKconfig42 rescue systems, and reliably handles dynamic major/minor numbers.
/linux-4.4.14/drivers/media/rc/
DKconfig23 LIRC daemon handles protocol decoding for IR reception and
/linux-4.4.14/drivers/gpu/drm/qxl/
Dqxl_display.c1017 obj = drm_gem_object_lookup(dev, file_priv, mode_cmd->handles[0]); in qxl_user_framebuffer_create()
/linux-4.4.14/Documentation/video4linux/
Dvideobuf6 and user space. It handles the allocation and management of buffers for
Dv4l2-controls.txt559 A common type of control cluster is one that handles 'auto-foo/foo'-type
Dv4l2-framework.txt458 The device node handles a subset of the V4L2 API.
/linux-4.4.14/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt7 sizing and assignment on PowerKVM and how generic PCI code handles this
/linux-4.4.14/Documentation/filesystems/caching/
Dfscache.txt164 indexed by NFS file handles to get data file objects. Each data file
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt376 that handles the end of transfer interrupts in the handler, but defer
/linux-4.4.14/Documentation/sound/oss/
DREADME.OSS656 The driver handles software configurable cards automatically. Just configure
1059 program handles these options itself. (You may use the SB, MPU and MSS options
1087 in the proper address. The SB driver handles the rest. You have to configure
1109 The SoundScape driver handles initialization of MSS and MPU supports
/linux-4.4.14/Documentation/thermal/
Dsysfs-api.txt486 This function handles the trip events from sensor drivers. It starts
/linux-4.4.14/drivers/net/usb/
DKconfig580 called VL600. This driver only handles the ethernet
/linux-4.4.14/Documentation/arm64/
Dacpi_object_usage.txt537 Since there is no direct equivalent of the x86 SCI or NMI, arm64 handles
/linux-4.4.14/Documentation/s390/
Dcds.txt55 the channel program and handles the interrupt itself.
/linux-4.4.14/Documentation/RCU/
Dchecklist.txt346 an issue, the memory-allocator locking handles it). However,
/linux-4.4.14/drivers/gpu/drm/vmwgfx/
Dvmwgfx_kms.c989 mode_cmd.handle = mode_cmd2->handles[0]; in vmw_kms_fb_create()
/linux-4.4.14/drivers/usb/serial/
DKconfig58 handles a wide range of very simple devices, all in one
/linux-4.4.14/net/bluetooth/
Dhci_event.c3199 struct hci_comp_pkts_info *info = &ev->handles[i]; in hci_num_comp_pkts_evt()
3287 struct hci_comp_blocks_info *info = &ev->handles[i]; in hci_num_comp_blocks_evt()
/linux-4.4.14/drivers/gpio/
DKconfig914 Note, that usually system firmware/ACPI handles GPIO pins on their
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq626 * are busy. This handles the non-packetized
679 * are busy. This handles the non-packetized
/linux-4.4.14/Documentation/gpio/
Dgpio-legacy.txt601 function devices, FPGAs or CPLDs -- most often board-specific code handles
/linux-4.4.14/drivers/staging/comedi/
DKconfig52 Currently, it only handles digital I/O subdevices.
/linux-4.4.14/net/netfilter/
DKconfig996 all nodes see all packets and this match decides which node handles
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt738 the binary. In other words, Kbuild handles hostprogs-m exactly
/linux-4.4.14/drivers/watchdog/
DKconfig1451 LPAR provides a very similar interface. This driver handles
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex810 This function handles all the standard $ioctl$ requests for \cdrom\
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt1078 also handles volume control for the headphone and speakers on these
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dpfpsp.S2401 # This exception handles 3 types of operations: #
/linux-4.4.14/Documentation/block/
Dbiodoc.txt462 by using rq_for_each_segment. This handles the fact that a request
/linux-4.4.14/lib/
DKconfig.debug1532 and to test how the mmc host driver handles retries from

12