Home
last modified time | relevance | path

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

/linux-4.4.14/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.4.14/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.4.14/tools/perf/bench/
DBuild5 perf-y += futex-wake.o
6 perf-y += futex-wake-parallel.o
/linux-4.4.14/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.
Drobust-futexes.txt20 sys_futex(FUTEX_WAKE) syscall to wake them up. Once all waiters have
Dintel_txt.txt105 o It will wake the APs from the special sleep state the GETSEC[SENTER]
Dmemory-barriers.txt36 - Sleep and wake-up functions.
1949 of going to sleep, and the primitives to initiate a wake up imply certain
1991 Secondly, code that performs a wake up normally follows something like this:
2001 A write memory barrier is implied by wake_up() and co. if and only if they wake
2048 order multiple stores before the wake-up with respect to loads of those stored
2242 To wake up a particular waiter, the up_read() or up_write() functions have to:
Dkernel-parameters.txt890 disable BSP to wake up multiple CPUs without
2474 interrupt wake-up latency, which may improve performance
3078 wake up the corresponding kthread, but degrades
3080 periodically wake up to do the polling.
Dpinctrl.txt902 wake up and maybe even gpio_request/gpio_free as part of this cycle. This
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Darm,vic.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.
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
Dimg,pdc-intc.txt5 lines which can wake the system, and are passed on through output interrupt
Dbrcm,bcm7120-l2-intc.txt70 - brcm,irq-can-wake: if present, this means the L2 controller can be used as a
/linux-4.4.14/drivers/nfc/s3fwrn5/
Ds3fwrn5.h74 static inline int s3fwrn5_set_wake(struct s3fwrn5_info *info, bool wake) in s3fwrn5_set_wake() argument
79 info->phy_ops->set_wake(info->phy_id, wake); in s3fwrn5_set_wake()
Di2c.c49 static void s3fwrn5_i2c_set_wake(void *phy_id, bool wake) in s3fwrn5_i2c_set_wake() argument
54 gpio_set_value(phy->gpio_fw_wake, wake); in s3fwrn5_i2c_set_wake()
/linux-4.4.14/Documentation/DocBook/
Dgenericirq.xml.db29 API-irq-set-irq-wake
30 API-irq-wake-thread
71 API-irq-chip-set-wake-parent
Dkernel-locking.xml.db16 API-requeue-pi-wake-futex
Dnetworking.xml.db218 API-xprt-wake-pending-tasks
226 API-rpc-wake-up
227 API-rpc-wake-up-status
309 API-netif-wake-subqueue
405 API-netif-wake-queue
D80211.xml.db129 API-ieee80211-wake-queue
131 API-ieee80211-wake-queues
Dkernel-api.xml.db371 API-irq-set-irq-wake
372 API-irq-wake-thread
429 API---pci-enable-wake
430 API-pci-wake-from-d3
433 API-pci-dev-run-wake
Ddevice-drivers.xml.db24 API-wake-up-process
96 API---wake-up
97 API---wake-up-sync-key
100 API-wake-up-bit
101 API-wake-up-atomic-t
/linux-4.4.14/tools/perf/Documentation/
Dperf-bench.txt194 *wake*::
195 Suite for evaluating wake calls.
197 *wake-parallel*::
198 Suite for evaluating parallel wake calls.
/linux-4.4.14/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.txt31 - wake-gpios: GPIO specification for the WAKE input
56 wake-gpios = <&gpio4 9 GPIO_ACTIVE_HIGH>;
/linux-4.4.14/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.4.14/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.4.14/Documentation/devicetree/bindings/arm/
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.4.14/tools/testing/selftests/futex/
DREADME56 Perhaps something like "wait-wake-1" "wait-wake-2" is adequate, leaving the
/linux-4.4.14/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.4.14/arch/arm/boot/dts/
Drk3288-veyron-chromebook.dtsi173 /* Common for sleep and wake, but no owners */
180 /* Common for sleep and wake, but no owners */
206 suspend_l_wake: suspend-l-wake {
Dbcm7445.dtsi123 brcm,irq-can-wake;
143 brcm,irq-can-wake;
Dimx6qdl-nit6xlite.dtsi332 /* BT wake */
338 /* BT host wake irq */
Dimx53-tx53-x03x.dts222 wake-gpios = <&gpio2 21 GPIO_ACTIVE_HIGH>;
Dsun6i-a31s-sinovoip-bpi-m2.dts142 interrupt-names = "host-wake";
Dsun7i-a20-wits-pro-a20-dkt.dts133 interrupt-names = "host-wake";
Drk3288-veyron.dtsi438 /* Common for sleep and wake, but no owners */
442 /* Common for sleep and wake, but no owners */
Dsun7i-a20-i12-tvbox.dts182 interrupt-names = "host-wake";
Dsun5i-a13-utoo-p66.dts99 wake-gpios = <&pio 1 3 GPIO_ACTIVE_HIGH>; /* PB3 */
Dsun7i-a20-cubietruck.dts186 interrupt-names = "host-wake";
Dimx6qdl-tx6.dtsi278 wake-gpios = <&gpio2 21 GPIO_ACTIVE_HIGH>;
Dimx28-tx28.dts330 wake-gpios = <&gpio4 9 GPIO_ACTIVE_HIGH>;
/linux-4.4.14/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.4.14/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.4.14/Documentation/devicetree/bindings/iio/temperature/
Dmlx90614.txt13 to hold low in order to wake up the device. In normal operation, the
/linux-4.4.14/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.4.14/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
550 ->probe() callback will likely need to wake it up using one of the PM core's
602 The device may have different wake-up settings for runtime PM and system sleep.
603 For example, remote wake-up may be enabled for runtime suspend but disallowed
606 device's wake-up setting (it may leave that to the device driver's system
615 * The device might need to switch power levels, wake-up settings, etc.
617 * Remote wake-up events might have been lost by the firmware.
772 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.4.14/Documentation/devicetree/bindings/sound/
Dda7219.txt25 interrupt is to be used to wake system, otherwise "irq" should be used.
26 - wakeup-source: Flag to indicate this device can wake system (suspend/resume).
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dste,nomadik.txt68 0: wake-up detection enabled,
69 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.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_fence.c149 bool wake = false; in amdgpu_fence_activity() local
189 wake = true; in amdgpu_fence_activity()
204 return wake; in amdgpu_fence_activity()
/linux-4.4.14/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.c1966 int wake = 0; in dlm_assert_master_handler() local
1974 wake = 1; in dlm_assert_master_handler()
1982 if (wake) in dlm_assert_master_handler()
2486 int wake = 0; in dlm_migrate_lockres() local
2546 wake = 1; in dlm_migrate_lockres()
2596 wake = 1; in dlm_migrate_lockres()
2642 wake = 1; in dlm_migrate_lockres()
2673 if (wake) in dlm_migrate_lockres()
/linux-4.4.14/kernel/power/
Dsuspend.c194 if (state != PM_SUSPEND_FREEZE && suspend_ops->wake) in platform_resume_noirq()
195 suspend_ops->wake(); in platform_resume_noirq()
DKconfig149 wake-up event or a driver's request.
154 wake-up events.
177 make it wake up a few seconds later using an RTC wakeup alarm.
/linux-4.4.14/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.4.14/Documentation/devicetree/bindings/input/
Dgpio-keys.txt26 - wakeup-source: Boolean, button can wake-up the system.
Dgpio-keys-polled.txt30 - wakeup-source: Boolean, button can wake-up the system.
Drotary-encoder.txt22 - wakeup-source: Boolean, rotary encoder can wake up the system.
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-bus-usb19 free to wake up in response to I/O requests, you should
/linux-4.4.14/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.4.14/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.4.14/drivers/acpi/
Dsleep.c594 .wake = acpi_pm_finish,
622 .wake = acpi_pm_finish,
/linux-4.4.14/drivers/misc/mic/host/
Dmic_virtio.c480 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wake); in mic_virtio_config_change()
505 ret = wait_event_timeout(wake, in mic_virtio_config_change()
747 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(wake); in mic_virtio_del_device()
762 ret = wait_event_timeout(wake, in mic_virtio_del_device()
/linux-4.4.14/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.4.14/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.4.14/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt60 - fsl,wake-on-filer : If present, indicates that the hardware supports
63 certain packet types (user) defined by filer rules to wake up the system.
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dp1022si-post.dtsi227 fsl,wake-on-filer;
232 fsl,wake-on-filer;
/linux-4.4.14/include/linux/
Dwm97xx.h322 enum wm97xx_gpio_wake wake);
Dsuspend.h183 void (*wake)(void); member
/linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/
Dpmu.txt35 to wake up a suspended PMU). In which case, they can have the
/linux-4.4.14/sound/soc/intel/common/
Dsst-dsp.c321 if (sst->ops->wake) in sst_dsp_wake()
322 return sst->ops->wake(sst); in sst_dsp_wake()
Dsst-dsp-priv.h41 int (*wake)(struct sst_dsp *); member
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt22 time to wake up from sleep before they can receive SPI transfers at a high
/linux-4.4.14/drivers/media/rc/img-ir/
DKconfig27 and allows an IR scancode to be used as a wake event.
/linux-4.4.14/sound/pci/hda/
Dhda_proc.c657 unsigned int enable, direction, wake, unsol, sticky, data; in print_gpio() local
673 wake = snd_hda_codec_read(codec, nid, 0, in print_gpio()
687 (wake & (1<<i)) ? 1 : 0, in print_gpio()
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmmc.txt71 - wakeup-source: Enables wake up of host system on SDIO IRQ assertion
145 interrupt-names = "host-wake";
/linux-4.4.14/fs/ceph/
Dcaps.c1120 int wake = 0; in __send_cap() local
1166 wake = 1; in __send_cap()
1209 if (wake) in __send_cap()
2581 int last = 0, put = 0, flushsnaps = 0, wake = 0; in ceph_put_cap_refs() local
2613 wake = 1; in ceph_put_cap_refs()
2635 if (wake) in ceph_put_cap_refs()
2769 bool wake = false; in handle_cap_grant() local
2890 wake = true; in handle_cap_grant()
2946 wake = true; in handle_cap_grant()
2963 wake = true; in handle_cap_grant()
[all …]
Dmds_client.c1345 int wake = 0; in renewed_caps() local
1356 wake = 1; in renewed_caps()
1366 if (wake) in renewed_caps()
2634 int wake = 0; in handle_session() local
2666 wake = 1; in handle_session()
2681 wake = 2; /* for good measure */ in handle_session()
2717 if (wake) { in handle_session()
2720 if (wake == 2) in handle_session()
Dinode.c677 bool wake = false; in fill_inode() local
871 wake = true; in fill_inode()
901 if (wake) in fill_inode()
/linux-4.4.14/kernel/rcu/
Dtree.c164 struct rcu_data *rdp, bool wake);
3510 bool wake, unsigned long flags) in __rcu_report_exp_rnp() argument
3525 if (wake) { in __rcu_report_exp_rnp()
3548 struct rcu_node *rnp, bool wake) in rcu_report_exp_rnp() argument
3554 __rcu_report_exp_rnp(rsp, rnp, wake, flags); in rcu_report_exp_rnp()
3563 unsigned long mask, bool wake) in rcu_report_exp_cpu_mult() argument
3574 __rcu_report_exp_rnp(rsp, rnp, wake, flags); /* Releases rnp->lock. */ in rcu_report_exp_cpu_mult()
3582 bool wake) in rcu_report_exp_rdp() argument
3584 rcu_report_exp_cpu_mult(rsp, rdp->mynode, rdp->grpmask, wake); in rcu_report_exp_rdp()
Dtree_plugin.h105 bool wake);
/linux-4.4.14/arch/unicore32/kernel/
Dsleep.S91 @ set wake up source
/linux-4.4.14/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.4.14/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.4.14/drivers/net/ethernet/freescale/fs_enet/
Dfs_enet-main.c648 int wake = 0; in fs_timeout() local
662 wake = fep->tx_free && !(CBDR_SC(fep->cur_tx) & BD_ENET_TX_READY); in fs_timeout()
665 if (wake) in fs_timeout()
/linux-4.4.14/drivers/usb/gadget/udc/
Dat91_udc.c1993 int wake = udc->driver && device_may_wakeup(&pdev->dev); in at91udc_suspend() local
2002 || !wake in at91udc_suspend()
2006 wake = 0; in at91udc_suspend()
2011 udc->active_suspend = wake; in at91udc_suspend()
2012 if (gpio_is_valid(udc->board.vbus_pin) && !udc->board.vbus_polled && wake) in at91udc_suspend()
/linux-4.4.14/drivers/net/ethernet/intel/
De100.c3048 static int __e100_power_off(struct pci_dev *pdev, bool wake) in __e100_power_off() argument
3050 if (wake) in __e100_power_off()
3062 bool wake; in e100_suspend() local
3063 __e100_shutdown(pdev, &wake); in e100_suspend()
3064 return __e100_power_off(pdev, wake); in e100_suspend()
3097 bool wake; in e100_shutdown() local
3098 __e100_shutdown(pdev, &wake); in e100_shutdown()
3100 __e100_power_off(pdev, wake); in e100_shutdown()
/linux-4.4.14/arch/mips/boot/dts/brcm/
Dbcm7358.dtsi101 brcm,irq-can-wake;
Dbcm7360.dtsi101 brcm,irq-can-wake;
Dbcm7362.dtsi107 brcm,irq-can-wake;
Dbcm7346.dtsi107 brcm,irq-can-wake;
/linux-4.4.14/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.4.14/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.4.14/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.c1363 int wake = 0; in prepare_al_transaction_nonblock() local
1372 wake = 1; in prepare_al_transaction_nonblock()
1379 if (wake) in prepare_al_transaction_nonblock()
/linux-4.4.14/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.4.14/sound/soc/
Dsoc-jack.c364 if (gpios[i].wake) { in snd_soc_jack_add_gpios()
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dregulator.txt27 only some external interrupt can wake the device.
/linux-4.4.14/fs/btrfs/
Dextent_io.c534 unsigned *bits, int wake, in clear_state_bit() argument
548 if (wake) in clear_state_bit()
595 unsigned bits, int wake, int delete, in __clear_extent_bit() argument
696 state = clear_state_bit(tree, state, &bits, wake, in __clear_extent_bit()
715 if (wake) in __clear_extent_bit()
718 clear_state_bit(tree, prealloc, &bits, wake, changeset); in __clear_extent_bit()
724 state = clear_state_bit(tree, state, &bits, wake, changeset); in __clear_extent_bit()
1319 unsigned bits, int wake, int delete, in clear_extent_bit() argument
1322 return __clear_extent_bit(tree, start, end, bits, wake, delete, in clear_extent_bit()
1329 int wake = 0; in clear_extent_bits() local
[all …]
Dcompression.c836 goto wake; in free_workspace()
842 wake: in free_workspace()
Dextent_io.h230 unsigned bits, int wake, int delete,
/linux-4.4.14/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.4.14/tools/virtio/virtio-trace/
DREADME17 the controller wake read/write threads.
/linux-4.4.14/drivers/net/ethernet/mellanox/mlx5/core/
Den.h255 u64 wake; member
Den_tx.c398 sq->stats.wake++; in mlx5e_poll_tx_cq()
Den_main.c169 s->tx_queue_wake += sq_stats->wake; in mlx5e_update_stats()
/linux-4.4.14/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.4.14/Documentation/networking/dsa/
Dbcm_sf2.txt110 MAC controller wake-on logic. Whenever Wake-on-LAN is requested, an intersection
Ddsa.txt485 participating in Wake-on-LAN active as well as additional wake-up logic if
/linux-4.4.14/Documentation/filesystems/
Dfuse.txt333 | [wake up fc->waitq] | [woken up]
350 | [woken up] | [wake up req->waitq]
/linux-4.4.14/drivers/pinctrl/nomadik/
Dpinctrl-nomadik.c786 bool wake = irqd_is_wakeup_set(d); in nmk_gpio_irq_set_type() local
806 if (enabled || wake) in nmk_gpio_irq_set_type()
820 if (enabled || wake) in nmk_gpio_irq_set_type()
/linux-4.4.14/drivers/net/ethernet/sfc/
Dmcdi.c561 bool wake = false; in efx_mcdi_ev_cpl() local
583 wake = true; in efx_mcdi_ev_cpl()
588 if (wake) { in efx_mcdi_ev_cpl()
/linux-4.4.14/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.4.14/arch/frv/kernel/
Dsleep.S189 # wake SDRAM from self-refresh mode
/linux-4.4.14/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.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dmemx.fuc279 // Read random memory to wake up... things
/linux-4.4.14/sound/soc/intel/haswell/
Dsst-haswell-dsp.c697 .wake = hsw_wake,
/linux-4.4.14/drivers/media/firewire/
Dfiredtv-avc.c290 goto wake; in avc_recv()
306 wake: in avc_recv()
/linux-4.4.14/drivers/net/ethernet/intel/igb/
Digb_main.c7386 bool wake; in igb_suspend() local
7389 retval = __igb_shutdown(pdev, &wake, 0); in igb_suspend()
7393 if (wake) { in igb_suspend()
7472 bool wake; in igb_runtime_suspend() local
7474 retval = __igb_shutdown(pdev, &wake, 1); in igb_runtime_suspend()
7478 if (wake) { in igb_runtime_suspend()
7496 bool wake; in igb_shutdown() local
7498 __igb_shutdown(pdev, &wake, 0); in igb_shutdown()
7501 pci_wake_from_d3(pdev, wake); in igb_shutdown()
/linux-4.4.14/drivers/net/ethernet/intel/e1000/
De1000_main.c5144 bool wake; in e1000_suspend() local
5146 retval = __e1000_shutdown(pdev, &wake); in e1000_suspend()
5150 if (wake) { in e1000_suspend()
5207 bool wake; in e1000_shutdown() local
5209 __e1000_shutdown(pdev, &wake); in e1000_shutdown()
5212 pci_wake_from_d3(pdev, wake); in e1000_shutdown()
/linux-4.4.14/drivers/base/regmap/
Dregmap.c2693 bool wake; in regmap_async_complete_cb() local
2699 wake = list_empty(&map->async_list); in regmap_async_complete_cb()
2706 if (wake) in regmap_async_complete_cb()
/linux-4.4.14/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.4.14/fs/xfs/
Dxfs_log.c2629 int wake = 0; in xlog_state_do_callback() local
2823 wake = 1; in xlog_state_do_callback()
2826 if (wake) in xlog_state_do_callback()
/linux-4.4.14/drivers/media/usb/pwc/
Dphilips.txt86 will shut down, but never wake up). Consider this experimental. By
/linux-4.4.14/arch/powerpc/platforms/
DKconfig100 The driver provides a way to wake up the system by MPIC
/linux-4.4.14/Documentation/virtual/kvm/
Dmsr.txt191 kind of token 0xffffffff which tells vcpu that it should wake
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dgpc.fuc351 // ack, and wake up main()
Dhub.fuc370 // ack, and wake up main()
/linux-4.4.14/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.4.14/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.4.14/Documentation/nfc/
Dnfc-hci.txt235 The completion callback will then wake the syscall context.
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt431 Definition: Button can wake-up the system.
/linux-4.4.14/drivers/net/ethernet/intel/ixgbe/
Dixgbe_main.c6019 bool wake; in ixgbe_suspend() local
6021 retval = __ixgbe_shutdown(pdev, &wake); in ixgbe_suspend()
6025 if (wake) { in ixgbe_suspend()
6038 bool wake; in ixgbe_shutdown() local
6040 __ixgbe_shutdown(pdev, &wake); in ixgbe_shutdown()
6043 pci_wake_from_d3(pdev, wake); in ixgbe_shutdown()
/linux-4.4.14/drivers/usb/gadget/
DKconfig121 for a bursty VFS behaviour. For instance there may be CPU wake up
/linux-4.4.14/Documentation/video4linux/
Dvideobuf314 - Mark the buffer as done and wake up the process waiting for it.
/linux-4.4.14/Documentation/arm/
Dcluster-pm-race-avoidance.txt431 Because CPUs may power up asynchronously in response to external wake-up
/linux-4.4.14/include/sound/
Dsoc.h698 bool wake; member
/linux-4.4.14/sound/soc/codecs/
Drt5670.c573 rt5670->hp_gpio.wake = true; in rt5670_set_jack_detect()
/linux-4.4.14/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.4.14/Documentation/sysctl/
Dvm.txt179 The kernel flusher threads will periodically wake up and write `old' data
/linux-4.4.14/drivers/platform/x86/
DKconfig906 sleep state, these devices will wake after either a configured
/linux-4.4.14/drivers/gpio/
DKconfig536 active during S3. The suspend powered GPIOs can be used to wake the
/linux-4.4.14/drivers/net/wireless/
Dairo.c7224 int wake = 0; in airo_set_scan() local
7255 wake = 1; in airo_set_scan()
7259 if (wake) in airo_set_scan()
/linux-4.4.14/Documentation/trace/
Dftrace.txt541 for those interested in wake up timings of RT tasks.
1390 time it takes for a task that is woken to actually wake up.
/linux-4.4.14/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.4.14/Documentation/s390/
DDebugging390.txt1276 is cpu_idle+0x66 ( quiet the cpu is asleep, don't wake it )
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2340 version command is a good way to 'wake it up' before networking has