Home
last modified time | relevance | path

Searched full:activity (Results 1 – 25 of 686) sorted by relevance

12345678910>>...28

/linux/include/linux/input/
H A Dadxl34x.h89 * 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 Dmma9553.c76 * 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/Documentation/arch/arm64/
H A Damu.rst4 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/drivers/leds/trigger/
H A DKconfig39 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 Dledtrig-disk.c3 * LED Disk Activity Trigger
34 led_trigger_register_simple("disk-activity", &ledtrig_disk); in ledtrig_disk_init()
H A Dledtrig-cpu.c3 * 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 Dledtrig-activity.c3 * 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 Devents-kmem.rst11 - 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/devicetree/bindings/leds/
H A Dleds-bcm6328.yaml27 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/drivers/net/wireless/intel/iwlwifi/fw/api/
H A Dtime-event.h300 * 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/Documentation/ABI/testing/
H A Dsysfs-driver-hid-ntrig7 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 Dsysfs-block-device6 (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 Dbcm63268-comtrend-vr-3032u.dts67 /* EPHY0 Activity */
72 /* EPHY1 Activity */
77 /* EPHY2 Activity */
82 /* GPHY0 Activity */
/linux/drivers/gpu/drm/i915/
H A Di915_active.h22 * 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 Dled.h14 #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/tools/perf/pmu-events/arch/x86/alderlaken/
H A Dother.json53 …e CPU into the C0.1 activity state. For Tremont, UMWAIT and TPAUSE will only put the CPU into C0.1…
/linux/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/
H A Dsmu_v13_0_6_pmfw.h184 //ACTIVITY
223 // VCN/JPEG ACTIVITY
231 // PER XCD ACTIVITY
292 //ACTIVITY
323 // VCN/JPEG ACTIVITY
/linux/drivers/net/ethernet/mellanox/mlxsw/
H A Dspectrum1_acl_tcam.c208 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 Dnvidia,tegra30-actmon.yaml7 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 Dcache.json231 …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 Dreboot.c100 * 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/gpu/drm/i915/gem/
H A Di915_gem_busy.c27 * 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/drivers/usb/common/
H A DKconfig11 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 Dntrig.rst36 |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/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dtime-event.c400 u32 activity; member
411 if (mvmvif->roc_activity == data->activity) { in iwl_mvm_rx_roc_iterator()
423 u32 activity = le32_to_cpu(notif->activity); in iwl_mvm_rx_roc_notif() local
427 .activity = activity, in iwl_mvm_rx_roc_notif()
772 static void iwl_mvm_roc_rm_cmd(struct iwl_mvm *mvm, u32 activity) in iwl_mvm_roc_rm_cmd() argument
776 .activity = cpu_to_le32(activity), in iwl_mvm_roc_rm_cmd()
1099 int duration, enum iwl_roc_activity activity) in iwl_mvm_roc_add_cmd() argument
1105 .activity = cpu_to_le32(activity), in iwl_mvm_roc_add_cmd()
1130 "Requesting to remain on channel %u for %utu. activity %u\n", in iwl_mvm_roc_add_cmd()
1131 channel->hw_value, duration_tu, activity); in iwl_mvm_roc_add_cmd()
[all …]

12345678910>>...28