| /linux-4.4.14/drivers/staging/unisys/visorinput/ |
| D | visorinput.c | 543 scancode = r.activity.arg1; in visorinput_channel_interrupt()
545 switch (r.activity.action) { in visorinput_channel_interrupt()
562 r.activity.arg2); in visorinput_channel_interrupt()
565 xmotion = r.activity.arg1; in visorinput_channel_interrupt()
566 ymotion = r.activity.arg2; in visorinput_channel_interrupt()
572 button = calc_button(r.activity.arg1); in visorinput_channel_interrupt()
579 button = calc_button(r.activity.arg1); in visorinput_channel_interrupt()
586 button = calc_button(r.activity.arg1); in visorinput_channel_interrupt()
596 button = calc_button(r.activity.arg1); in visorinput_channel_interrupt()
607 zmotion = r.activity.arg1; in visorinput_channel_interrupt()
[all …]
|
| D | ultrainputreport.h | 71 struct ultra_inputactivity activity; member
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 16 is usually 1:1 for hardware to LED signals, but through the activity/link
65 - brcm,activity-signal-sources : An array of hardware activity
66 signal sources. Up to four activity hardware signals can get muxed into
206 brcm,activity-signal-sources = <0>;
207 /* USB link/activity routed to USB LED */
212 brcm,activity-signal-sources = <1>;
213 /* INET activity routed to INET LED */
258 brcm,activity-signal-sources = <0 1>;
259 /* USB/INET link/activity routed to USB LED */
286 brcm,activity-signal-sources = <0 1>;
|
| D | leds-ns2.txt | 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
|
| D | common.txt | 29 "ide-disk" - LED indicates disk activity
|
| /linux-4.4.14/drivers/iio/accel/ |
| D | mma9553.c | 199 u8 activity; member
213 static enum iio_modifier mma9553_activity_to_mod(enum activity_level activity) in mma9553_activity_to_mod() argument
215 switch (activity) { in mma9553_activity_to_mod()
322 u8 *activity, u16 *stepcnt) in mma9553_read_activity_stepcnt() argument
336 *activity = mma9553_get_bits(buf[0], MMA9553_MASK_STATUS_ACTIVITY); in mma9553_read_activity_stepcnt()
372 ret = mma9553_read_activity_stepcnt(data, &data->activity, in mma9553_conf_gpio()
478 u8 activity; in mma9553_read_raw() local
506 activity = in mma9553_read_raw()
514 if (chan->channel2 == mma9553_activity_to_mod(activity)) in mma9553_read_raw()
1019 u8 activity; in mma9553_event_handler() local
[all …]
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-kmem.txt | 21 Heavy activity for these events may indicate that a specific cache is
47 a simple indicator of page allocator activity. Pages may be allocated from
52 amounts of activity imply high activity on the zone->lock. Taking this lock
57 is triggered. Significant amounts of activity here could indicate that the
62 freed in batch with a page list. Significant amounts of activity here could
|
| /linux-4.4.14/Documentation/input/ |
| D | ntrig.txt | 31 min_width both to decide activation and during activity
34 propagating the end of activity events
47 sensor_logical_height the range for positions reported during activity
76 seem to have different profiles. Ghost activity typically shows up as small
|
| D | atarikbd.txt | 364 matrix activity is still monitored and scan codes or ASCII characters enqueued
|
| /linux-4.4.14/drivers/s390/virtio/ |
| D | virtio_ccw.c | 988 __u32 activity) in virtio_ccw_check_activity() argument
990 if (vcdev->curr_io & activity) { in virtio_ccw_check_activity()
991 switch (activity) { in virtio_ccw_check_activity()
1004 vcdev->curr_io &= ~activity; in virtio_ccw_check_activity()
1010 "Suspicious activity '%08x'\n", activity); in virtio_ccw_check_activity()
1021 __u32 activity = intparm & VIRTIO_CCW_INTPARM_MASK; in virtio_ccw_int_handler() local
1030 virtio_ccw_check_activity(vcdev, activity); in virtio_ccw_int_handler()
1049 virtio_ccw_check_activity(vcdev, activity); in virtio_ccw_int_handler()
|
| /linux-4.4.14/net/ipv4/ |
| D | cipso_ipv4.c | 83 u32 activity; member
337 entry->activity += 1; in cipso_v4_cache_check()
347 if (prev_entry->activity > 0) in cipso_v4_cache_check()
348 prev_entry->activity -= 1; in cipso_v4_cache_check()
349 if (entry->activity > prev_entry->activity && in cipso_v4_cache_check()
350 entry->activity - prev_entry->activity > in cipso_v4_cache_check()
|
| /linux-4.4.14/arch/cris/boot/dts/ |
| D | p1343.dts | 70 activity-button@0 {
|
| /linux-4.4.14/arch/cris/ |
| D | Kconfig | 323 connection and will flash off when there is activity.
326 there is activity.
328 This setting will also affect the behaviour of other activity LEDs
335 connection and will flash off when there is activity.
338 there is activity.
340 This setting will also affect the behaviour of other activity LEDs
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra30-actmon.txt | 3 The activity monitor block collects statistics about the behaviour of other
|
| /linux-4.4.14/Documentation/networking/ |
| D | sctp.txt | 25 module removal of lksctp is not yet a safe activity.
|
| D | netdevices.txt | 105 NAPI activity to cease.
|
| D | 3c509.txt | 132 keyboard activity.
|
| D | arcnet-hardware.txt | 716 The green LED monitors the network activity: the red one shows the
717 board activity:
721 on | normal activity flash/on | data transfer
943 The green LED monitors the network activity: the red one shows the
944 board activity:
948 on | normal activity flash/on | data transfer
|
| D | vortex.txt | 247 port if it didn't detect activity on the 10baseT port. It would then
|
| D | cs89x0.txt | 433 adapter's cable is connected to the network (check for LED activity for
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | client.txt | 149 activity via other DMA engine calls not covered in this document.
171 This causes all activity for the DMA channel to be stopped, and may
177 This pauses activity on the DMA channel without data loss.
|
| /linux-4.4.14/net/sunrpc/ |
| D | Kconfig | 44 logging of different aspects of the kernel RPC activity.
|
| /linux-4.4.14/drivers/usb/ |
| D | Kconfig | 158 This option adds LED triggers for USB host and/or gadget activity.
161 LEDs and you want to use them as activity indicators for USB host or
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 110 channel for activity
125 visorchannel_signalremove() functions to respond to and initiate activity
314 As the s-Par back-end reports keyboard and mouse activity via events on the
315 virtual device channel, the visorinput driver delivers the activity to the
|
| D | proc-entries.txt | 18 to signify that any user level activity has been completed before the
|
| /linux-4.4.14/arch/mips/sibyte/ |
| D | Kconfig | 158 buffer activity. Raw buffer data is dumped to console, and
|
| /linux-4.4.14/drivers/net/ethernet/chelsio/cxgb3/ |
| D | adapter.h | 76 int activity; member
|
| /linux-4.4.14/Documentation/usb/ |
| D | iuu_phoenix.txt | 63 So I have added this option to permit him to see a lot of color ( each activity change the color
|
| D | WUSB-Design-overview.txt | 328 per-device activity timestamp. If not, every now and then we check and
329 if the activity timestamp gets old, we ping the device by sending it a
|
| D | power-management.txt | 336 force the drivers for those interface to stop all activity) without
|
| /linux-4.4.14/drivers/ata/ |
| D | ahci.h | 295 unsigned long activity; member
|
| D | libahci.c | 894 emp->activity++; in ahci_sw_activity()
917 if (emp->saved_activity != emp->activity) { in ahci_sw_activity_blink()
918 emp->saved_activity = emp->activity; in ahci_sw_activity_blink()
950 emp->saved_activity = emp->activity = 0; in ahci_init_sw_activity()
|
| /linux-4.4.14/Documentation/fb/ |
| D | sh7760fb.txt | 21 b) during PCMCIA (or any other slow bus) activity.
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | kirkwood-netgear_readynas_duo_v2.dts | 63 pmx_led_blue_activity: pmx-led-blue-activity {
|
| /linux-4.4.14/drivers/leds/trigger/ |
| D | Kconfig | 41 This allows LEDs to be controlled by IDE disk activity.
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-timechart.txt | 20 but it's possible to record IO (disk, network) activity using -I argument.
|
| D | perf-script-python.txt | 340 rw-by-file <comm> r/w activity for a program, by file
341 rw-by-pid system-wide r/w activity
405 rw-by-file <comm> r/w activity for a program, by file
406 rw-by-pid system-wide r/w activity
|
| /linux-4.4.14/drivers/w1/slaves/ |
| D | w1_ds2408.c | 321 static BIN_ATTR_RW(activity, 1);
|
| /linux-4.4.14/arch/mips/boot/dts/cavium-octeon/ |
| D | octeon_3xxx.dts | 66 /* irq, blink-activity, blink-link */
78 /* irq, blink-activity, blink-link */
|
| D | octeon_68xx.dts | 67 /* irq, blink-activity, blink-link */
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | smm665 | 80 and/or other activity. Triggered signals can include HEALTHY, RST, Power Off,
|
| /linux-4.4.14/drivers/isdn/i4l/ |
| D | Kconfig | 43 activity (i.e. which packets will reset the idle timer or bring up
|
| /linux-4.4.14/Documentation/vm/ |
| D | ksm.txt | 93 pages_volatile embraces several different kinds of activity, but a high
|
| /linux-4.4.14/drivers/net/can/ |
| D | Kconfig | 64 LEDs and you want to use them as canbus activity indicators.
|
| /linux-4.4.14/kernel/time/ |
| D | Kconfig | 106 the task mostly runs in userspace and has few kernel activity.
|
| /linux-4.4.14/sound/soc/codecs/ |
| D | rt5677.c | 704 static bool activity; in rt5677_set_dsp_vad() local
710 if (on && !activity) { in rt5677_set_dsp_vad()
711 activity = true; in rt5677_set_dsp_vad()
763 } else if (!on && activity) { in rt5677_set_dsp_vad()
764 activity = false; in rt5677_set_dsp_vad()
|
| /linux-4.4.14/Documentation/ |
| D | SubmittingDrivers | 143 Weekly summary of kernel development activity - http://lwn.net/
|
| D | iostats.txt | 6 activity. Tools such as sar and iostat typically interpret these and do
|
| D | DMA-API-HOWTO.txt | 580 You should call dma_unmap_single() when the DMA activity is finished, e.g.,
614 You should call dma_unmap_page() when the DMA activity is finished, e.g.,
645 Again, make sure DMA activity has already finished.
|
| D | kernel-per-CPU-kthreads.txt | 62 Bluetooth activity on some other CPU.
|
| D | cpu-hotplug.txt | 307 This will stop the activity and send a following CANCELED event back.
|
| D | md.txt | 231 requires a metadata update will cause array activity to be
|
| /linux-4.4.14/Documentation/arm/ |
| D | vlocks.txt | 8 These are intended to be used to coordinate critical activity among CPUs
|
| /linux-4.4.14/drivers/net/ppp/ |
| D | Kconfig | 77 activity (i.e. which packets will reset the idle timer or bring up
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head.S | 236 bnz .Lwaitforirq # activity or status control
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 19 preventing any other write activity on the file system during a
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 148 - Use of LED by user space app as activity indicator.
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci.txt | 58 Stop all DMA activity
423 Stop all DMA activity
458 4.3 Stop all DMA activity
|
| D | pci-error-recovery.txt | 346 The goal of this callback is to tell the driver to restart activity,
|
| /linux-4.4.14/Documentation/isdn/ |
| D | syncPPP.FAQ | 204 you can see, whether there is activity on the card/line.
|
| /linux-4.4.14/drivers/macintosh/ |
| D | Kconfig | 111 so that it blinks on IDE activity.
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | dapm.txt | 16 activity and audio mixer settings within the device.
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | sysfs-fs-lustre | 563 to lack of write activity on this client.
569 Number of seconds with no write activity for this target
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/dvm/ |
| D | rx.c | 470 bt_activity = &stats->general.activity; in iwlagn_rx_statistics()
|
| D | commands.h | 2736 struct statistics_bt_activity activity; member
|
| /linux-4.4.14/Documentation/laptops/ |
| D | laptop-mode.txt | 98 this results in concentration of disk activity in a small time interval which
110 the output of block_dump will be logged, causing disk activity that is not
|
| /linux-4.4.14/Documentation/RCU/ |
| D | trace.txt | 23 so that activity for both appears in rcu/rcu_sched.
172 been registered in absence of CPU-hotplug activity.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-iio | 385 to compute the stride length, distance, speed and activity
405 to compute the stride length, distance, speed and activity
1180 This attribute is used to read the confidence for an activity
1206 device (e.g.: human activity sensors report energy burnt by the
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | fuse.txt | 137 no filesystem activity and 'waiting' is non-zero, then the
|
| D | vfs.txt | 855 activity on this file and (optionally) go to sleep until there
856 is activity. Called by the select(2) and poll(2) system calls
|
| D | proc.txt | 1274 Various pieces of information about kernel activity are available in the
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig | 1268 such as GPIO interrupt or RTC activity wakes up the processor.
1281 this mode. Typically an external event or RTC activity will wake
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | paride.txt | 387 activity as they attempt to locate your drive.
|
| /linux-4.4.14/Documentation/power/ |
| D | devices.txt | 44 running, independently of other power management activity in principle.
73 network wake-on-LAN packets, keyboard or mouse activity, and media insertion
|
| D | pci.txt | 624 activity can be resumed.
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | ide-cd | 271 operations with other disk activity.
|
| D | cdrom-standard.tex | 891 current playing activity of the drive; this can be polled through an
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 346 comments for the future; indeed, this can be a useful activity for
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 629 post-attachment activity that requires memory allocations or blocking.
|
| D | memory.txt | 783 allocations. Monitoring this reclaiming activity might be useful for
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 759 invalidates any backing objects and waits for cessation of activity on any
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.lpfc | 1511 * Moved FCP activity to ring 0. Moved ELS/CT activity to ring 2.
|
| D | scsi_mid_low_api.txt | 1147 * activity has ceased on this device.
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 760 This can be used to turn a spare LED into a network activity LED,
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 916 during inactivity periods (includes interrupt activity monitoring).
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 224 * wait until any select-out activity has halted, and
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 2914 you the low-level activity of the virtual machine.
|