Home
last modified time | relevance | path

Searched refs:callbacks (Results 1 – 166 of 166) sorted by relevance

/linux-4.1.27/net/lapb/
Dlapb_iface.c145 const struct lapb_register_struct *callbacks) in lapb_register() argument
164 lapb->callbacks = callbacks; in lapb_register()
383 if (lapb->callbacks->connect_confirmation) in lapb_connect_confirmation()
384 lapb->callbacks->connect_confirmation(lapb->dev, reason); in lapb_connect_confirmation()
389 if (lapb->callbacks->connect_indication) in lapb_connect_indication()
390 lapb->callbacks->connect_indication(lapb->dev, reason); in lapb_connect_indication()
395 if (lapb->callbacks->disconnect_confirmation) in lapb_disconnect_confirmation()
396 lapb->callbacks->disconnect_confirmation(lapb->dev, reason); in lapb_disconnect_confirmation()
401 if (lapb->callbacks->disconnect_indication) in lapb_disconnect_indication()
402 lapb->callbacks->disconnect_indication(lapb->dev, reason); in lapb_disconnect_indication()
[all …]
/linux-4.1.27/sound/drivers/opl3/
Dopl3_seq.c175 struct snd_seq_port_callback callbacks; in snd_opl3_synth_create_port() local
186 memset(&callbacks, 0, sizeof(callbacks)); in snd_opl3_synth_create_port()
187 callbacks.owner = THIS_MODULE; in snd_opl3_synth_create_port()
188 callbacks.use = snd_opl3_synth_use; in snd_opl3_synth_create_port()
189 callbacks.unuse = snd_opl3_synth_unuse; in snd_opl3_synth_create_port()
190 callbacks.event_input = snd_opl3_synth_event_input; in snd_opl3_synth_create_port()
191 callbacks.private_free = snd_opl3_synth_free_port; in snd_opl3_synth_create_port()
192 callbacks.private_data = opl3; in snd_opl3_synth_create_port()
198 opl3->chset->port = snd_seq_event_port_attach(opl3->seq_client, &callbacks, in snd_opl3_synth_create_port()
Dopl3_oss.c78 struct snd_seq_port_callback callbacks; in snd_opl3_oss_create_port() local
89 memset(&callbacks, 0, sizeof(callbacks)); in snd_opl3_oss_create_port()
90 callbacks.owner = THIS_MODULE; in snd_opl3_oss_create_port()
91 callbacks.event_input = snd_opl3_oss_event_input; in snd_opl3_oss_create_port()
92 callbacks.private_free = snd_opl3_oss_free_port; in snd_opl3_oss_create_port()
93 callbacks.private_data = opl3; in snd_opl3_oss_create_port()
99 opl3->oss_chset->port = snd_seq_event_port_attach(opl3->seq_client, &callbacks, in snd_opl3_oss_create_port()
/linux-4.1.27/Documentation/usb/
Dcallbacks.txt1 What callbacks will usbcore do?
4 Usbcore will call into a driver through callbacks defined in the driver
7 callbacks are completely independent of each other. Information on the
10 The callbacks defined in the driver structure are:
12 1. Hotplugging callbacks:
27 3. Power management (PM) callbacks:
40 reason. Sysfs is preferred these days. The PM callbacks are covered
46 All callbacks are mutually exclusive. There's no need for locking
47 against other USB callbacks. All callbacks are called from a task
52 Hotplugging callbacks
[all …]
Danchors.txt4 A USB driver needs to support some callbacks requiring
Dusbmon.txt161 is reported. For callbacks, actual length is reported.
163 - Data Length. For submissions, this is the requested length. For callbacks,
DWUSB-Design-overview.txt257 bandwidth management done by the UWB stack will include callbacks to the
374 callbacks for the URBs issued from here are the ones that will declare
/linux-4.1.27/fs/dlm/
Dast.c219 struct dlm_callback callbacks[DLM_CALLBACKS_SIZE]; in dlm_callback_work() local
222 memset(&callbacks, 0, sizeof(callbacks)); in dlm_callback_work()
233 rv = dlm_rem_lkb_callback(ls, lkb, &callbacks[i], &resid); in dlm_callback_work()
251 if (!callbacks[i].seq) in dlm_callback_work()
253 if (callbacks[i].flags & DLM_CB_SKIP) { in dlm_callback_work()
255 } else if (callbacks[i].flags & DLM_CB_BAST) { in dlm_callback_work()
256 bastfn(lkb->lkb_astparam, callbacks[i].mode); in dlm_callback_work()
257 } else if (callbacks[i].flags & DLM_CB_CAST) { in dlm_callback_work()
258 lkb->lkb_lksb->sb_status = callbacks[i].sb_status; in dlm_callback_work()
259 lkb->lkb_lksb->sb_flags = callbacks[i].sb_flags; in dlm_callback_work()
/linux-4.1.27/net/ipv6/
Dip6_offload.c110 if (likely(ops && ops->callbacks.gso_segment)) { in ipv6_gso_segment()
112 segs = ops->callbacks.gso_segment(skb, features); in ipv6_gso_segment()
197 if (!ops || !ops->callbacks.gro_receive) { in ipv6_gro_receive()
205 if (!ops || !ops->callbacks.gro_receive) in ipv6_gro_receive()
250 pp = ops->callbacks.gro_receive(head, skb); in ipv6_gro_receive()
272 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in ipv6_gro_complete()
275 err = ops->callbacks.gro_complete(skb, nhoff); in ipv6_gro_complete()
285 .callbacks = {
293 .callbacks = {
Dtcpv6_offload.c68 .callbacks = {
Dudp_offload.c174 .callbacks = {
/linux-4.1.27/fs/afs/
Dcallback.c195 struct afs_callback callbacks[]) in afs_break_callbacks() argument
202 for (; count > 0; callbacks++, count--) { in afs_break_callbacks()
204 callbacks->fid.vid, in afs_break_callbacks()
205 callbacks->fid.vnode, in afs_break_callbacks()
206 callbacks->fid.unique, in afs_break_callbacks()
207 callbacks->version, in afs_break_callbacks()
208 callbacks->expiry, in afs_break_callbacks()
209 callbacks->type in afs_break_callbacks()
211 afs_break_one_callback(server, &callbacks->fid); in afs_break_callbacks()
/linux-4.1.27/Documentation/RCU/
Drcubarrier.txt55 If we unload the module while some RCU callbacks are pending,
56 the CPUs executing these callbacks are going to be severely
62 grace period to elapse, it does not wait for the callbacks to complete.
66 heavy RCU-callback load, then some of the callbacks might be deferred
75 callbacks to complete. Please note that rcu_barrier() does -not- imply
76 synchronize_rcu(), in particular, if there are no RCU callbacks queued
82 1. Prevent any new RCU callbacks from being posted.
153 52 /* Wait for all RCU callbacks to fire. */
166 Line 6 sets a global variable that prevents any RCU callbacks from
168 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
[all …]
DUP.txt72 It is far better to guarantee that callbacks are invoked
79 Quick Quiz #2: What locking restriction must RCU callbacks respect?
86 infrastructure -must- respect grace periods, and -must- invoke callbacks
107 What locking restriction must RCU callbacks respect?
117 then, since RCU callbacks can be invoked from softirq context,
123 callbacks acquire locks directly. However, a great many RCU
124 callbacks do acquire locks -indirectly-, for example, via
Dtrace.txt131 o "ql" is the number of RCU callbacks currently residing on
132 this CPU. The first number is the number of "lazy" callbacks
134 after the "/" is the total number of callbacks, lazy or not.
135 These counters count callbacks regardless of what phase of
143 "N" Indicates that there are callbacks queued that are not
148 "R" Indicates that there are callbacks queued that are
151 "W" Indicates that there are callbacks queued that are
154 "D" Indicates that there are callbacks queued that have
156 thus waiting to be invoked. Note that callbacks in
163 If there are no callbacks in a given one of the above states,
[all …]
Dchecklist.txt285 exhaustion when any given CPU has too many callbacks, a determined
288 offload all of its RCU callbacks onto a single CPU, or if the
343 13. RCU callbacks can be and are executed in parallel. In many cases,
347 if the callbacks do manipulate a shared data structure, they
351 RCU callbacks are -usually- executed on the same CPU that executed
Dstallwarn.txt149 prints the number of non-lazy callbacks posted since the last call to
151 no non-lazy callbacks ("." is printed otherwise, as shown above) and
215 This will prevent RCU callbacks from ever being invoked,
Dtorture.txt62 RCU callbacks (and corresponding kthreads) to use for
DRTFP.txt2086 ,Title="[{RFC}][{PATCH}] rcu classic: new algorithm for callbacks-processing"
2095 for RCU callbacks and also pulling common code into
2357 of RCU callbacks.
2753 ,Title="Relocating RCU callbacks"
DwhatisRCU.txt314 to their callers and (2) call_rcu() callbacks may be invoked. Efficient
/linux-4.1.27/drivers/rtc/
Drtc-hid-sensor-time.c37 struct hid_sensor_hub_callbacks callbacks; member
268 time_state->callbacks.send_event = hid_time_proc_event; in hid_time_probe()
269 time_state->callbacks.capture_sample = hid_time_capture_sample; in hid_time_probe()
270 time_state->callbacks.pdev = pdev; in hid_time_probe()
272 &time_state->callbacks); in hid_time_probe()
/linux-4.1.27/net/ipv4/
Dudp_offload.c161 if (!ops || !ops->callbacks.gso_segment) in skb_udp_tunnel_segment()
163 gso_inner_segment = ops->callbacks.gso_segment; in skb_udp_tunnel_segment()
315 uo_priv->offload->callbacks.gro_receive) in udp_gro_receive()
342 pp = uo_priv->offload->callbacks.gro_receive(head, skb, in udp_gro_receive()
393 uo_priv->offload->callbacks.gro_complete) in udp_gro_complete()
399 err = uo_priv->offload->callbacks.gro_complete(skb, in udp_gro_complete()
432 .callbacks = {
Dfou.c188 if (!ops || !ops->callbacks.gro_receive) in fou_gro_receive()
191 pp = ops->callbacks.gro_receive(head, skb); in fou_gro_receive()
212 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in fou_gro_complete()
215 err = ops->callbacks.gro_complete(skb, nhoff); in fou_gro_complete()
355 if (WARN_ON(!ops || !ops->callbacks.gro_receive)) in gue_gro_receive()
358 pp = ops->callbacks.gro_receive(head, skb); in gue_gro_receive()
386 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in gue_gro_complete()
389 err = ops->callbacks.gro_complete(skb, nhoff + guehlen); in gue_gro_complete()
432 fou->udp_offloads.callbacks.gro_receive = fou_gro_receive; in fou_encap_init()
433 fou->udp_offloads.callbacks.gro_complete = fou_gro_complete; in fou_encap_init()
[all …]
Dgre_offload.c217 pp = ptype->callbacks.gro_receive(head, skb); in gre_gro_receive()
248 err = ptype->callbacks.gro_complete(skb, nhoff + grehlen); in gre_gro_complete()
258 .callbacks = {
Dgeneve.c206 pp = ptype->callbacks.gro_receive(head, skb); in geneve_gro_receive()
234 err = ptype->callbacks.gro_complete(skb, nhoff + gh_len); in geneve_gro_complete()
358 gs->udp_offloads.callbacks.gro_receive = geneve_gro_receive; in geneve_socket_create()
359 gs->udp_offloads.callbacks.gro_complete = geneve_gro_complete; in geneve_socket_create()
Daf_inet.c1265 if (likely(ops && ops->callbacks.gso_segment)) in inet_gso_segment()
1266 segs = ops->callbacks.gso_segment(skb, features); in inet_gso_segment()
1320 if (!ops || !ops->callbacks.gro_receive) in inet_gro_receive()
1380 pp = ops->callbacks.gro_receive(head, skb); in inet_gro_receive()
1418 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in inet_gro_complete()
1425 err = ops->callbacks.gro_complete(skb, nhoff + sizeof(*iph)); in inet_gro_complete()
1639 .callbacks = {
1647 .callbacks = {
Dtcp_offload.c317 .callbacks = {
/linux-4.1.27/drivers/iio/orientation/
Dhid-sensor-rotation.c30 struct hid_sensor_hub_callbacks callbacks; member
287 rot_state->callbacks.send_event = dev_rot_proc_event; in hid_dev_rot_probe()
288 rot_state->callbacks.capture_sample = dev_rot_capture_sample; in hid_dev_rot_probe()
289 rot_state->callbacks.pdev = pdev; in hid_dev_rot_probe()
292 &rot_state->callbacks); in hid_dev_rot_probe()
Dhid-sensor-incl-3d.c42 struct hid_sensor_hub_callbacks callbacks; member
380 incl_state->callbacks.send_event = incl_3d_proc_event; in hid_incl_3d_probe()
381 incl_state->callbacks.capture_sample = incl_3d_capture_sample; in hid_incl_3d_probe()
382 incl_state->callbacks.pdev = pdev; in hid_incl_3d_probe()
385 &incl_state->callbacks); in hid_incl_3d_probe()
/linux-4.1.27/drivers/virtio/
Dvirtio_pci_common.c298 vq_callback_t *callbacks[], in vp_try_to_find_vqs() argument
321 if (callbacks[i]) in vp_try_to_find_vqs()
339 } else if (!callbacks[i] || !vp_dev->msix_enabled) in vp_try_to_find_vqs()
345 vqs[i] = vp_setup_vq(vdev, i, callbacks[i], names[i], msix_vec); in vp_try_to_find_vqs()
378 vq_callback_t *callbacks[], in vp_find_vqs() argument
384 err = vp_try_to_find_vqs(vdev, nvqs, vqs, callbacks, names, true, true); in vp_find_vqs()
388 err = vp_try_to_find_vqs(vdev, nvqs, vqs, callbacks, names, in vp_find_vqs()
393 return vp_try_to_find_vqs(vdev, nvqs, vqs, callbacks, names, in vp_find_vqs()
Dvirtio_pci_common.h139 vq_callback_t *callbacks[],
Dvirtio_balloon.c386 vq_callback_t *callbacks[] = { balloon_ack, balloon_ack, stats_request }; in init_vqs() local
395 err = vb->vdev->config->find_vqs(vb->vdev, nvqs, vqs, callbacks, names); in init_vqs()
Dvirtio_mmio.c483 vq_callback_t *callbacks[], in vm_find_vqs() argument
496 vqs[i] = vm_setup_vq(vdev, i, callbacks[i], names[i]); in vm_find_vqs()
Dvirtio_pci_modern.c425 vq_callback_t *callbacks[], in vp_modern_find_vqs() argument
430 int rc = vp_find_vqs(vdev, nvqs, vqs, callbacks, names); in vp_modern_find_vqs()
/linux-4.1.27/drivers/iio/pressure/
Dhid-sensor-press.c36 struct hid_sensor_hub_callbacks callbacks; member
324 press_state->callbacks.send_event = press_proc_event; in hid_press_probe()
325 press_state->callbacks.capture_sample = press_capture_sample; in hid_press_probe()
326 press_state->callbacks.pdev = pdev; in hid_press_probe()
328 &press_state->callbacks); in hid_press_probe()
/linux-4.1.27/drivers/iio/light/
Dhid-sensor-prox.c36 struct hid_sensor_hub_callbacks callbacks; member
314 prox_state->callbacks.send_event = prox_proc_event; in hid_prox_probe()
315 prox_state->callbacks.capture_sample = prox_capture_sample; in hid_prox_probe()
316 prox_state->callbacks.pdev = pdev; in hid_prox_probe()
318 &prox_state->callbacks); in hid_prox_probe()
Dhid-sensor-als.c37 struct hid_sensor_hub_callbacks callbacks; member
325 als_state->callbacks.send_event = als_proc_event; in hid_als_probe()
326 als_state->callbacks.capture_sample = als_capture_sample; in hid_als_probe()
327 als_state->callbacks.pdev = pdev; in hid_als_probe()
329 &als_state->callbacks); in hid_als_probe()
/linux-4.1.27/net/mpls/
Dmpls_gso.c65 .callbacks = {
72 .callbacks = {
/linux-4.1.27/Documentation/power/
Dnotifiers.txt7 or even .prepare() and .complete() callbacks are not suitable for this purpose.
25 hibernation. Device drivers' restore callbacks have
33 Device drivers' restore callbacks have been executed
39 suspend. Device drivers' resume callbacks have been
Dpci.txt273 pointers to several device power management callbacks:
295 These callbacks are executed by the PM core in various situations related to
296 device power management and they, in turn, execute power management callbacks
302 that these callbacks operate on:
354 Namely, it provides subsystem-level callbacks:
422 callbacks for this purpose. They are executed in phases such that each phase
434 The following PCI bus type's callbacks, respectively, are used in these phases:
449 pointers to the driver's callbacks), pci_pm_default_suspend() is called, which
473 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
484 PCI device drivers (that don't implement legacy power management callbacks) are
[all …]
Druntime_pm.txt23 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
31 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
37 There are three device runtime PM callbacks defined in 'struct dev_pm_ops':
47 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
66 priority order of callbacks from high to low is: PM domain, device type, class
68 a low-priority one. The PM domain, bus type, device type and class callbacks
69 are referred to as subsystem-level callbacks in what follows.
71 By default, the callbacks are always invoked in process context with interrupts
74 and ->runtime_idle() callbacks for the given device in atomic context with
158 that the following constraints are met with respect to runtime PM callbacks for
[all …]
Ddevices.txt273 hibernation state ("suspend-to-disk"). Each phase involves executing callbacks
275 support all these callbacks and not all drivers use all the callbacks. The
280 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
282 dev->driver->pm). These callbacks are regarded by the PM core as mutually
283 exclusive. Moreover, PM domain callbacks always take precedence over all of the
284 other callbacks and, for example, type callbacks take precedence over bus, class
285 and driver callbacks. To be precise, the following rules are used to determine
300 This allows PM domains and device types to override callbacks provided by bus
303 The PM domain, type, class and bus callbacks may in turn invoke device- or
380 If any of these callbacks returns an error, the system won't enter the desired
[all …]
Dsuspend-and-cpuhotplug.txt65 ======> by running all registered callbacks. |
134 ======> by running all registered callbacks.
258 inappropriate code by the callbacks registered for such CPU hotplug events.
Dsuspend-and-interrupts.txt12 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
29 callbacks for devices). The function doing that is resume_device_irqs().
Dbasic-pm-debugging.txt17 modes causes the PM core to skip some platform-related callbacks which on ACPI
Dfreezing-of-tasks.txt119 amounts of memory from their .suspend() callbacks before hibernation, but this
/linux-4.1.27/drivers/iio/accel/
Dhid-sensor-accel-3d.c42 struct hid_sensor_hub_callbacks callbacks; member
364 accel_state->callbacks.send_event = accel_3d_proc_event; in hid_accel_3d_probe()
365 accel_state->callbacks.capture_sample = accel_3d_capture_sample; in hid_accel_3d_probe()
366 accel_state->callbacks.pdev = pdev; in hid_accel_3d_probe()
368 &accel_state->callbacks); in hid_accel_3d_probe()
/linux-4.1.27/drivers/iio/gyro/
Dhid-sensor-gyro-3d.c42 struct hid_sensor_hub_callbacks callbacks; member
361 gyro_state->callbacks.send_event = gyro_3d_proc_event; in hid_gyro_3d_probe()
362 gyro_state->callbacks.capture_sample = gyro_3d_capture_sample; in hid_gyro_3d_probe()
363 gyro_state->callbacks.pdev = pdev; in hid_gyro_3d_probe()
365 &gyro_state->callbacks); in hid_gyro_3d_probe()
/linux-4.1.27/arch/x86/xen/
Dmulticalls.c49 } callbacks[MC_BATCH]; member
121 struct callback *cb = &b->callbacks[i]; in xen_mc_flush()
205 cb = &b->callbacks[b->cbidx++]; in xen_mc_callback()
/linux-4.1.27/drivers/md/
Ddm-snap-persistent.c160 struct commit_callback *callbacks; member
603 vfree(ps->callbacks); in persistent_dtr()
628 ps->callbacks = dm_vcalloc(ps->exceptions_per_area, in persistent_read_metadata()
629 sizeof(*ps->callbacks)); in persistent_read_metadata()
630 if (!ps->callbacks) in persistent_read_metadata()
719 cb = ps->callbacks + ps->callback_count++; in persistent_commit_exception()
754 cb = ps->callbacks + i; in persistent_commit_exception()
870 ps->callbacks = NULL; in persistent_ctr()
Ddm-raid.c70 struct dm_target_callbacks callbacks; member
746 struct raid_set *rs = container_of(cb, struct raid_set, callbacks); in raid_is_congested()
1299 rs->callbacks.congested_fn = raid_is_congested; in raid_ctr()
1300 dm_table_add_target_callbacks(ti->table, &rs->callbacks); in raid_ctr()
1317 list_del_init(&rs->callbacks.list); in raid_dtr()
Ddm-era-target.c1142 struct dm_target_callbacks callbacks; member
1388 struct era *era = container_of(cb, struct era, callbacks); in era_is_congested()
1520 era->callbacks.congested_fn = era_is_congested; in era_ctr()
1521 dm_table_add_target_callbacks(ti->table, &era->callbacks); in era_ctr()
Ddm-cache-target.c180 struct dm_target_callbacks callbacks; member
1892 struct cache *cache = container_of(cb, struct cache, callbacks); in cache_is_congested()
2378 cache->callbacks.congested_fn = cache_is_congested; in cache_create()
2379 dm_table_add_target_callbacks(ti->table, &cache->callbacks); in cache_create()
Ddm-thin.c278 struct dm_target_callbacks callbacks; member
2380 struct pool_c *pt = container_of(cb, struct pool_c, callbacks); in pool_is_congested()
2964 pt->callbacks.congested_fn = pool_is_congested; in pool_ctr()
2965 dm_table_add_target_callbacks(ti->table, &pt->callbacks); in pool_ctr()
/linux-4.1.27/drivers/net/wireless/ath/ath10k/
Dhif.h84 struct ath10k_hif_cb *callbacks);
167 struct ath10k_hif_cb *callbacks) in ath10k_hif_set_callbacks() argument
169 ar->hif.ops->set_callbacks(ar, callbacks); in ath10k_hif_set_callbacks()
Dpci.c1078 struct ath10k_hif_cb *callbacks) in ath10k_pci_hif_set_callbacks() argument
1084 memcpy(&ar_pci->msg_callbacks_current, callbacks, in ath10k_pci_hif_set_callbacks()
/linux-4.1.27/drivers/iio/magnetometer/
Dhid-sensor-magn-3d.c46 struct hid_sensor_hub_callbacks callbacks; member
477 magn_state->callbacks.send_event = magn_3d_proc_event; in hid_magn_3d_probe()
478 magn_state->callbacks.capture_sample = magn_3d_capture_sample; in hid_magn_3d_probe()
479 magn_state->callbacks.pdev = pdev; in hid_magn_3d_probe()
481 &magn_state->callbacks); in hid_magn_3d_probe()
/linux-4.1.27/Documentation/phy/
Dsamsung-usb2.txt22 the probe function and provides two callbacks to the Generic PHY
23 Framework. This two callbacks are used to power on and power off the
26 specific callbacks. The specific SoC version is selected by choosing
102 These two callbacks are used to power on and power off the phy
/linux-4.1.27/drivers/isdn/pcbit/
DMakefile9 pcbit-y := module.o edss1.o drv.o layer2.o capi.o callbacks.o
/linux-4.1.27/Documentation/pcmcia/
Dlocking.txt16 The following functions and callbacks to struct pcmcia_socket must
33 The following functions and callbacks to struct pcmcia_socket must
/linux-4.1.27/Documentation/isdn/
DREADME.concap104 The network interface driver accesses those primitives via callbacks
152 The encapsulation protocol accesses those primitives via callbacks
178 struct concap_device_ops *dops; /* callbacks provided by device */
179 struct concap_proto_ops *pops; /* callbacks provided by us */
195 only by means of the callbacks referred to by the dops pointer.
206 to provide the device specific callbacks
208 struct concap_proto *cprot; /* callbacks provided by protocol */
DINTERFACE13 the fields. All further communication is done via callbacks using
49 invoking the other callbacks.
725 for free channels. The HL driver itself never delivers STAT callbacks for
/linux-4.1.27/net/ethernet/
Deth.c437 pp = ptype->callbacks.gro_receive(head, skb); in eth_gro_receive()
461 err = ptype->callbacks.gro_complete(skb, nhoff + in eth_gro_complete()
471 .callbacks = {
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-firmware-gsmi7 triggers. Some of the callbacks are similar to those
13 these firmware callbacks. Currently, this functionality
Dsysfs-devices-online7 callbacks. The number read from it (0 or 1) reflects the value
Dsysfs-power153 drivers' suspend and resume callbacks to be executed in parallel
183 made by device drivers' "freeze" callbacks, in bytes.
Dsysfs-devices-power59 enable or diasble the device's suspend and resume callbacks to
/linux-4.1.27/include/linux/
Dvirtio_config.h72 vq_callback_t *callbacks[],
156 vq_callback_t *callbacks[] = { c }; in virtio_find_single_vq() local
159 int err = vdev->config->find_vqs(vdev, 1, &vq, callbacks, names); in virtio_find_single_vq()
Dlapb.h48 const struct lapb_register_struct *callbacks);
Dperf_event.h820 extern int perf_register_guest_info_callbacks(struct perf_guest_info_callbacks *callbacks);
821 extern int perf_unregister_guest_info_callbacks(struct perf_guest_info_callbacks *callbacks);
949 (struct perf_guest_info_callbacks *callbacks) { return 0; } in perf_register_guest_info_callbacks() argument
951 (struct perf_guest_info_callbacks *callbacks) { return 0; } in perf_unregister_guest_info_callbacks() argument
Dvringh.h74 struct vringh *vrhs[], vrh_callback_t *callbacks[]);
Dnetdevice.h1993 struct offload_callbacks callbacks; member
2011 struct udp_offload_callbacks callbacks; member
/linux-4.1.27/Documentation/gpio/
Ddriver.txt94 struct gpio_chip, as everything happens directly in the callbacks.
114 associated irqdomain and resource allocation callbacks, the gpiolib has
119 the struct gpio_chip* for the chip to all IRQ callbacks, so the callbacks
146 callbacks from the GPIO and irqchip APIs. Do not rely on gpiod_to_irq() having
169 typically be called in the .startup() and .shutdown() callbacks from the
Dgpio-legacy.txt615 such gpio_chip controllers to provide setup() and teardown() callbacks to
616 board specific code; those board specific callbacks would register devices
/linux-4.1.27/drivers/block/
Dvirtio_blk.c384 vq_callback_t **callbacks; in init_vq() local
406 callbacks = kmalloc(sizeof(*callbacks) * num_vqs, GFP_KERNEL); in init_vq()
407 if (!callbacks) in init_vq()
415 callbacks[i] = virtblk_done; in init_vq()
421 err = vdev->config->find_vqs(vdev, num_vqs, vqs, callbacks, names); in init_vq()
434 kfree(callbacks); in init_vq()
/linux-4.1.27/drivers/scsi/
Dvirtio_scsi.c893 vq_callback_t **callbacks; in virtscsi_init() local
899 callbacks = kmalloc(num_vqs * sizeof(vq_callback_t *), GFP_KERNEL); in virtscsi_init()
902 if (!callbacks || !vqs || !names) { in virtscsi_init()
907 callbacks[0] = virtscsi_ctrl_done; in virtscsi_init()
908 callbacks[1] = virtscsi_event_done; in virtscsi_init()
912 callbacks[i] = virtscsi_req_done; in virtscsi_init()
917 err = vdev->config->find_vqs(vdev, num_vqs, vqs, callbacks, names); in virtscsi_init()
936 kfree(callbacks); in virtscsi_init()
/linux-4.1.27/drivers/net/wireless/brcm80211/brcmsmac/
Dmac80211_if.c316 while (atomic_read(&wl->callbacks) > 0) in brcms_free()
1122 atomic_set(&wl->callbacks, 0); in brcms_attach()
1410 uint callbacks, ret_val = 0; in brcms_down() local
1414 callbacks = atomic_read(&wl->callbacks) - ret_val; in brcms_down()
1422 SPINWAIT((atomic_read(&wl->callbacks) > callbacks), 100 * 1000); in brcms_down()
1439 atomic_inc(&t->wl->callbacks); in _brcms_timer()
1450 atomic_dec(&t->wl->callbacks); in _brcms_timer()
1507 atomic_inc(&t->wl->callbacks); in brcms_add_timer()
1525 atomic_dec(&t->wl->callbacks); in brcms_del_timer()
Dmac80211_if.h77 atomic_t callbacks; /* # outstanding callback functions */ member
Dmain.c4876 uint callbacks; in brcms_c_detach() local
4884 callbacks = 0; in brcms_c_detach()
4886 callbacks++; in brcms_c_detach()
4895 return callbacks; in brcms_c_detach()
5110 uint callbacks = 0; in brcms_c_down_del_timer() local
5112 return callbacks; in brcms_c_down_del_timer()
5118 uint callbacks = 0; in brcms_b_bmac_down_prep() local
5121 return callbacks; in brcms_b_bmac_down_prep()
5136 callbacks += wlc_phy_down(wlc_hw->band->pi); in brcms_b_bmac_down_prep()
5138 return callbacks; in brcms_b_bmac_down_prep()
[all …]
/linux-4.1.27/tools/perf/util/
Dunwind-libdw.c145 static const Dwfl_Thread_Callbacks callbacks = { variable
197 if (!dwfl_attach_state(ui.dwfl, EM_NONE, thread->tid, &callbacks, &ui)) in unwind__get_entries()
/linux-4.1.27/Documentation/networking/
Dnetdev-features.txt58 ndo_*_features callbacks are called with rtnl_lock held. Missing callbacks
63 from ndo_*_features callbacks. netdev->features should not be modified by
138 protect against other callbacks (the rules you need to find out).
Dnfc.txt57 of the set of supported NFC protocols and the set of ops callbacks. The ops
58 callbacks that must be implemented are the following:
Dlapb-module.txt15 callbacks from the module to indicate important state changes, and
109 callbacks, and is used by the device driver in all calls to the LAPB module.
198 These callbacks are functions provided by the device driver for the LAPB
Dstmmac.txt182 o setup/init/exit: callbacks used for calling a custom initialization;
187 exit callbacks. init/exit callbacks should not use or modify
/linux-4.1.27/arch/mips/include/asm/octeon/
Dcvmx-spi.h161 extern void cvmx_spi_get_callbacks(cvmx_spi_callbacks_t *callbacks);
/linux-4.1.27/drivers/hid/
Dhid-sensor-custom.c47 struct hid_sensor_hub_callbacks callbacks; member
772 sensor_inst->callbacks.capture_sample = hid_sensor_capture_sample; in hid_sensor_custom_probe()
773 sensor_inst->callbacks.send_event = hid_sensor_send_event; in hid_sensor_custom_probe()
774 sensor_inst->callbacks.pdev = pdev; in hid_sensor_custom_probe()
780 &sensor_inst->callbacks); in hid_sensor_custom_probe()
/linux-4.1.27/Documentation/fault-injection/
Dnotifier-error-inject.txt5 specified notifier chain callbacks. It is useful to test the error handling of
17 injecting artificial errors to CPU notifier chain callbacks.
/linux-4.1.27/drivers/virt/
DKconfig30 4) A kernel interface for receiving callbacks when a managed
/linux-4.1.27/Documentation/driver-model/
Ddriver.txt21 the callbacks as possible, though each is optional.
102 let the bus wrapper fill in the fields. For the callbacks, the bus can
103 define generic callbacks that forward the call to the bus-specific
104 callbacks of the drivers.
Ddesign-patterns.txt19 means that the probe() function and all callbacks need to be reentrant.
Doverview.txt24 of common callbacks, such as device discovery during bus probing, bus
Dplatform.txt191 command line. This will execute all matching early_param() callbacks.
/linux-4.1.27/include/net/
Dprotocol.h72 struct offload_callbacks callbacks; member
Dlapb.h98 const struct lapb_register_struct *callbacks; member
/linux-4.1.27/Documentation/cpuidle/
Dgovernor.txt12 any given time. cpuidle core uses different callbacks to the governor.
/linux-4.1.27/drivers/firmware/google/
DKconfig18 Say Y here if you want to enable SMI callbacks for Google
/linux-4.1.27/drivers/remoteproc/
Dremoteproc_virtio.c149 vq_callback_t *callbacks[], in rproc_virtio_find_vqs() argument
156 vqs[i] = rp_find_vq(vdev, i, callbacks[i], names[i]); in rproc_virtio_find_vqs()
/linux-4.1.27/drivers/net/
Dvirtio_net.c1527 vq_callback_t **callbacks; in virtnet_find_vqs() local
1544 callbacks = kmalloc(total_vqs * sizeof(*callbacks), GFP_KERNEL); in virtnet_find_vqs()
1545 if (!callbacks) in virtnet_find_vqs()
1553 callbacks[total_vqs - 1] = NULL; in virtnet_find_vqs()
1559 callbacks[rxq2vq(i)] = skb_recv_done; in virtnet_find_vqs()
1560 callbacks[txq2vq(i)] = skb_xmit_done; in virtnet_find_vqs()
1567 ret = vi->vdev->config->find_vqs(vi->vdev, total_vqs, vqs, callbacks, in virtnet_find_vqs()
1584 kfree(callbacks); in virtnet_find_vqs()
1592 kfree(callbacks); in virtnet_find_vqs()
Dvxlan.c2536 vs->udp_offloads.callbacks.gro_receive = vxlan_gro_receive; in vxlan_socket_create()
2537 vs->udp_offloads.callbacks.gro_complete = vxlan_gro_complete; in vxlan_socket_create()
/linux-4.1.27/Documentation/scsi/
Dscsi_eh.txt18 [2-1] EH through fine-grained callbacks
168 - Fine-grained EH callbacks
169 LLDD can implement fine-grained EH callbacks and let SCSI
170 midlayer drive error handling and call appropriate callbacks.
193 [2-1] EH through fine-grained callbacks
207 hostt EH callbacks. Callbacks may be omitted and omitted ones are
284 EH through fine-grained callbacks start from scsi_unjam_host().
Dlibsas.txt38 notify_* event callbacks).
105 of your callbacks and passes you a phy. If the sas_phy is
Dscsi_mid_low_api.txt227 slave_configure() callbacks). Such instances are "owned" by the mid-level.
407 * this call can lead to slave_alloc() and slave_configure() callbacks
/linux-4.1.27/Documentation/fb/
Dep93xx-fb.txt79 Platform callbacks
83 callbacks: setup, teardown and blank. The setup and teardown functions
/linux-4.1.27/Documentation/PCI/
Dpcieaer-howto.txt88 the AER capability structure within its device and to provide callbacks.
134 3.2. Provide callbacks
152 3.2.2 PCI error-recovery callbacks
154 The PCI Express AER Root driver uses error callbacks to coordinate
163 definitions of the callbacks.
Dpci-error-recovery.txt102 A driver does not have to implement all of these callbacks; however,
345 PCI_ERS_RESULT_RECOVERED from one of the 3 previous callbacks.
379 The way the callbacks are called is platform policy. A platform with
/linux-4.1.27/Documentation/timers/
DNO_HZ.txt141 Finally, adaptive-ticks CPUs must have their RCU callbacks offloaded.
188 common being when that CPU has RCU callbacks pending.
193 that the RCU callbacks are processed in a timely fashion.
209 CPUs to be offloaded. Note that the callbacks will be
213 callbacks run on, along with their scheduling priority
224 The offloaded CPUs will never queue RCU callbacks, and therefore RCU
313 simply offloading RCU callbacks from all CPUs and pinning them
Dtimer_stats.txt24 - the number of events (callbacks)
Dhighres.txt195 The softirq for running the hrtimer queues and executing the callbacks has been
/linux-4.1.27/drivers/s390/kvm/
Dkvm_virtio.c257 vq_callback_t *callbacks[], in kvm_find_vqs() argument
268 vqs[i] = kvm_find_vq(vdev, i, callbacks[i], names[i]); in kvm_find_vqs()
Dvirtio_ccw.c620 vq_callback_t *callbacks[], in virtio_ccw_find_vqs() argument
633 vqs[i] = virtio_ccw_setup_vq(vdev, i, callbacks[i], names[i], in virtio_ccw_find_vqs()
/linux-4.1.27/Documentation/acpi/
Dscan_handlers.txt44 maintained by the ACPI core and the .attach() and .detach() callbacks are
66 callbacks from the scan handlers of all device nodes in the given namespace
/linux-4.1.27/Documentation/sound/alsa/
Dhda_codec.txt60 for the last command. These two callbacks are mandatory and have to
203 prepare callbacks. When a negative value is returned, some error
270 The suspend and resume callbacks are for power management.
320 The input MUX helper callbacks for such a control are provided, too:
/linux-4.1.27/Documentation/
Dkernel-per-CPU-kthreads.txt136 1. Offload callbacks and keep the CPU in either dyntick-idle or
228 Purpose: Execute RCU callbacks in CONFIG_RCU_BOOST=y kernels.
240 which offloads all RCU callbacks to kthreads that can be moved
246 another way of preventing any callbacks from being queued on the
251 Purpose: Offload RCU callbacks from the corresponding CPU.
Drbtree.txt224 In both cases, the callbacks are provided through struct rb_augment_callbacks.
225 3 callbacks must be defined:
239 copy callbacks, which results in a large function, so each augmented rbtree
306 Insertion/removal are defined using the following augmented callbacks:
Dhwspinlock.txt287 6. Implementation callbacks
289 There are three possible callbacks defined in 'struct hwspinlock_ops':
297 The first two callbacks are mandatory:
DIRQ-domain.txt63 callbacks) then it can be directly obtained from irq_data->hwirq.
196 3) new callbacks are added to struct irq_domain_ops to support hierarchy
Dclk.txt25 callbacks registered with struct clk_ops and the corresponding
247 clk_ops callbacks, nor must it be included by any logic which pokes
Dremoteproc.txt139 5. Implementation callbacks
141 These callbacks should be provided by platform-specific remoteproc
Deisa.txt34 implements the necessary callbacks to probe and release devices
Dvfio.txt262 a VFIO bus driver. The driver provides an ops structure for callbacks
280 callbacks are issued when a new file descriptor is created for a
Dkernel-parameters.txt2985 Invocation of these CPUs' RCU callbacks will
2998 make these kthreads poll for callbacks.
3006 Set maximum number of finished RCU callbacks to
3056 Set threshold of queued RCU callbacks beyond which
3060 Set threshold of queued RCU callbacks below which
3065 RCU callbacks (RCU_FAST_NO_HZ=y).
3069 only "lazy" RCU callbacks (RCU_FAST_NO_HZ=y).
3070 Lazy RCU callbacks are those which RCU can
3079 bursts of callbacks within a given callback-flood
3088 Set the number of callbacks to be registered
[all …]
Dvme_api.txt304 The VME API provides functions to attach and detach callbacks to specific VME
Drpmsg.txt177 additional rpmsg addresses, and bind them to different rx callbacks.
Dmedia-framework.txt372 in the end provide a way to use driver-specific callbacks.
Dcpu-hotplug.txt363 callbacks as well as initialize the already online CPUs.
Dparport-lowlevel.txt346 This function will register three callbacks into your driver:
DIPMI.txt254 so be careful using the callbacks. This also allows to you pass in a
Dpinctrl.txt211 The pin configuration driver implements callbacks for changing pin
/linux-4.1.27/Documentation/hid/
Dhid-transport.txt63 device. Once a device is registered with HID core, the callbacks provided via
70 provided callbacks.
214 Once hid_add_device() is entered, HID core might use the callbacks provided in
223 driver callbacks.
228 The available HID callbacks are:
Dhid-sensor.txt79 Each processing driver can use this structure to set some callbacks.
91 Registers callbacks for an usage id. The callback functions are not allowed
98 Removes callbacks for an usage id.
/linux-4.1.27/Documentation/arm/
Dfirmware.txt11 with appropriate callbacks and then registering it with register_firmware_ops()
/linux-4.1.27/Documentation/video4linux/
Dvideobuf50 Data structures, callbacks, and initialization
65 The next step is to write four simple callbacks to help videobuf deal with
136 videobuf calls into the implementation of the other driver callbacks. The
168 device, ops is the set of callbacks as described above, dev is the device
237 The V4L2 API includes a very long list of driver callbacks to respond to
Dv4l2-framework.txt399 The group ID gives the bridge driver more control how callbacks are called.
440 called. All three callbacks are optional.
545 the remove() callbacks are called of the i2c devices on that adapter.
740 wait_finish callbacks to unlock/lock if applicable. If you use the queue->lock
1058 replace() callbacks which drivers can set. These callbacks are called when
1070 A good example of these replace/merge callbacks is in v4l2-event.c:
1071 ctrls_replace() and ctrls_merge() callbacks for the control event.
1073 Note: these callbacks can be called from interrupt context, so they must be
1096 The ops argument allows the driver to specify a number of callbacks:
1102 All 4 callbacks are optional, if you don't want to specify any callbacks
/linux-4.1.27/arch/mips/cavium-octeon/executive/
Dcvmx-spi.c76 void cvmx_spi_get_callbacks(cvmx_spi_callbacks_t *callbacks) in cvmx_spi_get_callbacks() argument
78 memcpy(callbacks, &cvmx_spi_callbacks, sizeof(cvmx_spi_callbacks)); in cvmx_spi_get_callbacks()
/linux-4.1.27/Documentation/filesystems/
Drelay.txt160 callbacks, private_data)
175 callbacks:
217 Here are some typical definitions for these callbacks, in this case
244 * relay interface callbacks
395 define any callbacks, or doesn't define the subbuf_start() callback,
465 Finally, there are a couple of utility callbacks that can be used for
Dporting368 filesystem callbacks, the vfs drops out of rcu-walk mode before the fs call, so
370 the benefits of rcu-walk mode. We will begin to add filesystem callbacks that
462 taken anymore, so verify that your callbacks do not rely on it (none
Dgfs2-glocks.txt77 There is a plan to try and remove the go_lock and go_unlock callbacks
/linux-4.1.27/Documentation/rapidio/
Dtsi721.txt16 into the corresponding message queue. Messaging callbacks are implemented to be
Drapidio.txt191 vendor-specific callbacks on early stages.
/linux-4.1.27/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt115 All possible callbacks are defined in 'struct watchdog_ops'. You can find it
122 code left from the above steps, it should be refactored into these callbacks.
/linux-4.1.27/Documentation/dmaengine/
Dclient.txt127 slave DMA callbacks are permitted to prepare and submit a new
137 Note that callbacks will always be invoked from the DMA
/linux-4.1.27/drivers/misc/mic/card/
Dmic_virtio.c313 vq_callback_t *callbacks[], in mic_find_vqs() argument
327 vqs[i] = mic_find_vq(vdev, i, callbacks[i], names[i]); in mic_find_vqs()
/linux-4.1.27/Documentation/wimax/
DREADME.wimax20 control structures. This provides a set of callbacks that the WiMAX
/linux-4.1.27/sound/soc/omap/
DKconfig22 callbacks provided by OMAPDSS and registers the component
/linux-4.1.27/Documentation/infiniband/
Dcore_locking.txt93 callbacks run is not defined. Depending on the low-level driver, it
/linux-4.1.27/fs/affs/
DChanges138 - One set of dentry callbacks is enough. (BH)
167 - Added dentry callbacks to allow the dcache to
/linux-4.1.27/Documentation/input/
Dinput-programming.txt164 disconnects. Calls to both callbacks are serialized.
264 getkeycode() and setkeycode() callbacks allow drivers to override default
/linux-4.1.27/block/
Dblk-core.c3085 LIST_HEAD(callbacks); in flush_plug_callbacks()
3088 list_splice_init(&plug->cb_list, &callbacks); in flush_plug_callbacks()
3090 while (!list_empty(&callbacks)) { in flush_plug_callbacks()
3091 struct blk_plug_cb *cb = list_first_entry(&callbacks, in flush_plug_callbacks()
/linux-4.1.27/Documentation/power/powercap/
Dpowercap.txt231 The number of constraints in a power zone and the corresponding callbacks have
/linux-4.1.27/net/core/
Ddev.c2448 if (ptype->type == type && ptype->callbacks.gso_segment) { in skb_mac_gso_segment()
2449 segs = ptype->callbacks.gso_segment(skb, features); in skb_mac_gso_segment()
3920 if (ptype->type != type || !ptype->callbacks.gro_complete) in napi_gro_complete()
3923 err = ptype->callbacks.gro_complete(skb, 0); in napi_gro_complete()
4054 if (ptype->type != type || !ptype->callbacks.gro_receive) in dev_gro_receive()
4081 pp = ptype->callbacks.gro_receive(&napi->gro_list, skb); in dev_gro_receive()
4147 if (ptype->type != type || !ptype->callbacks.gro_receive) in gro_find_receive_by_type()
4161 if (ptype->type != type || !ptype->callbacks.gro_complete) in gro_find_complete_by_type()
/linux-4.1.27/init/
DKconfig644 they have RCU callbacks queued, and prevents RCU from waking
733 invoke callbacks, where the "N" is the CPU being offloaded,
748 This option allows no-CBs CPUs (whose RCU callbacks are invoked
758 no-CBs CPUs, whose RCU callbacks will be invoked by per-CPU
760 invoke their own RCU callbacks in softirq context.
770 callbacks are invoked by a per-CPU kthread whose name begins
773 All other CPUs will invoke their own RCU callbacks in softirq
784 boot parameter will be ignored. All CPUs' RCU callbacks will
/linux-4.1.27/drivers/usb/serial/
Dkeyspan.c1279 static struct callbacks { struct
1336 struct callbacks *cback; in keyspan_setup_urbs()
2401 struct callbacks *cback; in keyspan_port_probe()
/linux-4.1.27/Documentation/crypto/
Dasync-tx-api.txt172 1/ Completion callbacks are expected to happen in tasklet context
/linux-4.1.27/lib/
DKconfig.debug425 bool "Debug RCU callbacks objects"
606 memory hotplug notifier chain callbacks. It is controlled through
1360 specified notifier chain callbacks. It is useful to test the error
1371 errors to CPU notifier chain callbacks. It is controlled through
1395 PM notifier chain callbacks. It is controlled through debugfs
1418 OF reconfig notifier chain callbacks. It is controlled
/linux-4.1.27/Documentation/dvb/
DREADME.dvb-usb30 is done via callbacks, assigned in a static device-description (struct
/linux-4.1.27/sound/pci/hda/
Dhda_intel.c1262 static azx_get_pos_callback_t callbacks[] = { in assign_position_fix() local
1270 chip->get_position[0] = chip->get_position[1] = callbacks[fix]; in assign_position_fix()
/linux-4.1.27/drivers/net/wireless/brcm80211/brcmsmac/phy/
Dphy_cmn.c820 int callbacks = 0; in wlc_phy_down() local
824 callbacks++; in wlc_phy_down()
829 return callbacks; in wlc_phy_down()
/linux-4.1.27/Documentation/spi/
Dspi-summary136 completion callbacks. There are also some simple synchronous wrappers
296 data or chipselect callbacks. This is stored in spi_device later.)
/linux-4.1.27/arch/x86/kernel/
Dentry_32.S976 # to pop the stack frame we end up in an infinite loop of failsafe callbacks.
/linux-4.1.27/Documentation/i2c/
Dwriting-clients282 appropriate callbacks for the dev_pm_ops of the driver (like suspend
/linux-4.1.27/Documentation/devicetree/
Dusage-model.txt202 several times with different helper callbacks to parse device tree
Dbooting-without-of.txt264 containing the various callbacks that the generic code will
1192 early_init_dt_scan_*() callbacks. That code can be re-used in a
/linux-4.1.27/Documentation/filesystems/configfs/
Dconfigfs.txt426 These API cannot be called underneath any configfs callbacks, as
/linux-4.1.27/Documentation/block/
Dbiodoc.txt229 of the i/o scheduler. There are more pluggable callbacks, e.g for init,
653 I/O completion callbacks are per-bio rather than per-segment, so drivers
/linux-4.1.27/Documentation/cgroups/
Dcgroups.txt483 various methods, which are callbacks from the cgroup system, along
/linux-4.1.27/Documentation/trace/
Dftrace.txt228 as well as the number of callbacks that have been attached.
2450 function tracing callbacks are very sensitive, when these commands