Home
last modified time | relevance | path

Searched +full:echo +full:- +full:active +full:- +full:ms (Results 1 – 25 of 124) sorted by relevance

12345

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pps/
Dpps-gpio.txt1 Device-Tree Bindings for a PPS Signal on GPIO
3 These properties describe a PPS (pulse-per-second) signal connected to
7 - compatible: should be "pps-gpio"
8 - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt
10 Additional required properties for the PPS ECHO functionality:
11 - echo-gpios: one PPS ECHO GPIO in the format described by ../gpio/gpio.txt
12 - echo-active-ms: duration in ms of the active portion of the echo pulse
15 - assert-falling-edge: when present, assert is indicated by a falling edge
20 pinctrl-names = "default";
21 pinctrl-0 = <&pinctrl_pps>;
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/pps/
Dpps-gpio.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pps/pps-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Fabio Estevam <festevam@gmail.com>
14 const: pps-gpio
20 echo-gpios:
21 description: The GPIO that provides the PPS ECHO signal.
24 echo-active-ms:
25 description: Duration in ms of the active portion of the echo pulse.
[all …]
/kernel/linux/linux-6.6/drivers/pps/clients/
Dpps-gpio.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * pps-gpio.c -- PPS client driver using GPIO
9 #define PPS_GPIO_NAME "pps-gpio"
33 struct timer_list echo_timer; /* timer to reset echo active state */
36 unsigned int echo_active_ms; /* PPS echo active duration */
55 rising_edge = gpiod_get_value(info->gpio_pin); in pps_gpio_irq_handler()
56 if ((rising_edge && !info->assert_falling_edge) || in pps_gpio_irq_handler()
57 (!rising_edge && info->assert_falling_edge)) in pps_gpio_irq_handler()
58 pps_event(info->pps, &ts, PPS_CAPTUREASSERT, data); in pps_gpio_irq_handler()
59 else if (info->capture_clear && in pps_gpio_irq_handler()
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dds1621.rst47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
58 * 0 = active high,
59 * 1 = active low
62 -----------
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
75 ("cooler"), vice versa. That way "heater" equals "active low", whereas
[all …]
/kernel/linux/linux-5.10/Documentation/hwmon/
Dds1621.rst47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
58 * 0 = active high,
59 * 1 = active low
62 -----------
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
75 ("cooler"), vice versa. That way "heater" equals "active low", whereas
[all …]
/kernel/linux/linux-5.10/drivers/pps/clients/
Dpps-gpio.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * pps-gpio.c -- PPS client driver using GPIO
9 #define PPS_GPIO_NAME "pps-gpio"
19 #include <linux/pps-gpio.h>
34 struct timer_list echo_timer; /* timer to reset echo active state */
37 unsigned int echo_active_ms; /* PPS echo active duration */
56 rising_edge = gpiod_get_value(info->gpio_pin); in pps_gpio_irq_handler()
57 if ((rising_edge && !info->assert_falling_edge) || in pps_gpio_irq_handler()
58 (!rising_edge && info->assert_falling_edge)) in pps_gpio_irq_handler()
59 pps_event(info->pps, &ts, PPS_CAPTUREASSERT, data); in pps_gpio_irq_handler()
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/
Ddevlink_linecard.sh2 # SPDX-License-Identifier: GPL-2.0
5 # LC_SLOT - If not set, all probed line cards are going to be tested,
28 echo "$current"
41 devlink lc show $DEVLINK_DEV lc $lc -j | jq -e -r ".[][][].state"
48 local timeout=$3 # ms
57 local timeout=$3 # ms
67 echo "$current"
75 devlink port -j | jq -e -r ".[][] | select(.lc==$lc) | .port" | wc -l
82 local timeout=$3 # ms
91 devlink lc show $DEVLINK_DEV lc $lc -j | jq -e -r ".[][][].nested_devlink"
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/irq/
Dirq-affinity.rst6 - Started by Ingo Molnar <mingo@redhat.com>
7 - Update by Max Krasnyansky <maxk@qualcomm.com>
17 to all non-active IRQs. Once IRQ is allocated/activated its affinity bitmask
21 Here is an example of restricting IRQ44 (eth1) to CPU0-3 then restricting
22 it to CPU4-7 (this is an 8-CPU SMP box)::
28 [root@moon 44]# echo 0f > smp_affinity
31 [root@moon 44]# ping -f h
34 --- hell ping statistics ---
36 round-trip min/avg/max = 0.1/0.1/0.4 ms
39 … 1785 1785 1783 0 0 0 0 IO-APIC-level eth1
[all …]
/kernel/linux/linux-6.6/Documentation/core-api/irq/
Dirq-affinity.rst6 - Started by Ingo Molnar <mingo@redhat.com>
7 - Update by Max Krasnyansky <maxk@qualcomm.com>
17 to all non-active IRQs. Once IRQ is allocated/activated its affinity bitmask
21 Here is an example of restricting IRQ44 (eth1) to CPU0-3 then restricting
22 it to CPU4-7 (this is an 8-CPU SMP box)::
28 [root@moon 44]# echo 0f > smp_affinity
31 [root@moon 44]# ping -f h
34 --- hell ping statistics ---
36 round-trip min/avg/max = 0.1/0.1/0.4 ms
39 … 1785 1785 1783 0 0 0 0 IO-APIC-level eth1
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dleds-trigger-pattern.txt3 The pattern is given by a series of tuples, of brightness and duration (ms).
6 new value, and writing malformed pattern deactivates any active one.
9 the tuple with duration less than dimming interval (50ms) is treated as a step
17 echo 0 1000 255 2000 > pattern
19 It will make the LED go gradually from zero-intensity to max (255) intensity in
24 255-| / \ / \ /
28 0-| / \/ \/
29 +---0----1----2----3----4----5----6------------> time (s)
32 use zero-time lengths (the brightness must be same as the previous tuple's). So
37 echo 0 1000 0 0 255 2000 255 0 > pattern
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/
Dleds-trigger-pattern.txt3 The pattern is given by a series of tuples, of brightness and duration (ms).
6 new value, and writing malformed pattern deactivates any active one.
9 the tuple with duration less than dimming interval (50ms) is treated as a step
17 echo 0 1000 255 2000 > pattern
19 It will make the LED go gradually from zero-intensity to max (255) intensity in
24 255-| / \ / \ /
28 0-| / \/ \/
29 +---0----1----2----3----4----5----6------------> time (s)
32 use zero-time lengths (the brightness must be same as the previous tuple's). So
37 echo 0 1000 0 0 255 2000 255 0 > pattern
[all …]
/kernel/linux/linux-6.6/Documentation/scheduler/
Dsched-deadline.rst12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
86 ---------------------------------- > ---------
87 scheduling deadline - current time period
[all …]
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-deadline.rst12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
86 ---------------------------------- > ---------
87 scheduling deadline - current time period
[all …]
/kernel/linux/linux-6.6/Documentation/networking/
Dbonding.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
119 -----------------------------------------------
[all …]
/kernel/linux/linux-5.10/Documentation/networking/
Dbonding.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
119 -----------------------------------------------
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/damon/
Dlru_sort.rst1 .. SPDX-License-Identifier: GPL-2.0
4 DAMON-based LRU-lists Sorting
7 DAMON-based LRU-lists Sorting (DAMON_LRU_SORT) is a static kernel module that
9 (de)prioritization of pages on their LRU-lists for making LRU-lists a more
12 Where Proactive LRU-lists Sorting is Required?
15 As page-granularity access checking overhead could be significant on huge
23 Because DAMON can identify access patterns of best-effort accuracy while
24 inducing only user-specified range of overhead, proactively running
32 rates that higher than a user-specified threshold) and cold pages (pages of
34 user-specified threshold) using DAMON, and prioritizes hot pages while
[all …]
Dreclaim.rst1 .. SPDX-License-Identifier: GPL-2.0
4 DAMON-based Reclamation
7 DAMON-based Reclamation (DAMON_RECLAIM) is a static kernel module that aimed to
9 It doesn't aim to replace the LRU-list based page_granularity reclamation, but
15 On general memory over-committed systems, proactively reclaiming cold pages
20 Free Pages Reporting [3]_ based memory over-commit virtualization systems are
24 guests could be not so memory-frugal, mainly because some kernel subsystems and
25 user-space applications are designed to use as much memory as available. Then,
54 -------
60 no real monitoring and reclamation due to the watermarks-based activation
[all …]
/kernel/linux/linux-5.10/drivers/net/wireless/marvell/libertas/
DREADME4 (c) Copyright © 2003-2006, Marvell International Ltd.
14 THE FILE IS DISTRIBUTED AS-IS, WITHOUT WARRANTY OF ANY KIND, AND THE
35 Use the -i option to retrieve version information from the driver.
37 # ethtool -i eth0
39 version: COMM-USB8388-318.p4
40 firmware-version: 5.110.7
41 bus-info:
43 Use the -e option to read the EEPROM contents of the card.
46 ethtool -e ethX [raw on|off] [offset N] [length N]
48 -e retrieves and prints an EEPROM dump for the specified ethernet
[all …]
/kernel/linux/linux-6.6/drivers/net/wireless/marvell/libertas/
DREADME4 (c) Copyright © 2003-2006, Marvell International Ltd.
14 THE FILE IS DISTRIBUTED AS-IS, WITHOUT WARRANTY OF ANY KIND, AND THE
35 Use the -i option to retrieve version information from the driver.
37 # ethtool -i eth0
39 version: COMM-USB8388-318.p4
40 firmware-version: 5.110.7
41 bus-info:
43 Use the -e option to read the EEPROM contents of the card.
46 ethtool -e ethX [raw on|off] [offset N] [length N]
48 -e retrieves and prints an EEPROM dump for the specified ethernet
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/
Dworkqueue.rst33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
83 called worker-pools.
85 The cmwq design differentiates between the user-facing workqueues that
87 which manages worker-pools and processes the queued work items.
89 There are two worker-pools, one for normal work items and the other
91 worker-pools to serve work items queued on unbound workqueues - the
102 When a work item is queued to a workqueue, the target worker-pool is
104 and appended on the shared worklist of the worker-pool. For example,
106 be queued on the worklist of either normal or highpri worker-pool that
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-usb10 This allows to avoid side-effects with drivers
28 drivers, non-authorized one are not. By default, wired
42 A devices's CDID, as 16 space-separated hex octets.
53 space-separated hex octets.
67 Contact: linux-usb@vger.kernel.org
82 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
87 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
101 What: /sys/bus/usb-serial/drivers/.../new_id
103 Contact: linux-usb@vger.kernel.org
106 extra bus folder "usb-serial" in sysfs; apart from that
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/
Dmultigen_lru.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Gen LRU
6 The multi-gen LRU is an alternative LRU implementation that optimizes
26 -----------
38 0x0001 The main switch for the multi-gen LRU.
42 disabled, the multi-gen LRU will suffer a minor performance
46 0x0004 Clearing the accessed bit in non-leaf page table entries as
49 disabled, the multi-gen LRU will suffer a negligible
57 echo y >/sys/kernel/mm/lru_gen/enabled
60 echo 5 >/sys/kernel/mm/lru_gen/enabled
[all …]
/kernel/linux/linux-6.6/drivers/net/can/usb/etas_es58x/
Des58x_core.c1 // SPDX-License-Identifier: GPL-2.0
3 /* Driver for ETAS GmbH ES58X USB CAN(-FD) Bus Interfaces.
10 * Copyright (c) 2020-2022 Vincent Mailhol <mailhol.vincent@wanadoo.fr>
39 /* ETAS GmbH ES581.4 USB dual-channel CAN Bus Interface module. */
43 /* ETAS GmbH ES582.1 USB dual-channel CAN FD Bus Interface module. */
48 /* ETAS GmbH ES584.1 USB single-channel CAN FD Bus Interface module. */
75 * es58x_calculate_crc() - Compute the crc16 of a given URB.
85 ssize_t len = urb_len - ES58X_CRC_CALC_OFFSET - sizeof(crc); in es58x_calculate_crc()
87 crc = crc16(0, &urb_cmd->raw_cmd[ES58X_CRC_CALC_OFFSET], len); in es58x_calculate_crc()
92 * es58x_get_crc() - Get the CRC value of a given URB.
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-usb10 This allows to avoid side-effects with drivers
28 drivers, non-authorized one are not. By default, wired
33 Contact: linux-usb@vger.kernel.org
48 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
53 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
67 What: /sys/bus/usb-serial/drivers/.../new_id
69 Contact: linux-usb@vger.kernel.org
72 extra bus folder "usb-serial" in sysfs; apart from that
87 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
97 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/pm/
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.]
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
57 ``intel_pstate`` can operate in two different modes, active or passive. In the
58 active mode, it uses its own internal performance scaling governor algorithm or
[all …]

12345