/openbmc/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), 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 …]
|
H A 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>;
|
/openbmc/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 …]
|
/openbmc/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 …]
|
/openbmc/linux/Documentation/arch/arm64/ |
H A 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
|
/openbmc/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
|
/openbmc/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.
|
/openbmc/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" 132 This allows LEDs to be controlled by network device activity. 153 This allows LEDs to be controlled by activity on ttys which includes
|
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()
|
/openbmc/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 */
|
/openbmc/openbmc/.github/ |
H A D | stale.yml | 14 This issue has been automatically marked as stale because no activity has 15 occurred in the last 6 months. It will be closed if no activity occurs in the 21 This issue has been closed because no activity has occurred in the last 7
|
/openbmc/linux/drivers/platform/x86/dell/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/atop/ |
H A D | atop_2.4.0.bb | 1 SUMMARY = "Monitor for system resources and process activity" 3 is capable of reporting the activity of all processes (even if processes have \ 4 finished during the interval), daily logging of system and process activity for \ 6 etc. At regular intervals, it shows system-level activity related to the CPU, \
|
/openbmc/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 */
|
/openbmc/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
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
H A D | other.json | 50 …e CPU into the C0.1 activity state. For Tremont, UMWAIT and TPAUSE will only put the CPU into C0.1…
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/iptraf/ |
H A D | iptraf-ng_1.2.1.bb | 7 and activity indicators, TCP/UDP traffic breakdowns, and LAN station \ 12 packet counts, IP checksum errors, interface activity and packet size \ 16 about their activity; TCP, UDP and other protocol display filters so \
|
/openbmc/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()
|
/openbmc/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.
|
/openbmc/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…
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
H A D | Progress.interface.yaml | 2 Implement to provide the progress on user requested activity. Objects which 30 Status of the activity
|
/openbmc/linux/Documentation/accel/qaic/ |
H A D | qaic.rst | 29 sleep for a time to see if the workload will generate more activity. The IRQ 30 line remains disabled during this time. If no activity is detected, QAIC exits 54 the resources that are loaded onto a device since the majority of that activity 56 roll back userspace activity. To ensure that a userspace client's resources
|
/openbmc/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
|