| /linux-6.12.1/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>;
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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"
129 This allows LEDs to be controlled by network device activity.
143 This allows LEDs to be controlled by activity on ttys which includes
152 Turn LEDs on when there is input (/dev/input/event*) activity and turn
153 them back off again after there has been no activity for 5 seconds.
|
| D | ledtrig-disk.c | 3 * LED Disk Activity Trigger
34 led_trigger_register_simple("disk-activity", &ledtrig_disk); in ledtrig_disk_init()
|
| D | ledtrig-cpu.c | 3 * ledtrig-cpu.c - LED trigger based on CPU activity
16 * activity indication in their code.
168 pr_info("ledtrig-cpu: registered to indicate activity on CPUs\n"); in ledtrig_cpu_init()
|
| D | ledtrig-activity.c | 3 * Activity LED trigger
106 * the activity, up to the point where we have 90ms ON, 10ms OFF when in led_activity_function()
217 .name = "activity",
269 MODULE_DESCRIPTION("Activity LED trigger");
|
| /linux-6.12.1/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
|
| /linux-6.12.1/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 300 * activity.
339 * Activity types for the ROC command
340 * @ROC_ACTIVITY_HOTSPOT: ROC for hs20 activity
341 * @ROC_ACTIVITY_P2P_DISC: ROC for p2p discoverability activity
342 * @ROC_ACTIVITY_P2P_TXRX: ROC for p2p action frames activity
361 * @activity: type of activity, see &enum iwl_roc_activity
362 * @sta_id: station id, resumed during "Remain On Channel" activity.
371 __le32 activity; member
389 * @activity: notification to which activity - &enum iwl_roc_activity
394 __le32 activity; member
[all …]
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 67 /* EPHY0 Activity */
72 /* EPHY1 Activity */
77 /* EPHY2 Activity */
82 /* GPHY0 Activity */
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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 */
|
| /linux-6.12.1/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
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/alderlaken/ |
| D | other.json | 53 …e CPU into the C0.1 activity state. For Tremont, UMWAIT and TPAUSE will only put the CPU into C0.1…
|
| /linux-6.12.1/drivers/net/ethernet/mellanox/mlxsw/ |
| D | spectrum1_acl_tcam.c | 208 bool *activity) in mlxsw_sp1_acl_tcam_region_entry_activity_get() argument
218 *activity = mlxsw_reg_ptce2_a_get(ptce2_pl); in mlxsw_sp1_acl_tcam_region_entry_activity_get()
225 bool *activity) in mlxsw_sp1_acl_tcam_entry_activity_get() argument
234 offset, activity); in mlxsw_sp1_acl_tcam_entry_activity_get()
|
| /linux-6.12.1/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/ |
| D | smu_v13_0_6_pmfw.h | 184 //ACTIVITY
223 // VCN/JPEG ACTIVITY
231 // PER XCD ACTIVITY
292 //ACTIVITY
323 // VCN/JPEG ACTIVITY
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a65-e1/ |
| D | cache.json | 231 …activity in the private L2 cache, and the L3D_CACHE* events count the activity in the DSU L3 cache…
234 …activity in the private L2 cache, and the L3D_CACHE* events count the activity in the DSU L3 cache…
|
| /linux-6.12.1/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_busy.c | 27 * engines. This would be true if we accessed the activity tracking in __busy_write_id()
29 * its activity locklessly we can not guarantee that the last_write in __busy_write_id()
139 * activity with in i915_gem_busy_ioctl()
|
| /linux-6.12.1/arch/arm/kernel/ |
| D | reboot.c | 100 * activity (executing tasks, handling interrupts). smp_send_stop()
112 * activity (executing tasks, handling interrupts). smp_send_stop()
124 * Restart requires that the secondary CPUs stop performing any activity
|
| /linux-6.12.1/drivers/usb/common/ |
| D | Kconfig | 11 This option adds LED triggers for USB host and/or gadget activity.
14 LEDs and you want to use them as activity indicators for USB host or
|