Searched +full:hardware +full:- +full:driven (Results 1 – 25 of 504) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-6.6/drivers/gpio/ |
| D | gpio-stp-xway.c | 1 // SPDX-License-Identifier: GPL-2.0-only
22 * 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
37 /* software or hardware update select bit */
58 /* 2 groups of 3 bits can be driven by the phys */
85 u8 groups; /* we can drive 1-3 groups of 8bit each */
86 u8 dsl; /* the 2 LSBs can be driven by the dsl core */
87 u8 phy1; /* 3 bits can be driven by phy1 */
88 u8 phy2; /* 3 bits can be driven by phy2 */
89 u8 phy3; /* 3 bits can be driven by phy3 */
90 u8 phy4; /* 3 bits can be driven by phy4 */
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | gpio-stp-xway.c | 1 // SPDX-License-Identifier: GPL-2.0-only
21 * 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
36 /* software or hardware update select bit */
57 /* 2 groups of 3 bits can be driven by the phys */
84 u8 groups; /* we can drive 1-3 groups of 8bit each */
85 u8 dsl; /* the 2 LSBs can be driven by the dsl core */
86 u8 phy1; /* 3 bits can be driven by phy1 */
87 u8 phy2; /* 3 bits can be driven by phy2 */
88 u8 phy3; /* 3 bits can be driven by phy3 */
89 u8 phy4; /* 3 bits can be driven by phy4 */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-ports.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
15 controller, named "Ports" in the hardware reference manual.
16 Pin multiplexing and GPIO configuration is performed on a per-pin basis
17 writing configuration values to per-port register sets.
25 - const: renesas,r7s72100-ports # RZ/A1H
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-ports.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
15 controller, named "Ports" in the hardware reference manual.
16 Pin multiplexing and GPIO configuration is performed on a per-pin basis
17 writing configuration values to per-port register sets.
25 - const: renesas,r7s72100-ports # RZ/A1H
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
17 and is described by all the files in this directory excepted gpio-legacy.txt.
18 - The legacy integer-based interface which is considered deprecated (but still
19 usable for compatibility reasons) is documented in gpio-legacy.txt.
21 The remainder of this document applies to the new descriptor-based interface.
22 gpio-legacy.txt contains the same information applied to the legacy
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
31 to Linux developers working with embedded and custom hardware. Each GPIO
33 (BGA) packages. Board schematics show which external hardware connects to
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
18 - The legacy integer-based interface which is considered deprecated (but still
21 The remainder of this document applies to the new descriptor-based interface.
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
31 to Linux developers working with embedded and custom hardware. Each GPIO
33 (BGA) packages. Board schematics show which external hardware connects to
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
38 non-dedicated pin can be configured as a GPIO; and most chips have at least
43 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | parport.rst | 4 The ``parport`` code provides parallel-port support under Linux. This
9 detection of your hardware. This is particularly useful if you want
16 port-sharing) and architecture-dependent (which deals with actually
28 architecture-dependent code with (for example)::
32 to tell the ``parport`` code that you want three PC-style ports, one at
34 auto-detected IRQ. Currently, PC-style (``parport_pc``), Sun ``bpp``,
35 Amiga, Atari, and MFC3 hardware is supported.
43 --------
60 ------------------------
68 parport0: Printer, BJC-210 (Canon)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | parport.rst | 4 The ``parport`` code provides parallel-port support under Linux. This
9 detection of your hardware. This is particularly useful if you want
16 port-sharing) and architecture-dependent (which deals with actually
28 architecture-dependent code with (for example)::
32 to tell the ``parport`` code that you want three PC-style ports, one at
34 auto-detected IRQ. Currently, PC-style (``parport_pc``), Sun ``bpp``,
35 Amiga, Atari, and MFC3 hardware is supported.
43 --------
60 ------------------------
68 parport0: Printer, BJC-210 (Canon)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | leds-class.rst | 8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
48 - devicename:
51 than to the hardware; the information related to the product and the bus
57 - color:
59 include/dt-bindings/leds/common.h.
61 - function:
63 include/dt-bindings/leds/common.h.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | st,stm32-timers.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/st,stm32-timers.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This hardware block provides 3 types of timer along with PWM functionality:
11 - advanced-control timers consist of a 16-bit auto-reload counter driven
14 - general-purpose timers consist of a 16-bit or 32-bit auto-reload counter
15 driven by a programmable prescaler and PWM outputs.
16 - basic timers consist of a 16-bit auto-reload counter driven by a
20 - Benjamin Gaignard <benjamin.gaignard@st.com>
[all …]
|
| /kernel/linux/linux-6.6/drivers/leds/rgb/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 tristate "LEDs group multi-color support"
11 different colors are physically grouped in a single multi-color LED
12 and driven by a controller that doesn't have multi-color support.
15 will be called leds-group-multicolor.
18 tristate "PWM driven multi-color LED Support"
21 This option enables support for PWM driven monochrome LEDs that are
25 will be called leds-pwm-multicolor.
39 If compiled as a module, the module will be named leds-qcom-lpg.
47 In MT6370, there are four channel current-sink LED drivers that
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | st,stm32-timers.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/st,stm32-timers.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This hardware block provides 3 types of timer along with PWM functionality:
11 - advanced-control timers consist of a 16-bit auto-reload counter driven
14 - general-purpose timers consist of a 16-bit or 32-bit auto-reload counter
15 driven by a programmable prescaler and PWM outputs.
16 - basic timers consist of a 16-bit auto-reload counter driven by a
20 - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 12 -----------
17 Currently, due to the absence of in-kernel API to access HWMON drivers, Nouveau
24 ----------------------
26 Temperature is exposed under as a read-only HWMON attribute temp1_input.
56 --------------
75 Your fan can be driven in different modes:
78 * 1: The fan can be driven in manual (use pwm1 to change the speed);
79 * 2; The fan is driven automatically depending on the temperature.
85 When operating in manual mode outside the vbios-defined
87 depending on your hardware.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 12 -----------
17 Currently, due to the absence of in-kernel API to access HWMON drivers, Nouveau
24 ----------------------
26 Temperature is exposed under as a read-only HWMON attribute temp1_input.
56 --------------
75 Your fan can be driven in different modes:
78 * 1: The fan can be driven in manual (use pwm1 to change the speed);
79 * 2; The fan is driven automatically depending on the temperature.
85 When operating in manual mode outside the vbios-defined
87 depending on your hardware.
[all …]
|
| /kernel/linux/linux-6.6/drivers/char/ipmi/ |
| D | ipmi_si_sm.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
5 * State machine interface for low-level IPMI system management
8 * BT interface) and the actual low-level state machine.
35 SI_SM_HOSED, /* The hardware violated the state machine. */
38 * The hardware is asserting attn and the state machine is
61 * return -2 if the state machine is not idle, -1 if the size
70 * -1 if the buffer is too small, zero if no transaction is
78 * receiving an interrupt (for a interrupt-driven interface).
79 * If interrupt driven, you should probably poll this
|
| /kernel/linux/linux-5.10/drivers/char/ipmi/ |
| D | ipmi_si_sm.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
5 * State machine interface for low-level IPMI system management
8 * BT interface) and the actual low-level state machine.
35 SI_SM_HOSED, /* The hardware violated the state machine. */
38 * The hardware is asserting attn and the state machine is
61 * return -2 if the state machine is not idle, -1 if the size
70 * -1 if the buffer is too small, zero if no transaction is
78 * receiving an interrupt (for a interrupt-driven interface).
79 * If interrupt driven, you should probably poll this
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | Kconfig | 16 EDAC is a subsystem along with hardware-specific drivers designed to
17 report hardware errors. These are low-level errors that are reported
22 The mailing list for the EDAC project is linux-edac@vger.kernel.org.
40 levels are 0-4 (from low to high) and by default it is set to 2.
44 tristate "Decode MCEs in human-readable form (only on AMD for now)"
49 occurring on your machine in human-readable form.
59 Not all machines support hardware-driven error report. Some of those
60 provide a BIOS-driven error report mechanism via ACPI, using the
64 When this option is enabled, it will disable the hardware-driven
68 It should be noticed that keeping both GHES and a hardware-driven
[all …]
|
| /kernel/linux/linux-6.6/drivers/edac/ |
| D | Kconfig | 16 EDAC is a subsystem along with hardware-specific drivers designed to
17 report hardware errors. These are low-level errors that are reported
22 The mailing list for the EDAC project is linux-edac@vger.kernel.org.
40 levels are 0-4 (from low to high) and by default it is set to 2.
44 tristate "Decode MCEs in human-readable form (only on AMD for now)"
49 occurring on your machine in human-readable form.
60 Not all machines support hardware-driven error report. Some of those
61 provide a BIOS-driven error report mechanism via ACPI, using the
65 When this option is enabled, it will disable the hardware-driven
69 It should be noticed that keeping both GHES and a hardware-driven
[all …]
|
| /kernel/linux/linux-6.6/Documentation/spi/ |
| D | spi-lm70llp.rst | 2 spi_lm70llp : LM70-LLP parport-to-SPI adapter
15 -----------
22 into a SPI bus with a single device, which will be driven by the generic
26 Hardware Interfacing
27 --------------------
28 The schematic for this particular board (the LM70EVAL-LLP) is
33 The hardware interfacing on the LM70 LLP eval board is as follows:
39 D0 2 - -
40 D1 3 --> V+ 5
41 D2 4 --> V+ 5
[all …]
|
| /kernel/linux/linux-5.10/Documentation/spi/ |
| D | spi-lm70llp.rst | 2 spi_lm70llp : LM70-LLP parport-to-SPI adapter
15 -----------
22 into a SPI bus with a single device, which will be driven by the generic
26 Hardware Interfacing
27 --------------------
28 The schematic for this particular board (the LM70EVAL-LLP) is
33 The hardware interfacing on the LM70 LLP eval board is as follows:
39 D0 2 - -
40 D1 3 --> V+ 5
41 D2 4 --> V+ 5
[all …]
|
| /kernel/linux/linux-6.6/drivers/leds/blink/ |
| D | Kconfig | 10 BCM63138 SoC. The same hardware block is known to be also used
13 If compiled as module it will be called leds-bcm63138.
22 gateway-on-a-chip SoC to be shipped on mid and high end home
25 These LEDs are driven by a Serial Shift Output (SSO) controller.
26 The driver supports hardware blinking and the LEDs can be configured
27 to be triggered by software/CPU or by hardware.
31 will be called leds-lgm-sso.
|
| /kernel/linux/linux-6.6/arch/powerpc/platforms/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
37 bool "ePAPR para-virtualization support"
39 Enables ePAPR para-virtualization support for guests.
47 Support for running natively on the hardware, i.e. without
48 a hypervisor. This option is not user-selectable but should
65 bool "Device-tree based CPU feature discovery & setup"
97 The MPIC global timer is a hardware timer inside the
99 specified interval times out, the hardware timer generates
124 registers are used for inter-processor communication.
206 bool "On-chip CPU temperature sensor support"
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
35 bool "ePAPR para-virtualization support"
37 Enables ePAPR para-virtualization support for guests.
45 Support for running natively on the hardware, i.e. without
46 a hypervisor. This option is not user-selectable but should
62 bool "Device-tree based CPU feature discovery & setup"
94 The MPIC global timer is a hardware timer inside the
96 specified interval times out, the hardware timer generates
121 registers are used for inter-processor communication.
203 bool "On-chip CPU temperature sensor support"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
13 This binding is intended to represent the location of hardware
23 "#address-cells":
26 "#size-cells":
29 read-only:
34 wp-gpios:
36 GPIO to which the write-protect pin of the chip is connected.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
13 This binding is intended to represent the location of hardware
24 pattern: "^(eeprom|efuse|nvram)(@.*|-[0-9a-f])*$"
26 "#address-cells":
29 "#size-cells":
32 read-only:
37 wp-gpios:
[all …]
|
12345678910>>...21