/linux/Documentation/devicetree/bindings/leds/ |
H A 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 125 # LED indicates USB gadget activity 127 # LED indicates USB host activity 131 # LED is triggered by CPU activity [all …]
|
H A 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/include/linux/input/ |
H A 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/drivers/iio/accel/ |
H A 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/drivers/net/wireless/intel/iwlwifi/fw/api/ |
H A 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 388 * @activity: type of activity, see &enum iwl_roc_activity 389 * @sta_id: station id, resumed during "Remain On Channel" activity. [all …]
|
/linux/drivers/leds/trigger/ |
H A 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.
|
H A D | ledtrig-disk.c | 3 * LED Disk Activity Trigger 34 led_trigger_register_simple("disk-activity", &ledtrig_disk); in ledtrig_disk_init()
|
H A 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()
|
H A 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/Documentation/trace/ |
H A 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/Documentation/ABI/testing/ |
H A 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.
|
H A 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/arch/mips/boot/dts/brcm/ |
H A D | bcm63268-comtrend-vr-3032u.dts | 67 /* EPHY0 Activity */ 72 /* EPHY1 Activity */ 77 /* EPHY2 Activity */ 82 /* GPHY0 Activity */
|
/linux/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/ |
H A D | smu_v13_0_6_pmfw.h | 189 //ACTIVITY 228 // VCN/JPEG ACTIVITY 236 // PER XCD ACTIVITY 307 //ACTIVITY 338 // VCN/JPEG ACTIVITY 396 //ACTIVITY 433 // VCN/JPEG ACTIVITY 441 // PER XCD ACTIVITY
|
/linux/drivers/gpu/drm/i915/ |
H A 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/arch/parisc/include/asm/ |
H A 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 */
|
H A D | pdc_chassis.h | 154 * Source ID, Problem detail, Caller activity, Activity status, 198 /* Caller activity */ 209 /* Activity status - implementation dependent */ 242 #define PDC_CHASSIS_DT_ACT_LEV (15ULL << 59) /* activity level/timeout */
|
/linux/drivers/net/ethernet/mellanox/mlxsw/ |
H A 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/Documentation/devicetree/bindings/devfreq/ |
H A 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/tools/perf/pmu-events/arch/arm64/arm/cortex-a65-e1/ |
H A 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/arch/arm/kernel/ |
H A 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/drivers/usb/common/ |
H A 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
|
/linux/Documentation/input/devices/ |
H A 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
|
/linux/Documentation/accel/qaic/ |
H A 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
|
/linux/drivers/scsi/mvsas/ |
H A D | mv_94xx.h | 124 VSR_PHY_ACT_LED = 0x0C * 4, /* Activity LED control */ 251 MVS_SGPIO_CFG1_MAXACTON_SHIFT = 16, /* max activity on time */ 253 /* force activity off time */ 255 /* stretch activity on time */
|