| /kernel/linux/linux-6.6/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),
121 # LED indicates USB gadget activity
123 # LED indicates USB host activity
127 # LED is triggered by CPU activity
129 # LED is triggered by Bluetooth activity
[all …]
|
| D | leds-bcm6328.yaml | 27 is usually 1:1 for hardware to LED signals, but through the activity/link
100 brcm,activity-signal-sources:
105 An array of hardware activity signal sources. Up to four activity
278 brcm,activity-signal-sources = <0>;
279 /* USB link/activity routed to USB LED */
285 brcm,activity-signal-sources = <1>;
286 /* INET activity routed to INET LED */
336 brcm,activity-signal-sources = <0 1>;
337 /* USB/INET link/activity routed to USB LED */
366 brcm,activity-signal-sources = <0 1>;
|
| /kernel/linux/linux-5.10/include/linux/input/ |
| D | adxl34x.h | 89 * X/Y/Z Enable: A '1' enables X, Y, or Z participation in activity
96 * to determine whether activity or inactivity is detected. In AC
97 * coupled operation for activity detection, the acceleration value
98 * at the start of activity detection is taken as a reference value.
101 * activity_threshold the device will trigger an activity interrupt. In
125 * holds the threshold value for activity detection.
128 * Activity interrupt is enabled.
225 * LINK: A '1' with both the activity and inactivity functions
226 * enabled will delay the start of the activity function until
227 * inactivity is detected. Once activity is detected, inactivity
[all …]
|
| /kernel/linux/linux-6.6/include/linux/input/ |
| D | adxl34x.h | 89 * X/Y/Z Enable: A '1' enables X, Y, or Z participation in activity
96 * to determine whether activity or inactivity is detected. In AC
97 * coupled operation for activity detection, the acceleration value
98 * at the start of activity detection is taken as a reference value.
101 * activity_threshold the device will trigger an activity interrupt. In
125 * holds the threshold value for activity detection.
128 * Activity interrupt is enabled.
225 * LINK: A '1' with both the activity and inactivity functions
226 * enabled will delay the start of the activity function until
227 * inactivity is detected. Once activity is detected, inactivity
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/accel/ |
| D | mma9553.c | 76 * The internal activity level must be stable for ACTTHD samples before
77 * ACTIVITY is updated. The ACTIVITY variable contains the current activity
94 /* Status register - activity field */
190 u8 activity; member
204 static enum iio_modifier mma9553_activity_to_mod(enum activity_level activity) in mma9553_activity_to_mod() argument
206 switch (activity) { in mma9553_activity_to_mod()
313 u8 *activity, u16 *stepcnt) in mma9553_read_activity_stepcnt() argument
327 *activity = mma9553_get_bits(buf[0], MMA9553_MASK_STATUS_ACTIVITY); in mma9553_read_activity_stepcnt()
346 * If both step detector and activity are enabled, use the MRGFL bit. in mma9553_conf_gpio()
361 /* Save initial values for activity and stepcnt */ in mma9553_conf_gpio()
[all …]
|
| /kernel/linux/linux-6.6/drivers/iio/accel/ |
| D | mma9553.c | 76 * The internal activity level must be stable for ACTTHD samples before
77 * ACTIVITY is updated. The ACTIVITY variable contains the current activity
94 /* Status register - activity field */
190 u8 activity; member
204 static enum iio_modifier mma9553_activity_to_mod(enum activity_level activity) in mma9553_activity_to_mod() argument
206 switch (activity) { in mma9553_activity_to_mod()
313 u8 *activity, u16 *stepcnt) in mma9553_read_activity_stepcnt() argument
327 *activity = mma9553_get_bits(buf[0], MMA9553_MASK_STATUS_ACTIVITY); in mma9553_read_activity_stepcnt()
346 * If both step detector and activity are enabled, use the MRGFL bit. in mma9553_conf_gpio()
361 /* Save initial values for activity and stepcnt */ in mma9553_conf_gpio()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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>;
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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.
|
| 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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/drivers/leds/trigger/ |
| D | Kconfig | 39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
76 tristate "LED activity Trigger"
132 This allows LEDs to be controlled by network device activity.
153 This allows LEDs to be controlled by activity on ttys which includes
|
| /kernel/linux/linux-5.10/drivers/platform/x86/ |
| D | dell-laptop.c | 1005 * bit 3 Auto: ALS- and input-activity-based On; input-activity based Off
1006 * bit 4 Auto: Input-activity-based On; input-activity based Off
1007 * bit 5 Auto: Input-activity-based On (illumination level 25%); input-activity based Off
1008 * bit 6 Auto: Input-activity-based On (illumination level 50%); input-activity based Off
1009 * bit 7 Auto: Input-activity-based On (illumination level 75%); input-activity based Off
1010 * bit 8 Auto: Input-activity-based On (illumination level 100%); input-activity based Off
1020 * bit 1 Touchpad activity
1042 * bit 3 Auto: ALS- and input-activity-based On; input-activity based Off
1043 * bit 4 Auto: Input-activity-based On; input-activity based Off
1044 * bit 5 Auto: Input-activity-based On (illumination level 25%); input-activity based Off
[all …]
|
| /kernel/linux/linux-6.6/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 67 /* EPHY0 Activity */
72 /* EPHY1 Activity */
77 /* EPHY2 Activity */
82 /* GPHY0 Activity */
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 67 /* EPHY0 Activity */
72 /* EPHY1 Activity */
77 /* EPHY2 Activity */
82 /* GPHY0 Activity */
|
| /kernel/linux/linux-6.6/drivers/platform/x86/dell/ |
| D | dell-laptop.c | 1022 * bit 3 Auto: ALS- and input-activity-based On; input-activity based Off
1023 * bit 4 Auto: Input-activity-based On; input-activity based Off
1024 * bit 5 Auto: Input-activity-based On (illumination level 25%); input-activity based Off
1025 * bit 6 Auto: Input-activity-based On (illumination level 50%); input-activity based Off
1026 * bit 7 Auto: Input-activity-based On (illumination level 75%); input-activity based Off
1027 * bit 8 Auto: Input-activity-based On (illumination level 100%); input-activity based Off
1037 * bit 1 Touchpad activity
1059 * bit 3 Auto: ALS- and input-activity-based On; input-activity based Off
1060 * bit 4 Auto: Input-activity-based On; input-activity based Off
1061 * bit 5 Auto: Input-activity-based On (illumination level 25%); input-activity based Off
[all …]
|
| /kernel/linux/linux-6.6/arch/parisc/include/asm/ |
| D | led.h | 14 #define LED_LAN_RCV LED0 /* for LAN receive activity */
15 #define LED_LAN_TX LED1 /* for LAN transmit activity */
16 #define LED_DISK_IO LED2 /* for disk activity */
|
| /kernel/linux/linux-5.10/arch/parisc/include/asm/ |
| D | led.h | 14 #define LED_LAN_RCV LED0 /* for LAN receive activity */
15 #define LED_LAN_TX LED1 /* for LAN transmit activity */
16 #define LED_DISK_IO LED2 /* for disk activity */
|
| /kernel/linux/linux-5.10/drivers/leds/trigger/ |
| D | Kconfig | 39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
75 tristate "LED activity Trigger"
130 This allows LEDs to be controlled by network device activity.
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/ |
| D | i915_active.h | 22 * We use the fences to synchronize access from the CPU with activity on the
51 * __i915_active_fence_init - prepares the activity tracker for use
58 * an activity tracker, that is for tracking the last known active fence
127 * GPU activity tracking
146 * different resources that need to track their associated GPU activity to
147 * provide a callback when that GPU activity has ceased, or otherwise to
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_active.h | 22 * We use the fences to synchronize access from the CPU with activity on the
51 * __i915_active_fence_init - prepares the activity tracker for use
58 * an activity tracker, that is for tracking the last known active fence
127 * GPU activity tracking
146 * different resources that need to track their associated GPU activity to
147 * provide a callback when that GPU activity has ceased, or otherwise to
|