Searched +full:inactive +full:- (Results 1 – 25 of 107) sorted by relevance
12345
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/gpio-restart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
17 'open-source' is not found, the GPIO line will be driven in the inactive state. Otherwise its
22 This will also cause an inactive->active edge condition, triggering positive edge triggered
23 reset. After a delay specified by active-delay, the GPIO is set to inactive, thus causing an
24 active->inactive edge, triggering negative edge triggered reset. After a delay specified by
25 inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the
[all …]
|
| D | gpio-poweroff.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/gpio-poweroff.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
15 from inactive to active. After a delay (active-delay-ms) it
16 is expected to be switched back to inactive. After another
17 delay (inactive-delay-ms) it is configured as active again.
19 the system is still running after waiting some time (timeout-ms).
22 - $ref: restart-handler.yaml#
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-v2-line-set-values-ioctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_SET_VALUES_IOCTL - Set the values of requested output lines.
26 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
38 The values set are logical, indicating if the line is to be active or inactive.
40 values (active/inactive) and physical values (high/low).
41 If ``GPIO_V2_LINE_FLAG_ACTIVE_LOW`` is not set then active is high and inactive
43 inactive is high.
53 On error -1 and the ``errno`` variable is set appropriately.
54 Common error codes are described in error-codes.rst.
|
| D | gpio-handle-set-line-values-ioctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 gpio-v2-line-set-values-ioctl.rst.
15 GPIO_HANDLE_SET_LINE_VALUES_IOCTL - Set the values of all requested output lines.
29 :c:type:`request.fd<gpiohandle_request>` by gpio-get-linehandle-ioctl.rst.
39 The values set are logical, indicating if the line is to be active or inactive.
41 values (active/inactive) and physical values (high/low).
43 inactive is low. If ``GPIOHANDLE_REQUEST_ACTIVE_LOW`` is set then active is low
44 and inactive is high.
54 On error -1 and the ``errno`` variable is set appropriately.
55 Common error codes are described in error-codes.rst.
|
| D | gpio-v2-line-get-values-ioctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_GET_VALUES_IOCTL - Get the values of requested lines.
26 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
37 The values returned are logical, indicating if the line is active or inactive.
39 values (high/low) and logical values (active/inactive).
41 inactive. If ``GPIO_V2_LINE_FLAG_ACTIVE_LOW`` is set then low is active and
42 high is inactive.
57 On error -1 and the ``errno`` variable is set appropriately.
58 Common error codes are described in error-codes.rst.
|
| D | gpio-handle-get-line-values-ioctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 gpio-v2-line-get-values-ioctl.rst.
15 GPIOHANDLE_GET_LINE_VALUES_IOCTL - Get the values of all requested lines.
29 :c:type:`request.fd<gpiohandle_request>` by gpio-get-linehandle-ioctl.rst.
39 The values returned are logical, indicating if the line is active or inactive.
41 values (high/low) and logical values (active/inactive).
43 low is inactive. If ``GPIOHANDLE_REQUEST_ACTIVE_LOW`` is set then low is active
44 and high is inactive.
62 On error -1 and the ``errno`` variable is set appropriately.
63 Common error codes are described in error-codes.rst.
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-matrix-keypad.txt | 6 keypad can sense a key-press and key-release by means of GPIO lines and
10 - compatible: Should be "gpio-matrix-keypad"
11 - row-gpios: List of gpios used as row lines. The gpio specifier
14 - col-gpios: List of gpios used as column lines. The gpio specifier
17 - linux,keymap: The definition can be found at
18 bindings/input/matrix-keymap.txt
21 - linux,no-autorepeat: do no enable autorepeat feature.
22 - wakeup-source: use any event on keypad as wakeup event.
24 - debounce-delay-ms: debounce interval in milliseconds
25 - col-scan-delay-us: delay, measured in microseconds, that is needed
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | davinci-mcasp-audio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/davinci-mcasp-audio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jayesh Choudhary <j-choudhary@ti.com>
15 - ti,dm646x-mcasp-audio
16 - ti,da830-mcasp-audio
17 - ti,am33xx-mcasp-audio
18 - ti,dra7-mcasp-audio
19 - ti,omap4-mcasp-audio
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
32 ``inactive`` (idle). If they are active, they have to be in power states
34 are inactive, ideally, they should be in low-power states in which they may not
39 draw (or maximum energy usage) of it. If all of them are inactive, the system
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | idt,versaclock5.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
16 - 5P49V5923:
17 0 -- OUT0_SEL_I2CB
18 1 -- OUT1
19 2 -- OUT2
21 - 5P49V5933:
22 0 -- OUT0_SEL_I2CB
23 1 -- OUT1
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-rfkill | 1 rfkill - radio frequency (RF) connector kill switch support
3 For details to this subsystem look at Documentation/driver-api/rfkill.rst.
6 Documentation/ABI/removed/sysfs-class-rfkill.
9 Date: 09-Jul-2007
11 Contact: linux-wireless@vger.kernel.org,
17 What: /sys/class/rfkill/rfkill[0-9]+/name
18 Date: 09-Jul-2007
20 Contact: linux-wireless@vger.kernel.org
25 What: /sys/class/rfkill/rfkill[0-9]+/type
26 Date: 09-Jul-2007
[all …]
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 12 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 …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | writecache.rst | 14 1. type of the cache device - "p" or "s"
15 - p - persistent memory
16 - s - SSD
25 offset from the start of cache device in 512-byte sectors
45 applicable only to persistent memory - use the FUA flag
49 applicable only to persistent memory - don't use the FUA
53 - some underlying devices perform better with fua, some
64 dm-writecache target and replace it with dm-linear or
79 1. error indicator - 0 if there was no error, otherwise error number
104 2. load an inactive table with a linear target that maps
[all …]
|
| D | dm-ima.rst | 2 dm-ima
6 (including the attestation service) interact with it - both during the
7 setup and during rest of the system run-time. They share sensitive data
9 may want to verify the current run-time state of the relevant kernel
10 subsystems before fully trusting the system with business-critical
18 impact the security profile of the block device, and in-turn, of the
24 fully trusting the system with business-critical data/workload.
28 various block devices -
30 - by device mapper itself, from within the kernel,
31 - in a tamper resistant way,
[all …]
|
| /Documentation/maintainer/ |
| D | feature-and-driver-maintainers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
36 may range from two working days for fast-paced subsystems (e.g. networking)
40 --------------------------
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
46 `lei <https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started>`_.
52 -------
56 multiple drivers - whether to provide a review is left to the maintainer.
58 When there are multiple maintainers for a piece of code an ``Acked-by``
59 or ``Reviewed-by`` tag (or review comments) from a single maintainer is
68 ----------------------------
[all …]
|
| /Documentation/filesystems/ |
| D | qnx6.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 ------
39 ---------------
51 inactive superblock.
65 Unused block pointers are always set to ~0 - regardless of root node,
79 0x1000 is the size reserved for each superblock - regardless of the
83 ------
104 -----------
125 -------------
141 --------------
[all …]
|
| /Documentation/devicetree/bindings/iio/imu/ |
| D | adi,adis16460.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dragos Bogdan <dragos.bogdan@analog.com>
14 https://www.analog.com/media/en/technical-documentation/data-sheets/ADIS16460.pdf
19 - adi,adis16460
24 spi-cpha: true
26 spi-cpol: true
28 spi-cs-inactive-delay-ns:
36 - compatible
[all …]
|
| /Documentation/driver-api/ |
| D | pwm.rst | 15 ----------------
24 PWM_LOOKUP("tegra-pwm", 0, "pwm-backlight", NULL,
36 ----------
59 easily possible, drivers are supposed to emit the inactive state, but some
60 drivers cannot. If you rely on getting the inactive state, use .duty_cycle=0,
82 PWM arguments are usually platform-specific and allows the PWM user to only
93 -----------------------------------
102 The number of PWM channels this chip supports (read-only).
105 Exports a PWM channel for use with sysfs (write-only).
108 Unexports a PWM channel from sysfs (write-only).
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-wacom | 4 Contact: linux-bluetooth@vger.kernel.org
14 Contact: linux-input@vger.kernel.org
25 Contact: linux-input@vger.kernel.org
35 Contact: linux-input@vger.kernel.org
44 Contact: linux-input@vger.kernel.org
50 same side are always inactive.
54 Contact: linux-input@vger.kernel.org
59 the left are always inactive.
63 Contact: linux-input@vger.kernel.org
70 Contact: linux-input@vger.kernel.org
[all …]
|
| D | sysfs-class-power-ltc4162l | 1 What: /sys/class/power_supply/ltc4162-l/charge_status
18 What: /sys/class/power_supply/ltc4162-l/ibat
29 What: /sys/class/power_supply/ltc4162-l/vbat
39 What: /sys/class/power_supply/ltc4162-l/vbat_avg
49 What: /sys/class/power_supply/ltc4162-l/force_telemetry
65 What: /sys/class/power_supply/ltc4162-l/arm_ship_mode
69 The charger will normally drain the battery while inactive,
74 until some external power-supply is attached raising the input
|
| /Documentation/virt/kvm/devices/ |
| D | mpic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - KVM_DEV_TYPE_FSL_MPIC_20 Freescale MPIC v2.0
10 - KVM_DEV_TYPE_FSL_MPIC_42 Freescale MPIC v4.2
20 KVM_DEV_MPIC_BASE_ADDR (rw, 64-bit)
25 KVM_DEV_MPIC_GRP_REGISTER (rw, 32-bit)
28 must be 4-byte aligned.
33 KVM_DEV_MPIC_GRP_IRQ_ACTIVE (rw, 32-bit)
34 IRQ input line for each standard openpic source. 0 is inactive and 1
37 For edge-triggered interrupts: Writing 1 is considered an activating
53 The numbering is the same as the MPIC device tree binding -- based on
[all …]
|
| /Documentation/bpf/ |
| D | map_lru_hash_update.dot | 1 // SPDX-License-Identifier: GPL-2.0-only
2 // Copyright (C) 2022-2023 Isovalent, Inc.
39 from global -> local"]
47 label="Shrink inactive list
50 (global LRU -> local)"]
55 inactive, or if empty,
70 label="Steal a node from\nper-cpu freelist?"]
89 fn_htab_lru_map_update_elem_ENOMEM [shape=oval,label="return -ENOMEM"]
95 fn_htab_lru_map_update_elem_EBUSY [shape=oval,label="return -EBUSY"]
96 fn_htab_lru_map_update_elem_EEXIST [shape=oval,label="return -EEXIST"]
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 10 Drivers that use firmware from linux-firmware should follow the rules in
18 the firmware files in linux-firmware be named with some device
21 firmware file name, in order to let the driver detact any non-ABI
22 fixes/changes. The firmware files in linux-firmware should be
27 * If the kernel support for the hardware is normally inactive, or the
33 non-optionally.
36 be successful, then all supported major versions in the linux-firmware
|
| /Documentation/admin-guide/mm/damon/ |
| D | reclaim.rst | 1 .. 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 …]
|
| /Documentation/devicetree/bindings/mux/ |
| D | gpio-mux.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mux/gpio-mux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based multiplexer controller
10 - Peter Rosin <peda@axentia.se>
18 bit. An active pin is a binary 1, an inactive pin is a binary 0.
22 const: gpio-mux
24 mux-gpios:
28 '#mux-control-cells':
[all …]
|
12345