| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-backlight-adp5520 | 2 ---------------------------------------------------------------
4 The backlight brightness control operates at three different levels for the
5 adp5520 and adp5501 devices: daylight (level 1), office (level 2) and dark
6 (level 3). By default the brightness operates at the daylight brightness level.
16 is at one of the three levels (daylight, office or dark). This
18 value between 0 mA and 30 mA using linear or non-linear
29 one of the three levels (daylight, office or dark). This is an
31 between 0 mA and 30 mA using linear or non-linear algorithms.
|
| D | sysfs-class-backlight-adp8860 | 2 -----------------------------------------------------------
4 The backlight brightness control operates at three different levels for the
5 adp8860, adp8861 and adp8863 devices: daylight (level 1), office (level 2) and
6 dark (level 3). By default the brightness operates at the daylight brightness
7 level.
21 is at one of the three levels (daylight, office or dark). This
23 value between 0 mA and 30 mA using linear or non-linear
35 one of the three levels (daylight, office or dark). This is an
37 between 0 mA and 30 mA using linear or non-linear algorithms.
|
| 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
30 button is pressed on the stylus. This luminance level is
31 normally lower than the level when a button is pressed.
35 Contact: linux-input@vger.kernel.org
44 Contact: linux-input@vger.kernel.org
49 24HD) status LEDs is active (0..3). The other three LEDs on the
54 Contact: linux-input@vger.kernel.org
58 and Cintiq 24HD) status LEDs is active (0..3). The other three LEDs on
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | realtek,usb2phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Stanley Chang <stanley_chang@realtek.com>
20 The USB architecture includes three XHCI controllers.
23 XHCI controller#0 -- usb2phy -- phy#0
24 |- usb3phy -- phy#0
25 XHCI controller#1 -- usb2phy -- phy#0
26 XHCI controller#2 -- usb2phy -- phy#0
27 |- usb3phy -- phy#0
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/um/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
14 bool "64-bit kernel" if "$(SUBARCH)" = "x86"
31 bool "Three-level pagetables" if !64BIT
34 Three-level pagetables will let UML have more than 4G of physical
38 However, this it experimental on 32-bit architectures, so if unsure say
39 N (on x86-64 it's automatically enabled, instead, as it's safe there).
|
| /kernel/linux/linux-6.6/arch/x86/um/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
15 bool "64-bit kernel" if "$(SUBARCH)" = "x86"
32 bool "Three-level pagetables" if !64BIT
35 Three-level pagetables will let UML have more than 4G of physical
39 However, this it experimental on 32-bit architectures, so if unsure say
40 N (on x86-64 it's automatically enabled, instead, as it's safe there).
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | img,pdc-intc.txt | 10 - compatible: Specifies the compatibility list for the interrupt controller.
11 The type shall be <string> and the value shall include "img,pdc-intc".
13 - reg: Specifies the base PDC physical address(s) and size(s) of the
14 addressable register space. The type shall be <prop-encoded-array>.
16 - interrupt-controller: The presence of this property identifies the node
19 - #interrupt-cells: Specifies the number of cells needed to encode an
22 - num-perips: Number of waking peripherals.
24 - num-syswakes: Number of SysWake inputs.
26 - interrupts: List of interrupt specifiers. The first specifier shall be the
34 - <1st-cell>: The interrupt-number that identifies the interrupt source.
[all …]
|
| D | riscv,cpu-intc.txt | 1 RISC-V Hart-Level Interrupt Controller (HLIC)
2 ---------------------------------------------
4 RISC-V cores include Control Status Registers (CSRs) which are local to each
5 CPU core (HART in RISC-V terminology) and can be read or written by software.
10 The RISC-V supervisor ISA manual specifies three interrupt sources that are
13 timer interrupt comes from an architecturally mandated real-time timer that is
16 via the platform-level interrupt controller (PLIC).
18 All RISC-V systems that conform to the supervisor ISA specification are
19 required to have a HLIC with these three interrupt sources present. Since the
27 - compatible : "riscv,cpu-intc"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/ |
| D | img,pdc-intc.txt | 10 - compatible: Specifies the compatibility list for the interrupt controller.
11 The type shall be <string> and the value shall include "img,pdc-intc".
13 - reg: Specifies the base PDC physical address(s) and size(s) of the
14 addressable register space. The type shall be <prop-encoded-array>.
16 - interrupt-controller: The presence of this property identifies the node
19 - #interrupt-cells: Specifies the number of cells needed to encode an
22 - num-perips: Number of waking peripherals.
24 - num-syswakes: Number of SysWake inputs.
26 - interrupts: List of interrupt specifiers. The first specifier shall be the
34 - <1st-cell>: The interrupt-number that identifies the interrupt source.
[all …]
|
| D | riscv,cpu-intc.txt | 1 RISC-V Hart-Level Interrupt Controller (HLIC)
2 ---------------------------------------------
4 RISC-V cores include Control Status Registers (CSRs) which are local to each
5 CPU core (HART in RISC-V terminology) and can be read or written by software.
10 The RISC-V supervisor ISA manual specifies three interrupt sources that are
13 timer interrupt comes from an architecturally mandated real-time timer that is
16 via the platform-level interrupt controller (PLIC).
18 All RISC-V systems that conform to the supervisor ISA specification are
19 required to have a HLIC with these three interrupt sources present. Since the
27 - compatible : "riscv,cpu-intc"
[all …]
|
| /kernel/linux/linux-6.6/arch/sh/boards/mach-dreamcast/ |
| D | irq.c | 1 // SPDX-License-Identifier: GPL-2.0
18 * Dreamcast System ASIC Hardware Events -
28 * There are three 32-bit ESRs located at 0xa05f6900 - 0xa05f6908. Event
29 * types can be found in arch/sh/include/mach-dreamcast/mach/sysasic.h.
30 * There are three groups of EMRs that parallel the ESRs. Each EMR group
31 * corresponds to an IRQ, so 0xa05f6910 - 0xa05f6918 triggers IRQ 13,
32 * 0xa05f6920 - 0xa05f6928 triggers IRQ 11, and 0xa05f6930 - 0xa05f6938
39 * 6900/6910 - Events 0-31, IRQ 13
40 * 6904/6924 - Events 32-63, IRQ 11
41 * 6908/6938 - Events 64-95, IRQ 9
[all …]
|
| /kernel/linux/linux-5.10/arch/sh/boards/mach-dreamcast/ |
| D | irq.c | 1 // SPDX-License-Identifier: GPL-2.0
18 * Dreamcast System ASIC Hardware Events -
28 * There are three 32-bit ESRs located at 0xa05f6900 - 0xa05f6908. Event
29 * types can be found in arch/sh/include/mach-dreamcast/mach/sysasic.h.
30 * There are three groups of EMRs that parallel the ESRs. Each EMR group
31 * corresponds to an IRQ, so 0xa05f6910 - 0xa05f6918 triggers IRQ 13,
32 * 0xa05f6920 - 0xa05f6928 triggers IRQ 11, and 0xa05f6930 - 0xa05f6938
39 * 6900/6910 - Events 0-31, IRQ 13
40 * 6904/6924 - Events 32-63, IRQ 11
41 * 6908/6938 - Events 64-95, IRQ 9
[all …]
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-stats.rst | 11 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
12 release). Some counters make more sense to be per-runqueue; other to be
13 per-domain. Note that domains (and their associated information) will only
16 In version 14 of schedstat, there is at least one level of domain
22 are no architectures which need more than three domain levels. The first
33 Note that any such script will necessarily be version-specific, as the main
38 --------------
45 Next three are schedule() statistics:
57 Next three are statistics describing scheduling latency:
66 -----------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-stats.rst | 11 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
12 release). Some counters make more sense to be per-runqueue; other to be
13 per-domain. Note that domains (and their associated information) will only
16 In version 14 of schedstat, there is at least one level of domain
22 are no architectures which need more than three domain levels. The first
33 Note that any such script will necessarily be version-specific, as the main
38 --------------
45 Next three are schedule() statistics:
57 Next three are statistics describing scheduling latency:
66 -----------------
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/include/ivsrcid/dcn/ |
| D | irqsrcs_dcn_1_0.h | 30 …C_I2C_SW_DONE 1 // DC_I2C SW done DC_I2C_SW_DONE_INTERRUPT DISP_INTERRUPT_STATUS Level
33 … // DC_I2C DDC1 HW done DOUT_IHC_I2C_DDC1_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
36 … // DC_I2C DDC2 HW done DOUT_IHC_I2C_DDC2_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
39 … // DC_I2C DDC3 HW done DOUT_IHC_I2C_DDC3_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
42 … // DC_I2C_DDC4 HW done DOUT_IHC_I2C_DDC4_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
45 … // DC_I2C_DDC5 HW done DOUT_IHC_I2C_DDC5_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
48 … // DC_I2C_DDC6 HW done DOUT_IHC_I2C_DDC6_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
51 …DC_I2C_DDCVGA HW done DOUT_IHC_I2C_DDCVGA_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
54 …DC1 read request DC_I2C_DDC1_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse
57 …DC2 read request DC_I2C_DDC2_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/include/ivsrcid/dcn/ |
| D | irqsrcs_dcn_1_0.h | 30 …C_I2C_SW_DONE 1 // DC_I2C SW done DC_I2C_SW_DONE_INTERRUPT DISP_INTERRUPT_STATUS Level
33 … // DC_I2C DDC1 HW done DOUT_IHC_I2C_DDC1_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
36 … // DC_I2C DDC2 HW done DOUT_IHC_I2C_DDC2_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
39 … // DC_I2C DDC3 HW done DOUT_IHC_I2C_DDC3_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
42 … // DC_I2C_DDC4 HW done DOUT_IHC_I2C_DDC4_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
45 … // DC_I2C_DDC5 HW done DOUT_IHC_I2C_DDC5_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
48 … // DC_I2C_DDC6 HW done DOUT_IHC_I2C_DDC6_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
51 …DC_I2C_DDCVGA HW done DOUT_IHC_I2C_DDCVGA_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level
54 …DC1 read request DC_I2C_DDC1_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse
57 …DC2 read request DC_I2C_DDC2_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | gpio-wdt.txt | 1 * GPIO-controlled Watchdog
4 - compatible: Should contain "linux,wdt-gpio".
5 - gpios: From common gpio binding; gpio connection to WDT reset pin.
6 - hw_algo: The algorithm used by the driver. Should be one of the
8 - toggle: Either a high-to-low or a low-to-high transition clears
10 left floating or connected to a three-state buffer.
11 - level: Low or high level starts counting WDT timeout,
12 the opposite level disables the WDT. Active level is determined
14 - hw_margin_ms: Maximum time to reset watchdog circuit (milliseconds).
17 - always-running: If the watchdog timer cannot be disabled, add this flag to
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/ |
| D | paravirt_ops.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 including native machine -- without any hypervisors.
16 corresponding to low-level critical instructions and high-level
18 time by enabling binary patching of the low-level critical operations
21 pv_ops operations are classified into three categories:
23 - simple indirect call
24 These operations correspond to high-level functionality where it is
27 - indirect call which allows optimization with binary patch
28 Usually these operations correspond to low-level critical instructions. They
32 - a set of macros for hand written assembly code
|
| /kernel/linux/linux-5.10/Documentation/virt/ |
| D | paravirt_ops.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 including native machine -- without any hypervisors.
16 corresponding to low level critical instructions and high level
17 functionalities in various areas. pv-ops allows for optimizations at run
18 time by enabling binary patching of the low-ops critical operations
21 pv_ops operations are classified into three categories:
23 - simple indirect call
24 These operations correspond to high level functionality where it is
27 - indirect call which allows optimization with binary patch
28 Usually these operations correspond to low level critical instructions. They
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/opp/ |
| D | opp.txt | 2 ----------------------------------------------------
4 Devices work at voltage-current-frequency combinations and some implementations
13 Binding 1: operating-points
16 This binding only supports voltage-frequency pairs.
19 - operating-points: An array of 2-tuples items, and each item consists
20 of frequency and voltage like <freq-kHz vol-uV>.
27 compatible = "arm,cortex-a9";
29 next-level-cache = <&L2>;
30 operating-points = <
39 Binding 2: operating-points-v2
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/regulator/ |
| D | overview.rst | 26 - Regulator
27 - Electronic device that supplies power to other devices.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
35 - Power Management IC. An IC that contains numerous
39 - Consumer
40 - Electronic device that is supplied power by a regulator.
41 Consumers can be classified into two types:-
52 - Power Domain
53 - Electronic circuit that is supplied its input power by the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| D | overview.rst | 26 - Regulator
27 - Electronic device that supplies power to other devices.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
35 - Power Management IC. An IC that contains numerous
39 - Consumer
40 - Electronic device that is supplied power by a regulator.
41 Consumers can be classified into two types:-
52 - Power Domain
53 - Electronic circuit that is supplied its input power by the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/ |
| D | linux,wdt-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/watchdog/linux,wdt-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-controlled Watchdog
10 - Guenter Roeck <linux@roeck-us.net>
11 - Robert Marko <robert.marko@sartura.hr>
15 const: linux,wdt-gpio
24 - description:
25 Either a high-to-low or a low-to-high transition clears the WDT counter.
[all …]
|
| /kernel/linux/linux-6.6/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
30 button is pressed on the stylus. This luminance level is
31 normally lower than the level when a button is pressed.
35 Contact: linux-input@vger.kernel.org
44 Contact: linux-input@vger.kernel.org
49 24HD) status LEDs is active (0..3). The other three LEDs on the
54 Contact: linux-input@vger.kernel.org
58 and Cintiq 24HD) status LEDs is active (0..3). The other three LEDs on
[all …]
|