| /linux/Documentation/ABI/testing/ |
| 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.
|
| 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/Documentation/devicetree/bindings/leds/ |
| 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
116 # LED indicates network activity
123 # LED indicates USB gadget activity
125 # LED indicates USB host activity
129 # LED is triggered by CPU activity
133 # LED is triggered by SD/MMC activity
[all …]
|
| 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/drivers/iio/accel/ |
| A D | mma9553.c | 190 u8 activity; member
206 switch (activity) { in mma9553_activity_to_mod()
313 u8 *activity, u16 *stepcnt) in mma9553_read_activity_stepcnt() argument
469 u8 activity; in mma9553_read_raw() local
497 activity = in mma9553_read_raw()
505 if (chan->channel2 == mma9553_activity_to_mod(activity)) in mma9553_read_raw()
1009 u8 activity; in mma9553_event_handler() local
1022 data->activity), in mma9553_event_handler()
1025 mma9553_activity_to_mod(activity), in mma9553_event_handler()
1039 if (activity != data->activity) { in mma9553_event_handler()
[all …]
|
| /linux/drivers/leds/trigger/ |
| 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.
|
| A D | Makefile | 10 obj-$(CONFIG_LEDS_TRIGGER_ACTIVITY) += ledtrig-activity.o
|
| /linux/drivers/net/ethernet/mellanox/mlxsw/ |
| 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()
|
| A D | spectrum_acl_flex_actions.c | 65 bool *activity) in mlxsw_sp1_act_kvdl_set_activity_get() argument
71 bool *activity) in mlxsw_sp2_act_kvdl_set_activity_get() argument
81 mlxsw_reg_pefa_unpack(pefa_pl, activity); in mlxsw_sp2_act_kvdl_set_activity_get()
|
| A D | core_acl_flex_actions.h | 19 bool *activity);
52 int mlxsw_afa_block_activity_get(struct mlxsw_afa_block *block, bool *activity);
|
| A D | spectrum2_acl_tcam.c | 254 bool *activity) in mlxsw_sp2_acl_tcam_entry_activity_get() argument
258 return mlxsw_afa_block_activity_get(entry->act_block, activity); in mlxsw_sp2_acl_tcam_entry_activity_get()
|
| /linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| A D | time-event.c | 400 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()
1131 channel->hw_value, duration_tu, activity); in iwl_mvm_roc_add_cmd()
1139 mvmvif->roc_activity = activity; in iwl_mvm_roc_add_cmd()
|
| /linux/Documentation/trace/ |
| A D | events-kmem.rst | 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
|
| /linux/net/ipv6/ |
| A D | calipso.c | 80 u32 activity; member
218 entry->activity += 1; in calipso_cache_check()
228 if (prev_entry->activity > 0) in calipso_cache_check()
229 prev_entry->activity -= 1; in calipso_cache_check()
230 if (entry->activity > prev_entry->activity && in calipso_cache_check()
231 entry->activity - prev_entry->activity > in calipso_cache_check()
|
| /linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| A D | time-event.h | 371 __le32 activity; member
394 __le32 activity; member
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | fsl,micfil.yaml | 36 - description: voice activity detector event interrupt
37 - description: voice activity detector error interrupt
|
| /linux/drivers/usb/common/ |
| 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/arch/arm64/ |
| A D | amu.rst | 18 The activity monitors extension is an optional extension introduced by the
21 The activity monitors unit, implemented in each CPU, provides performance
53 activity monitors extension. Therefore, when CONFIG_ARM64_AMU_EXTN is
|
| /linux/Documentation/input/devices/ |
| 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/arch/arm64/boot/dts/marvell/ |
| A D | cn9131-cf-solidwan.dts | 72 led-sfp1-activity {
84 led-sfp0-activity {
284 * - LED[1]: link/activity: On/blink (green)
497 * - LED[1]: link/activity: On/blink (green)
527 * - LED[1]: link/activity: On/blink (green)
|
| A D | cn9130-cf-base.dts | 66 * - LED[0]: link/activity: On/blink (green)
106 * - LED[0]: link/activity: On/blink (green)
|
| /linux/arch/arm/boot/dts/marvell/ |
| A D | kirkwood-ns2lite.dts | 30 linux,default-trigger = "disk-activity";
|
| /linux/net/ipv4/ |
| A D | cipso_ipv4.c | 69 u32 activity; member
252 entry->activity += 1; in cipso_v4_cache_check()
262 if (prev_entry->activity > 0) in cipso_v4_cache_check()
263 prev_entry->activity -= 1; in cipso_v4_cache_check()
264 if (entry->activity > prev_entry->activity && in cipso_v4_cache_check()
265 entry->activity - prev_entry->activity > in cipso_v4_cache_check()
|
| /linux/arch/arm/boot/dts/sigmastar/ |
| A D | mstar-infinity-breadbee-common.dtsi | 38 linux,default-trigger = "activity";
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| A D | rk3568-qnap-ts433.dts | 53 linux,default-trigger = "disk-activity";
62 linux,default-trigger = "disk-activity";
71 linux,default-trigger = "disk-activity";
80 linux,default-trigger = "disk-activity";
|