Searched full:activity (Results 1 – 25 of 92) sorted by relevance
1234
| /Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 90 # LED indicates disk activity
91 - disk-activity
92 # LED indicates disk read activity
94 # LED indicates disk write activity
111 # LED indicates MTD memory activity
113 # LED indicates NAND memory activity (deprecated),
116 # LED indicates network activity
123 # LED indicates USB gadget activity
125 # LED indicates USB host activity
129 # LED is triggered by CPU activity
[all …]
|
| D | leds-bcm6328.yaml | 27 is usually 1:1 for hardware to LED signals, but through the activity/link
96 brcm,activity-signal-sources:
101 An array of hardware activity signal sources. Up to four activity
274 brcm,activity-signal-sources = <0>;
275 /* USB link/activity routed to USB LED */
281 brcm,activity-signal-sources = <1>;
282 /* INET activity routed to INET LED */
332 brcm,activity-signal-sources = <0 1>;
333 /* USB/INET link/activity routed to USB LED */
362 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 | leds-gpio.yaml | 59 linux,default-trigger = "disk-activity";
|
| /Documentation/arch/arm64/ |
| D | amu.rst | 4 Activity Monitors Unit (AMU) extension in AArch64 Linux
11 This document briefly describes the provision of Activity Monitors Unit
18 The activity monitors extension is an optional extension introduced by the
21 The activity monitors unit, implemented in each CPU, provides performance
26 Version 1 of the Activity Monitors architecture implements a counter group
39 The Activity Monitors architecture provides space for up to 16 architected
53 activity monitors extension. Therefore, when CONFIG_ARM64_AMU_EXTN is
|
| /Documentation/trace/ |
| D | events-kmem.rst | 11 - Per-CPU Allocator Activity
25 Heavy activity for these events may indicate that a specific cache is
55 a simple indicator of page allocator activity. Pages may be allocated from
60 amounts of activity imply high activity on the zone->lock. Taking this lock
65 is triggered. Significant amounts of activity here could indicate that the
70 freed in batch with a page list. Significant amounts of activity here could
74 4. Per-CPU Allocator Activity
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-ntrig | 7 start of activity (activating touch).
16 acknowledging the end of activity (deactivating touch).
50 activation and activity.
53 activation and activity.
73 (RO) The range for positions reported during activity.
|
| D | sysfs-block-device | 6 (RW) Used by drivers which support software controlled activity
12 0 OFF - the LED is not activated on activity
13 1 BLINK_ON - the LED blinks on every 10ms when activity is
16 every 10ms when activity is detected.
20 control the activity LED via the em_message file.
|
| /Documentation/devicetree/bindings/devfreq/ |
| D | nvidia,tegra30-actmon.yaml | 7 title: NVIDIA Tegra30 Activity Monitor
15 The activity monitor block collects statistics about the behaviour of other
59 memory clients, see MEMORY CONTROLLER and ACTIVITY MONITOR sections.
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,micfil.yaml | 36 - description: voice activity detector event interrupt
37 - description: voice activity detector error interrupt
|
| /Documentation/input/devices/ |
| D | ntrig.rst | 36 |min_width |both to decide activation and during activity |
39 | |propagating the end of activity events |
55 |sensor_logical_height, | the range for positions reported during activity |
87 seem to have different profiles. Ghost activity typically shows up as small
|
| /Documentation/accel/qaic/ |
| D | qaic.rst | 32 sleep for a time to see if the workload will generate more activity. The IRQ
33 line remains disabled during this time. If no activity is detected, QAIC exits
77 the resources that are loaded onto a device since the majority of that activity
79 roll back userspace activity. To ensure that a userspace client's resources
|
| /Documentation/networking/ |
| D | sctp.rst | 30 module removal of lksctp is not yet a safe activity.
|
| D | smc-sysctl.rst | 40 viability, after the last activity of connections on it. Value 0 means
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-timeout.rst | 41 there's no IR activity for a long time. This can help lircd in
|
| /Documentation/admin-guide/media/ |
| D | mgb4.rst | 354 **activity**:
366 levels (activity bits 5 and 6) using sysfs access or in triggered buffer mode.
367 In the triggered buffer mode you can follow the signal level changes (activity
372 *Note: although the activity sample always contains all the status bits, it makes
|
| /Documentation/devicetree/bindings/iio/imu/ |
| D | invensense,icm42600.yaml | 21 Processing engine for gesture recognition, activity classification, and
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.yaml | 12 activity LEDs and for mapping the ComboPHYs.
|
| /Documentation/devicetree/bindings/net/ |
| D | smsc,lan9115.yaml | 44 up the host system with a 50ms pulse on network activity
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 272 activity via other DMA engine calls not covered in this document.
311 This causes all activity for the DMA channel to be stopped, and may
336 This pauses activity on the DMA channel without data loss.
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 14 space code cannot be executed and the overall system activity is significantly
121 First, when hibernation is triggered, the kernel stops all system activity and
141 activity in the system is stopped and the restore kernel overwrites itself with
|
| D | strategies.rst | 16 which user space code cannot be executed and the overall system activity is
|
| /Documentation/scheduler/ |
| D | completion.rst | 8 If you have one or more threads that must wait for some kernel activity
144 For a thread to wait for some concurrent activity to finish, it
181 time depending on the nature of the activity they are waiting for, so in
|
| /Documentation/usb/ |
| D | iuu_phoenix.rst | 72 So I have added this option to permit him to see a lot of color ( each activity change the color
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 56 application activity. The 'ndbusX/firmware/capability' property will be
|
1234