Home
last modified time | relevance | path

Searched refs:wake (Results 1 – 137 of 137) sorted by relevance

/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-devices-power14 space to check if the device is enabled to wake up the system
33 be enabled to wake up the system from sleep states.
86 attribute is read-only. If the device is not capable to wake up
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
100 the device is not enabled to wake up the system from sleep
111 is not capable to wake up the system from sleep states, this
112 attribute is not present. If the device is not enabled to wake
122 read-only. If the device is not capable to wake up the system
124 device is not enabled to wake up the system from sleep states,
[all …]
Dsysfs-class-rc91 to trigger a system wake event.
93 scancodes which match the filter will wake the system from e.g.
106 expected value to trigger a system wake event.
108 scancodes which match the filter will wake the system from e.g.
Dsysfs-driver-intel-rapid-start11 indicates that the system will wake to enter hibernation when
/linux-4.1.27/Documentation/devicetree/bindings/net/wireless/
Dbrcm,bcm43xx-fmac.txt16 - interrupts : specifies attributes for the out-of-band interrupt (host-wake).
19 to "host-wake".
39 interrupt-names = "host-wake";
/linux-4.1.27/Documentation/
Dbtmrvl.txt19 where GPIO is the pin number of GPIO used to wake up the host.
27 # Use SDIO interface to wake up the host and set GAP to 0x80:
31 # Use GPIO pin #3 to wake up the host and set GAP to 0xff:
55 These commands are used to enable host sleep or wake up firmware
Dfutex-requeue-pi.txt19 implementation would wake the highest-priority waiter, and leave the
91 The requeue code cannot simply wake the waiter and leave it to
108 wake-up scenarios.
112 possibly wake the waiting tasks. Internally, this system call is
124 their sum is all that really matters. futex_requeue() will wake or
125 requeue up to nr_wake + nr_requeue tasks. It will wake only as many
Drtc.txt44 a few ways (enabling longer alarm periods, and wake-from-hibernate).
156 after wake if a daily wakeup is required. Format is seconds since
189 In many cases, the RTC alarm can be a system wake event, used to force
Dthis_cpu_ops.txt278 unless absolutely necessary. Please consider using an IPI to wake up
329 the wake up times will be affected.
Dintel_txt.txt105 o It will wake the APs from the special sleep state the GETSEC[SENTER]
Drobust-futexes.txt20 sys_futex(FUTEX_WAKE) syscall to wake them up. Once all waiters have
Dmemory-barriers.txt36 - Sleep and wake-up functions.
1960 of going to sleep, and the primitives to initiate a wake up imply certain
2002 Secondly, code that performs a wake up normally follows something like this:
2012 A write memory barrier is implied by wake_up() and co. if and only if they wake
2059 order multiple stores before the wake-up with respect to loads of those stored
2287 To wake up a particular waiter, the up_read() or up_write() functions have to:
Dkernel-parameters.txt875 disable BSP to wake up multiple CPUs without
2397 interrupt wake-up latency, which may improve performance
3001 wake up the corresponding kthread, but degrades
3003 periodically wake up to do the polling.
Dpinctrl.txt891 wake up and maybe even gpio_request/gpio_free as part of this cycle. This
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dvic.txt26 configured as wake up source for the system. Order of bits is the same as for
28 configured as a wake up source for the system. If unspecied, defaults to all
29 interrupt sources configurable as wake up sources.
Didle-states.txt29 wake-up capabilities, hence it is not considered in this document).
64 like cache flushing. This is abortable on pending wake-up
74 between 0 and infinite time, until a wake-up event occurs.
85 wakeup-latency: Maximum delay between the signaling of a wake-up event and the
93 (ie wake-up) that causes the CPU to return to the EXEC phase.
95 An operating system scheduler may need to compute the shortest wake-up delay
102 (eg waking-up) the CPU with the shortest wake-up latency.
103 The wake-up latency must take into account the entry latency if that period
111 worst case wake-up latency it can incur if a CPU is allowed to enter an
187 wake-up IRQ) is less than IDLE2-min-residency, IDLE1 is the better idle state
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dchipone_icn8318.txt9 - wake-gpios : GPIO specification for the WAKE input
38 wake-gpios = <&pio 1 3 GPIO_ACTIVE_HIGH>; /* PB3 */
Dedt-ft5x06.txt29 - wake-gpios: GPIO specification for the WAKE input
54 wake-gpios = <&gpio4 9 0>;
/linux-4.1.27/drivers/md/
Ddm-kcopyd.c185 static void wake(struct dm_kcopyd_client *kc) in wake() function
475 wake(kc); in complete_io()
488 wake(kc); in complete_io()
614 wake(kc); in dispatch_job()
681 wake(kc); in segment_complete()
797 wake(kc); in dm_kcopyd_do_callback()
/linux-4.1.27/Documentation/sound/alsa/
Dpowersave.txt33 state. Also, it often takes certain time to wake up from the
40 consumption, but might result in longer wake-up time and click noise.
DHD-Audio.txt73 the wake-up timing. It wakes up a few samples before actually
76 an artificial delay to the wake up timing. This delay is controlled
/linux-4.1.27/tools/perf/bench/
DBuild5 perf-y += futex-wake.o
/linux-4.1.27/Documentation/scheduler/
Dsched-arch.txt10 take the runqueue lock. This is usually due to a wake up operation in
49 need an interrupt to wake them up when need_resched goes high.
Dsched-stats.txt48 6) # of times try_to_wake_up() was called to wake up the local cpu
/linux-4.1.27/arch/arm/plat-omap/
DKconfig141 bool "Enable wake-up events for serial ports"
145 Select this option if you want to have your system wake up
146 to data on the serial RX line. This allows you to wake the
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Dnvidia,tegra20-rtc.txt4 registers. The alarms and other interrupts may wake the system from low-power
Disil,isl12057.txt16 can wake up the device.
/linux-4.1.27/arch/arm/plat-samsung/
Dadc.c193 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wake); in s3c_adc_read()
197 client->wait = &wake; in s3c_adc_read()
204 ret = wait_event_timeout(wake, client->result >= 0, HZ / 2); in s3c_adc_read()
/linux-4.1.27/Documentation/power/
Dsuspend-and-interrupts.txt45 interrupt will wake the system from a suspended state -- for such cases it is
59 System wakeup interrupts generally need to be configured to wake up the system
68 wake up the system from sleep sates, the corresponding input of that interrupt
87 system suspend currently in progress to be aborted or wake up the system if
Dcharger-manager.txt76 should be able to wake up the system from suspend. Charger Manager
196 and others critical to chargers, the system should be configured to wake up.
197 At least the following should wake up the system from a suspend:
Druntime_pm.txt257 - set if the device is capable of generating runtime wake-up events
554 ->probe() callback will likely need to wake it up using one of the PM core's
600 The device may have different wake-up settings for runtime PM and system sleep.
601 For example, remote wake-up may be enabled for runtime suspend but disallowed
604 device's wake-up setting (it may leave that to the device driver's system
613 * The device might need to switch power levels, wake-up settings, etc.
615 * Remote wake-up events might have been lost by the firmware.
770 USB devices can go into low-power mode or send wake-up requests, but neither is
Dstates.txt109 trigger wake up events (e.g. pressing a key or opening a laptop lid).
Ddevices.txt73 network wake-on-LAN packets, keyboard or mouse activity, and media insertion
180 and Ethernet adapters whose WoL (wake-on-LAN) feature has been set up with
234 functional in order to wake the system.
Dpci.txt188 If the device is required to wake up the system from the target sleep state, the
315 unsigned int wakeup_prepared:1; /* Device prepared for wake up */
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,l2-intc.txt17 - brcm,irq-can-wake: If present, this means the L2 controller can be used as a
Dbrcm,bcm3380-l2-intc.txt28 - brcm,irq-can-wake: if present, this means the L2 controller can be used as a
Dbrcm,bcm7120-l2-intc.txt70 - brcm,irq-can-wake: if present, this means the L2 controller can be used as a
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dgpio-keys-polled.txt23 - gpio-key,wakeup: Boolean, button can wake-up the system.
Dgpio-keys.txt26 - gpio-key,wakeup: Boolean, button can wake-up the system.
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dste,nomadik.txt66 0: wake-up detection enabled,
67 1: wake-up detection disabled.
Dsamsung-pinctrl.txt147 of pins supporting wake-up interrupts:
160 Node of every bank of pins supporting direct wake-up interrupts (without
203 /* Pin bank with external GPIO or muxed wake-up interrupts */
214 /* Pin bank with external direct wake-up interrupts */
Dpinctrl-single.txt83 interrupts for wake-up events for example. In this case pinctrl-single
84 is set up as a chained interrupt controller and the wake-up interrupts
/linux-4.1.27/kernel/power/
Dsuspend.c191 if (state != PM_SUSPEND_FREEZE && suspend_ops->wake) in platform_resume_noirq()
192 suspend_ops->wake(); in platform_resume_noirq()
DKconfig139 wake-up event or a driver's request.
144 wake-up events.
167 make it wake up a few seconds later using an RTC wakeup alarm.
/linux-4.1.27/fs/ocfs2/dlm/
Ddlmconvert.c451 int call_ast = 0, kick_thread = 0, ast_reserved = 0, wake = 0; in dlm_convert_lock_handler() local
535 wake = 1; in dlm_convert_lock_handler()
538 if (wake) in dlm_convert_lock_handler()
Ddlmmaster.c1965 int wake = 0; in dlm_assert_master_handler() local
1973 wake = 1; in dlm_assert_master_handler()
1981 if (wake) in dlm_assert_master_handler()
2485 int wake = 0; in dlm_migrate_lockres() local
2545 wake = 1; in dlm_migrate_lockres()
2595 wake = 1; in dlm_migrate_lockres()
2641 wake = 1; in dlm_migrate_lockres()
2672 if (wake) in dlm_migrate_lockres()
/linux-4.1.27/tools/perf/Documentation/
Dperf-bench.txt210 *wake*::
211 Suite for evaluating wake calls.
/linux-4.1.27/drivers/staging/comedi/drivers/
Damplc_pci230.c1711 unsigned int wake; in pci230_ai_update_fifo_trigger_level() local
1716 wake = cmd->scan_end_arg - s->async->cur_chan; in pci230_ai_update_fifo_trigger_level()
1718 wake = comedi_nsamples_left(s, PCI230_ADC_FIFOLEVEL_HALFFULL); in pci230_ai_update_fifo_trigger_level()
1720 if (wake >= PCI230_ADC_FIFOLEVEL_HALFFULL) { in pci230_ai_update_fifo_trigger_level()
1722 } else if (wake > 1 && devpriv->hwver > 0) { in pci230_ai_update_fifo_trigger_level()
1724 if (devpriv->adcfifothresh != wake) { in pci230_ai_update_fifo_trigger_level()
1725 devpriv->adcfifothresh = wake; in pci230_ai_update_fifo_trigger_level()
1726 outw(wake, devpriv->daqio + PCI230P_ADCFFTH); in pci230_ai_update_fifo_trigger_level()
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-bus-usb19 free to wake up in response to I/O requests, you should
/linux-4.1.27/drivers/net/ethernet/cirrus/
Dep93xx_eth.c391 int wake; in ep93xx_tx_complete() local
393 wake = 0; in ep93xx_tx_complete()
432 wake = 1; in ep93xx_tx_complete()
437 if (wake) in ep93xx_tx_complete()
/linux-4.1.27/drivers/acpi/
Dsleep.c591 .wake = acpi_pm_finish,
619 .wake = acpi_pm_finish,
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dam33xx-usb.txt15 Module" block. A second offset and length for the USB wake up control
18 the USB wake up control register.
/linux-4.1.27/drivers/misc/mic/host/
Dmic_virtio.c481 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wake); in mic_virtio_config_change()
506 ret = wait_event_timeout(wake, in mic_virtio_config_change()
748 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wake); in mic_virtio_del_device()
763 ret = wait_event_timeout(wake, in mic_virtio_del_device()
/linux-4.1.27/net/phonet/
Dpep.c268 int wake = 0; in pipe_rcv_status() local
289 atomic_set(&pn->tx_credits, wake = 1); in pipe_rcv_status()
295 atomic_set(&pn->tx_credits, wake = 1); in pipe_rcv_status()
303 atomic_add(wake = hdr->data[4], &pn->tx_credits); in pipe_rcv_status()
311 if (wake) in pipe_rcv_status()
/linux-4.1.27/drivers/gpu/drm/radeon/
Dradeon_fence.c201 bool wake = false; in radeon_fence_activity() local
241 wake = true; in radeon_fence_activity()
256 return wake; in radeon_fence_activity()
/linux-4.1.27/Documentation/devicetree/bindings/arm/samsung/
Dpmu.txt35 to wake up a suspended PMU). In which case, they can have the
/linux-4.1.27/include/linux/
Dwm97xx.h322 enum wm97xx_gpio_wake wake);
Dsuspend.h183 void (*wake)(void); member
/linux-4.1.27/sound/soc/intel/common/
Dsst-dsp.c250 if (sst->ops->wake) in sst_dsp_wake()
251 return sst->ops->wake(sst); in sst_dsp_wake()
Dsst-dsp-priv.h39 int (*wake)(struct sst_dsp *); member
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc.txt65 - enable-sdio-wakeup: Enables wake up of host system on SDIO IRQ assertion
138 interrupt-names = "host-wake";
/linux-4.1.27/fs/ceph/
Dcaps.c1140 int wake = 0; in __send_cap() local
1188 wake = 1; in __send_cap()
1249 if (wake) in __send_cap()
2305 int last = 0, put = 0, flushsnaps = 0, wake = 0; in ceph_put_cap_refs() local
2337 wake = 1; in ceph_put_cap_refs()
2353 if (wake) in ceph_put_cap_refs()
2495 bool wake = false; in handle_cap_grant() local
2615 wake = true; in handle_cap_grant()
2671 wake = true; in handle_cap_grant()
2688 wake = true; in handle_cap_grant()
[all …]
Dmds_client.c1290 int wake = 0; in renewed_caps() local
1301 wake = 1; in renewed_caps()
1311 if (wake) in renewed_caps()
2574 int wake = 0; in handle_session() local
2606 wake = 1; in handle_session()
2621 wake = 2; /* for good measure */ in handle_session()
2657 if (wake) { in handle_session()
2660 if (wake == 2) in handle_session()
Dinode.c677 bool wake = false; in fill_inode() local
866 wake = true; in fill_inode()
896 if (wake) in fill_inode()
/linux-4.1.27/drivers/media/rc/img-ir/
DKconfig27 and allows an IR scancode to be used as a wake event.
/linux-4.1.27/sound/pci/hda/
Dhda_proc.c602 unsigned int enable, direction, wake, unsol, sticky, data; in print_gpio() local
618 wake = snd_hda_codec_read(codec, nid, 0, in print_gpio()
632 (wake & (1<<i)) ? 1 : 0, in print_gpio()
/linux-4.1.27/Documentation/devicetree/bindings/metag/
Dpdc-intc.txt5 lines which can wake the system, and are passed on through output interrupt
/linux-4.1.27/arch/unicore32/kernel/
Dsleep.S91 @ set wake up source
/linux-4.1.27/Documentation/filesystems/nfs/
Dknfsd-stats.txt77 already choosing not to wake idle nfsd threads because there are too
92 Counts how many times the sunrpc server layer chose not to wake an
/linux-4.1.27/drivers/net/ethernet/freescale/fs_enet/
Dfs_enet-main.c630 int wake = 0; in fs_timeout() local
644 wake = fep->tx_free && !(CBDR_SC(fep->cur_tx) & BD_ENET_TX_READY); in fs_timeout()
647 if (wake) in fs_timeout()
/linux-4.1.27/drivers/tty/vt/
Dvt_ioctl.c91 int wake = 0; in vt_event_post() local
106 wake = 1; in vt_event_post()
110 if (wake) in vt_event_post()
/linux-4.1.27/drivers/media/rc/
Dene_ir.c1148 bool wake = device_may_wakeup(&dev->pnp_dev->dev); in ene_suspend() local
1150 if (!wake && dev->rx_enabled) in ene_suspend()
1153 ene_enable_wake(dev, wake); in ene_suspend()
/linux-4.1.27/drivers/usb/gadget/udc/
Dat91_udc.c1972 int wake = udc->driver && device_may_wakeup(&pdev->dev); in at91udc_suspend() local
1981 || !wake in at91udc_suspend()
1985 wake = 0; in at91udc_suspend()
1990 udc->active_suspend = wake; in at91udc_suspend()
1991 if (gpio_is_valid(udc->board.vbus_pin) && !udc->board.vbus_polled && wake) in at91udc_suspend()
/linux-4.1.27/drivers/net/ethernet/intel/
De100.c3040 static int __e100_power_off(struct pci_dev *pdev, bool wake) in __e100_power_off() argument
3042 if (wake) in __e100_power_off()
3054 bool wake; in e100_suspend() local
3055 __e100_shutdown(pdev, &wake); in e100_suspend()
3056 return __e100_power_off(pdev, wake); in e100_suspend()
3089 bool wake; in e100_shutdown() local
3090 __e100_shutdown(pdev, &wake); in e100_shutdown()
3092 __e100_power_off(pdev, wake); in e100_shutdown()
/linux-4.1.27/Documentation/networking/
Dmultiqueue.txt23 netif_{start|stop|wake}_subqueue() functions to manage each queue while the
Dvortex.txt230 Becker's `ether-wake' application may be used to wake suspended
300 Donald's wake-on-LAN page:
Drds.txt348 wake up sock
Dscaling.txt234 to enqueue packets onto the backlog of another CPU and to wake up that
/linux-4.1.27/drivers/input/touchscreen/
Dwm97xx-core.c233 enum wm97xx_gpio_wake wake) in wm97xx_config_gpio() argument
256 if (wake == WM97XX_GPIO_WAKE) in wm97xx_config_gpio()
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dregulator.txt24 only some external interrupt can wake the device.
/linux-4.1.27/sound/soc/
Dsoc-jack.c360 if (gpios[i].wake) { in snd_soc_jack_add_gpios()
/linux-4.1.27/drivers/block/drbd/
Ddrbd_actlog.c233 int wake; in _al_get() local
238 wake = !test_and_set_bit(BME_PRIORITY, &bm_ext->flags); in _al_get()
240 if (wake) in _al_get()
Ddrbd_req.c1361 int wake = 0; in prepare_al_transaction_nonblock() local
1370 wake = 1; in prepare_al_transaction_nonblock()
1377 if (wake) in prepare_al_transaction_nonblock()
/linux-4.1.27/Documentation/sound/oss/
DALS32 If isapnptools is used to wake up the sound card (as in 2.2.x), the settings
DREADME.OSS314 PnP models of sound cards even you have managed to wake up the card properly.
/linux-4.1.27/arch/arm/boot/dts/
Dimx53-tx53-x03x.dts221 wake-gpios = <&gpio2 21 GPIO_ACTIVE_HIGH>;
Dimx6qdl-tx6.dtsi277 wake-gpios = <&gpio2 21 GPIO_ACTIVE_HIGH>;
Dimx28-tx28.dts329 wake-gpios = <&gpio4 9 GPIO_ACTIVE_HIGH>;
/linux-4.1.27/Documentation/arm/pxa/
Dmfp.txt129 c) if by board design, a pin can be configured to wake up the system
137 to indicate that this pin has the capability of wake-up the system,
/linux-4.1.27/tools/virtio/virtio-trace/
DREADME17 the controller wake read/write threads.
/linux-4.1.27/Documentation/devicetree/bindings/arm/msm/
Dqcom,idle-state.txt34 between the time it enters idle and the next known wake up. SPC mode is used
/linux-4.1.27/fs/btrfs/
Dcompression.c834 goto wake; in free_workspace()
840 wake: in free_workspace()
Dextent_io.h214 unsigned bits, int wake, int delete,
Dextent_io.c514 unsigned *bits, int wake) in clear_state_bit() argument
526 if (wake) in clear_state_bit()
573 unsigned bits, int wake, int delete, in clear_extent_bit() argument
674 state = clear_state_bit(tree, state, &bits, wake); in clear_extent_bit()
692 if (wake) in clear_extent_bit()
695 clear_state_bit(tree, prealloc, &bits, wake); in clear_extent_bit()
701 state = clear_state_bit(tree, state, &bits, wake); in clear_extent_bit()
/linux-4.1.27/drivers/net/ethernet/sfc/
Dmcdi.c469 bool wake = false; in efx_mcdi_ev_cpl() local
491 wake = true; in efx_mcdi_ev_cpl()
496 if (wake) { in efx_mcdi_ev_cpl()
/linux-4.1.27/Documentation/filesystems/
Dfuse.txt333 | [wake up fc->waitq] | [woken up]
350 | [woken up] | [wake up req->waitq]
/linux-4.1.27/drivers/pinctrl/nomadik/
Dpinctrl-nomadik.c785 bool wake = irqd_is_wakeup_set(d); in nmk_gpio_irq_set_type() local
805 if (enabled || wake) in nmk_gpio_irq_set_type()
819 if (enabled || wake) in nmk_gpio_irq_set_type()
/linux-4.1.27/kernel/rcu/
Dtree_plugin.h97 bool wake);
587 bool wake) in rcu_report_exp_rnp() argument
601 if (wake) { in rcu_report_exp_rnp()
/linux-4.1.27/Documentation/gpio/
Dgpio.txt55 wakeup events, to wake the system from a low power state.
Dgpio-legacy.txt42 wakeup events, to wake the system from a low power state.
/linux-4.1.27/arch/frv/kernel/
Dsleep.S189 # wake SDRAM from self-refresh mode
/linux-4.1.27/Documentation/locking/
Drt-mutex-design.txt526 mutex, but that owner has yet to wake up and actually take the mutex.
689 The schedule can then wake up for a few reasons.
742 If there are waiters, then we need to wake one up and give that waiter
745 On the wake up code, the pi_lock of the current owner is taken. The top
762 Finally we unlock the pi_lock of the pending owner and wake it up.
Dspinlocks.txt142 wake up. So read-locks are safe (which is good: they are very common
Dww-mutex-design.txt87 Of course, all the usual variants for handling wake-ups due to signals are also
/linux-4.1.27/block/
Dblk-mq.c146 bool wake; in blk_mq_unfreeze_queue() local
149 wake = !--q->mq_freeze_depth; in blk_mq_unfreeze_queue()
152 if (wake) { in blk_mq_unfreeze_queue()
/linux-4.1.27/sound/soc/intel/haswell/
Dsst-haswell-dsp.c697 .wake = hsw_wake,
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dmemx.fuc279 // Read random memory to wake up... things
/linux-4.1.27/drivers/media/firewire/
Dfiredtv-avc.c290 goto wake; in avc_recv()
306 wake: in avc_recv()
/linux-4.1.27/drivers/base/regmap/
Dregmap.c2476 bool wake; in regmap_async_complete_cb() local
2482 wake = list_empty(&map->async_list); in regmap_async_complete_cb()
2489 if (wake) in regmap_async_complete_cb()
/linux-4.1.27/drivers/net/ethernet/intel/igb/
Digb_main.c7433 bool wake; in igb_suspend() local
7436 retval = __igb_shutdown(pdev, &wake, 0); in igb_suspend()
7440 if (wake) { in igb_suspend()
7518 bool wake; in igb_runtime_suspend() local
7520 retval = __igb_shutdown(pdev, &wake, 1); in igb_runtime_suspend()
7524 if (wake) { in igb_runtime_suspend()
7542 bool wake; in igb_shutdown() local
7544 __igb_shutdown(pdev, &wake, 0); in igb_shutdown()
7547 pci_wake_from_d3(pdev, wake); in igb_shutdown()
/linux-4.1.27/drivers/net/ethernet/intel/e1000/
De1000_main.c5149 bool wake; in e1000_suspend() local
5151 retval = __e1000_shutdown(pdev, &wake); in e1000_suspend()
5155 if (wake) { in e1000_suspend()
5212 bool wake; in e1000_shutdown() local
5214 __e1000_shutdown(pdev, &wake); in e1000_shutdown()
5217 pci_wake_from_d3(pdev, wake); in e1000_shutdown()
/linux-4.1.27/arch/blackfin/
DKconfig1281 this mode. Typically an external event or RTC activity will wake
1305 the general-purpose wake-up enable (GPWE) control bit to enable
1306 wake-up upon detection of an active low signal on the /GPW (PH7) pin.
/linux-4.1.27/fs/xfs/
Dxfs_log.c2600 int wake = 0; in xlog_state_do_callback() local
2794 wake = 1; in xlog_state_do_callback()
2797 if (wake) in xlog_state_do_callback()
/linux-4.1.27/arch/powerpc/platforms/
DKconfig100 The driver provides a way to wake up the system by MPIC
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt86 will shut down, but never wake up). Consider this experimental. By
/linux-4.1.27/Documentation/virtual/kvm/
Dmsr.txt191 kind of token 0xffffffff which tells vcpu that it should wake
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dgpc.fuc349 // ack, and wake up main()
Dhub.fuc370 // ack, and wake up main()
/linux-4.1.27/Documentation/PCI/
Dpci.txt118 Useful for enabling wake-on-lan (NIC) or changing
260 o wake up the device if it was in suspended state,
/linux-4.1.27/Documentation/laptops/
Dlaptop-mode.txt265 # exceeded, the kernel will wake flusher threads which will then reduce the
387 # exceeded, the kernel will wake flusher threads which will then reduce the
Dthinkpad-acpi.txt336 undock. Set to zero for normal wake-ups or wake-ups
547 wake up caused by the firmware will have negated most safety nets...
/linux-4.1.27/Documentation/nfc/
Dnfc-hci.txt235 The completion callback will then wake the syscall context.
/linux-4.1.27/drivers/net/ethernet/intel/ixgbe/
Dixgbe_main.c5905 bool wake; in ixgbe_suspend() local
5907 retval = __ixgbe_shutdown(pdev, &wake); in ixgbe_suspend()
5911 if (wake) { in ixgbe_suspend()
5924 bool wake; in ixgbe_shutdown() local
5926 __ixgbe_shutdown(pdev, &wake); in ixgbe_shutdown()
5929 pci_wake_from_d3(pdev, wake); in ixgbe_shutdown()
/linux-4.1.27/drivers/usb/gadget/
DKconfig121 for a bursty VFS behaviour. For instance there may be CPU wake up
/linux-4.1.27/Documentation/video4linux/
Dvideobuf314 - Mark the buffer as done and wake up the process waiting for it.
/linux-4.1.27/include/sound/
Dsoc.h665 bool wake; member
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt431 Because CPUs may power up asynchronously in response to external wake-up
/linux-4.1.27/sound/soc/codecs/
Drt5670.c574 rt5670->hp_gpio.wake = true; in rt5670_set_jack_detect()
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES573 Fix reconnection (and certain failed mounts) to properly wake up the
666 wake up the demultiplex thread after it had exited. Do not log
/linux-4.1.27/drivers/gpio/
DKconfig361 active during S3. The suspend powered GPIOs can be used to wake the
/linux-4.1.27/drivers/platform/x86/
DKconfig860 sleep state, these devices will wake after either a configured
/linux-4.1.27/Documentation/sysctl/
Dvm.txt179 The kernel flusher threads will periodically wake up and write `old' data
/linux-4.1.27/drivers/net/wireless/
Dairo.c7219 int wake = 0; in airo_set_scan() local
7242 wake = 1; in airo_set_scan()
7246 if (wake) in airo_set_scan()
/linux-4.1.27/Documentation/trace/
Dftrace.txt530 for those interested in wake up timings of RT tasks.
1377 time it takes for a task that is woken to actually wake up.
/linux-4.1.27/Documentation/scsi/
DChangeLog.1992-1997831 count to 0, clear this bit to allow usage to continue, wake up
DChangeLog.lpfc389 moved to kthread. kthread_stop() is not able to wake up thread
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1276 is cpu_idle+0x66 ( quiet the cpu is asleep, don't wake it )
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2340 version command is a good way to 'wake it up' before networking has