| /linux-6.3-rc2/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-6.3-rc2/Documentation/devicetree/bindings/leds/ |
| 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>;
|
| A D | common.yaml | 91 # LED indicates disk activity
92 - disk-activity
104 # LED is triggered by Bluetooth activity
106 # LED is triggered by SD/MMC activity
108 # LED is triggered by WLAN activity
149 activity. Some LEDs can be related to a specific device and should somehow
|
| A D | leds-ns2.txt | 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
|
| /linux-6.3-rc2/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-6.3-rc2/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()
|
| A D | spectrum_acl_tcam.c | 1079 bool *activity) in mlxsw_sp_acl_tcam_entry_activity_get() argument
1084 entry->priv, activity); in mlxsw_sp_acl_tcam_entry_activity_get()
1154 bool *activity) in mlxsw_sp_acl_tcam_ventry_activity_get() argument
1157 ventry->entry, activity); in mlxsw_sp_acl_tcam_ventry_activity_get()
1742 void *rule_priv, bool *activity) in mlxsw_sp_acl_tcam_flower_rule_activity_get() argument
1747 activity); in mlxsw_sp_acl_tcam_flower_rule_activity_get()
1880 void *rule_priv, bool *activity) in mlxsw_sp_acl_tcam_mr_rule_activity_get() argument
1882 *activity = false; in mlxsw_sp_acl_tcam_mr_rule_activity_get()
|
| /linux-6.3-rc2/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-6.3-rc2/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"
131 This allows LEDs to be controlled by network device activity.
152 This allows LEDs to be controlled by activity on ttys which includes
|
| A D | Makefile | 10 obj-$(CONFIG_LEDS_TRIGGER_ACTIVITY) += ledtrig-activity.o
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/sound/ |
| A D | fsl,micfil.yaml | 30 - description: voice activity detector event interrupt
31 - description: voice activity detector error interrupt
|
| /linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/Documentation/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-6.3-rc2/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-6.3-rc2/arch/arm/boot/dts/ |
| A D | kirkwood-ns2lite.dts | 30 linux,default-trigger = "disk-activity";
|
| A D | mstar-infinity-breadbee-common.dtsi | 38 linux,default-trigger = "activity";
|
| /linux-6.3-rc2/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-6.3-rc2/drivers/s390/virtio/ |
| A D | virtio_ccw.c | 1083 __u32 activity) in virtio_ccw_check_activity() argument
1085 if (vcdev->curr_io & activity) { in virtio_ccw_check_activity()
1086 switch (activity) { in virtio_ccw_check_activity()
1100 vcdev->curr_io &= ~activity; in virtio_ccw_check_activity()
1106 "Suspicious activity '%08x'\n", activity); in virtio_ccw_check_activity()
1117 __u32 activity = intparm & VIRTIO_CCW_INTPARM_MASK; in virtio_ccw_int_handler() local
1126 virtio_ccw_check_activity(vcdev, activity); in virtio_ccw_int_handler()
1145 virtio_ccw_check_activity(vcdev, activity); in virtio_ccw_int_handler()
|
| /linux-6.3-rc2/arch/mips/boot/dts/ralink/ |
| A D | mt7621-gnubee-gb-pc1.dts | 45 linux,default-trigger = "disk-activity";
|
| /linux-6.3-rc2/include/uapi/misc/ |
| A D | xilinx_sdfec.h | 199 __s8 activity; member
|