Home
last modified time | relevance | path

Searched refs:hardware (Results 1 – 25 of 1425) sorted by relevance

12345678910>>...57

/Linux-v4.19/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
8 by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 should be controlled by a hardware signal instead of the MODE register value,
15 with 0 meaning hardware control enabled and 1 hardware control disabled. This
16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
20 but you can't turn it off if the hardware decides to light it up. For this
21 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
/Linux-v4.19/drivers/media/rc/
Dserial_ir.c74 static struct serial_ir_hw hardware[] = { variable
76 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_HOMEBREW].lock),
90 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO].lock),
101 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO_REMOTE].lock),
112 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_ANIMAX].lock),
120 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IGOR].lock),
171 soutp(UART_MCR, hardware[type].off); in on()
173 soutp(UART_MCR, hardware[type].on); in on()
179 soutp(UART_MCR, hardware[type].on); in off()
181 soutp(UART_MCR, hardware[type].off); in off()
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/spi/
Dspi-sprd-adi.txt5 framework for its hardware implementation is alike to SPI bus and its timing
9 48 hardware channels to access analog chip. For 2 software read/write channels,
10 users should set ADI registers to access analog chip. For hardware channels,
11 we can configure them to allow other hardware components to use it independently,
12 which means we can just link one analog chip address to one hardware channel,
13 then users can access the mapped analog chip address by this hardware channel
14 triggered by hardware components instead of ADI software channels.
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
17 channels, the first value specifies the hardware channel id which is used to
18 transfer data triggered by hardware automatically, and the second value specifies
[all …]
/Linux-v4.19/arch/mips/boot/dts/brcm/
Dbcm63268-comtrend-vr-3032u.dts29 brcm,hardware-controlled;
35 brcm,hardware-controlled;
66 brcm,hardware-controlled;
71 brcm,hardware-controlled;
76 brcm,hardware-controlled;
81 brcm,hardware-controlled;
86 brcm,hardware-controlled;
91 brcm,hardware-controlled;
96 brcm,hardware-controlled;
/Linux-v4.19/sound/isa/sb/
Dsb_common.c132 switch (chip->hardware) { in snd_sbdsp_probe()
136 chip->hardware = SB_HW_10; in snd_sbdsp_probe()
141 chip->hardware = SB_HW_201; in snd_sbdsp_probe()
144 chip->hardware = SB_HW_20; in snd_sbdsp_probe()
149 chip->hardware = SB_HW_PRO; in snd_sbdsp_probe()
153 chip->hardware = SB_HW_16; in snd_sbdsp_probe()
216 unsigned short hardware, in snd_sbdsp_create() argument
241 (hardware == SB_HW_ALS4000 || in snd_sbdsp_create()
242 hardware == SB_HW_CS5530) ? in snd_sbdsp_create()
251 if (hardware == SB_HW_ALS4000) in snd_sbdsp_create()
[all …]
Dsb8_midi.c70 valid_open_flags = chip->hardware >= SB_HW_20 in snd_sb8dsp_midi_input_open()
82 if (chip->hardware >= SB_HW_20) in snd_sb8dsp_midi_input_open()
97 valid_open_flags = chip->hardware >= SB_HW_20 in snd_sb8dsp_midi_output_open()
109 if (chip->hardware >= SB_HW_20) in snd_sb8dsp_midi_output_open()
163 if (chip->hardware < SB_HW_20) in snd_sb8dsp_midi_input_trigger()
169 if (chip->hardware < SB_HW_20) in snd_sb8dsp_midi_input_trigger()
194 if (chip->hardware >= SB_HW_20) { in snd_sb8dsp_midi_output_write()
273 if (chip->hardware >= SB_HW_20) in snd_sb8dsp_midi()
/Linux-v4.19/sound/isa/wss/
Dwss_lib.c423 if ((timeout & CS4231_MCE) == 0 || !(chip->hardware & hw_mask)) in snd_wss_mce_down()
603 if (!(chip->hardware & WSS_HW_AD1848_MASK)) { in snd_wss_calibrate_mute()
611 if (chip->hardware == WSS_HW_INTERWAVE) { in snd_wss_calibrate_mute()
633 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_playback_format()
634 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_playback_format()
648 } else if (chip->hardware == WSS_HW_AD1845) { in snd_wss_playback_format()
670 if (chip->hardware != WSS_HW_INTERWAVE && !chip->single_dma) { in snd_wss_playback_format()
679 if (chip->hardware == WSS_HW_OPL3SA2) in snd_wss_playback_format()
694 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_capture_format()
695 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_capture_format()
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/crypto/
Dbrcm,spu-crypto.txt1 The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
2 cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
/Linux-v4.19/drivers/isdn/hardware/
DKconfig2 # ISDN hardware drivers
4 comment "CAPI hardware drivers"
6 source "drivers/isdn/hardware/avm/Kconfig"
8 source "drivers/isdn/hardware/eicon/Kconfig"
/Linux-v4.19/drivers/tty/ipwireless/
Dtty.c49 struct ipw_hardware *hardware; member
218 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
305 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 1); in set_control_lines()
309 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
316 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 1); in set_control_lines()
320 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
327 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 0); in set_control_lines()
329 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
336 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 0); in set_control_lines()
338 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
[all …]
/Linux-v4.19/drivers/staging/fsl-dpaa2/ethernet/
Dethernet-driver.rst20 Unlike regular NICs, in the DPAA2 architecture there is no single hardware block
21 representing network interfaces; instead, several separate hardware resources
29 All hardware resources are allocated and configured through the Management
32 hardware resources, like queues, do not have a corresponding MC object and
57 . . . hardware
59 | MC hardware portals |
68 DPBPs represent hardware buffer pools. Packet I/O is performed in the context
70 hardware resources.
89 | | | | | hardware
91 | I/O hardware portals |
[all …]
/Linux-v4.19/drivers/hwmon/pmbus/
DKconfig21 If you say yes here you get hardware monitoring support for generic
33 If you say yes here you get hardware monitoring support for Analog
44 If you say yes here you get hardware monitoring support for the IBM
54 If you say yes here you get hardware monitoring support for the
64 If you say yes here you get hardware monitoring support for National
74 If you say yes here you get hardware monitoring support for Linear
92 If you say yes here you get hardware monitoring support for Linear
102 If you say yes here you get hardware monitoring support for Maxim
112 If you say yes here you get hardware monitoring support for Maxim
122 If you say yes here you get hardware monitoring support for Maxim
[all …]
/Linux-v4.19/drivers/char/hw_random/
DKconfig14 of possibly several hardware random number generators.
16 These hardware random number generators do feed into the
43 Generator hardware found on Intel i8xx-based motherboards.
56 Generator hardware found on AMD 76x-based motherboards.
69 Generator hardware found on Atmel AT91 devices.
83 Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
96 hardware found on the Broadcom iProc and STB SoCs.
109 Generator hardware found on the AMD Geode LX.
122 Generator hardware found on Niagara2 cpus.
135 Generator hardware found on VIA based motherboards.
[all …]
/Linux-v4.19/drivers/acpi/apei/
DKconfig28 platform hardware errors (such as that from chipset). It
29 works in so called "Firmware First" mode, that is, hardware
31 Linux by firmware. This way, some non-standard hardware
32 error registers or non-standard hardware link can be checked
33 by firmware to produce more valuable hardware error
53 and handles hardware error notifications from SEA, and it may then
55 option allows the OS to look for such hardware error record, and
69 EINJ provides a hardware error injection mechanism, it is
77 ERST is a way provided by APEI to save and retrieve hardware
/Linux-v4.19/drivers/isdn/mISDN/
Ddsp_dtmf.c52 int hardware = 1; in dsp_dtmf_hardware() local
58 hardware = 0; in dsp_dtmf_hardware()
66 hardware = 0; in dsp_dtmf_hardware()
73 hardware = 0; in dsp_dtmf_hardware()
81 hardware = 0; in dsp_dtmf_hardware()
89 hardware = 0; in dsp_dtmf_hardware()
92 dsp->dtmf.hardware = hardware; in dsp_dtmf_hardware()
93 dsp->dtmf.software = !hardware; in dsp_dtmf_hardware()
/Linux-v4.19/Documentation/driver-api/iio/
Dhw-consumer.rst4 An IIO device can be directly connected to another device in hardware. in this
5 case the buffers between IIO provider and IIO consumer are handled by hardware.
12 * :c:func:`iio_hw_consumer_alloc` — Allocate IIO hardware consumer
13 * :c:func:`iio_hw_consumer_free` — Free IIO hardware consumer
14 * :c:func:`iio_hw_consumer_enable` — Enable IIO hardware consumer
15 * :c:func:`iio_hw_consumer_disable` — Disable IIO hardware consumer
/Linux-v4.19/Documentation/powerpc/
Dptrace.txt1 GDB intends to support the following hardware debug features of BookE
4 4 hardware breakpoints (IAC)
5 2 hardware watchpoints (read, write and read-write) (DAC)
6 2 value conditions for the hardware watchpoints (DVC)
16 Query for GDB to discover the hardware debug features. The main info to
17 be returned here is the minimum alignment for the hardware watchpoints.
19 an 8-byte alignment restriction for hardware watchpoints. We'd like to avoid
23 GDB: this query will return the number of hardware breakpoints, hardware
47 Sets a hardware breakpoint or watchpoint, according to the provided structure:
80 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
[all …]
/Linux-v4.19/drivers/staging/fsl-dpaa2/ethsw/
DREADME23 The Ethernet Switch in the DPAA2 architecture consists of several hardware
47 . hardware
49 | MC hardware portals |
59 between ports is offloaded into the hardware. Exposed network interfaces
72 : : : : : : hardware
88 associated hardware resources.
97 Driver configures DPSW to perform hardware switching offload of
101 It allows configuration of hardware learning, flooding, multicast groups,
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-ptp7 features of PTP hardware clocks.
14 hardware clock registered into the PTP class driver
21 This file contains the name of the PTP hardware clock
32 This file contains the PTP hardware clock's maximum
41 alarms offer by the PTP hardware clock.
48 channels offered by the PTP hardware clock.
55 output channels offered by the PTP hardware clock.
62 offered by the PTP hardware clock.
69 pin offered by the PTP hardware clock. The file name
70 is the hardware dependent pin name. Reading from this
[all …]
Ddebugfs-pfo-nx-crypto33 - The total number of AES operations submitted to the hardware.
36 - The total number of bytes hashed by the hardware using SHA-256.
39 - The total number of SHA-256 operations submitted to the hardware.
42 - The total number of bytes hashed by the hardware using SHA-512.
45 - The total number of SHA-512 operations submitted to the hardware.
Dsysfs-class-switchtec18 Description: Component identifier as stored in the hardware (eg. PM8543)
27 Description: Component revision stored in the hardware (read only)
35 Description: Component vendor as stored in the hardware (eg. MICROSEM)
44 Description: Device version as stored in the hardware (read only)
76 Description: Product identifier as stored in the hardware (eg. PSX 48XG3)
85 Description: Product revision stored in the hardware (eg. RevB)
94 Description: Product vendor as stored in the hardware (eg. MICROSEM)
/Linux-v4.19/sound/isa/opti9xx/
Dopti92x-ad1848.c130 unsigned short hardware; member
186 unsigned short hardware) in snd_opti9xx_init() argument
190 chip->hardware = hardware; in snd_opti9xx_init()
191 strcpy(chip->name, snd_opti9xx_names[hardware]); in snd_opti9xx_init()
206 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
209 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
212 switch (hardware) { in snd_opti9xx_init()
216 chip->password = (hardware == OPTi9XX_HW_82C928) ? 0xe2 : 0xe3; in snd_opti9xx_init()
230 chip->mc_base = (hardware == OPTi9XX_HW_82C930) ? 0xf8f : 0xf8d; in snd_opti9xx_init()
239 snd_printk(KERN_ERR "chip %d not supported\n", hardware); in snd_opti9xx_init()
[all …]
/Linux-v4.19/sound/drivers/opl3/
Dopl3_lib.c131 if (opl3->hardware != OPL3_HW_AUTO) in snd_opl3_detect()
136 opl3->hardware = OPL3_HW_OPL2; in snd_opl3_detect()
144 opl3->hardware = OPL3_HW_OPL3; in snd_opl3_detect()
346 unsigned short hardware, in snd_opl3_new() argument
361 opl3->hardware = hardware; in snd_opl3_new()
387 switch (opl3->hardware & OPL3_HW_MASK) { in snd_opl3_init()
405 unsigned short hardware, in snd_opl3_create() argument
413 if ((err = snd_opl3_new(card, hardware, &opl3)) < 0) in snd_opl3_create()
431 switch (opl3->hardware) { in snd_opl3_create()
447 switch (opl3->hardware & OPL3_HW_MASK) { in snd_opl3_create()
[all …]
/Linux-v4.19/Documentation/media/uapi/dvb/
Dintro.rst72 following main hardware components:
75 Here the raw signal reaches the digital TV hardware from a satellite dish or
82 Conditional Access (CA) hardware like CI adapters and smartcard slots
83 The complete TS is passed through the CA hardware. Programs to which
89 Not every digital TV hardware provides conditional access hardware.
104 Modern hardware usually doesn't have a separate decoder hardware, as
106 adapter of the system or by a signal processing hardware embedded on
122 The Linux Digital TV API lets you control these hardware components through
125 control the MPEG2 decoder hardware, the frontend device the tuner and
127 and section filters of the hardware. If the hardware does not support
[all …]
/Linux-v4.19/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt41 The UART hardware is similar to the S3C2440, and is supported by the
48 The NAND hardware is similar to the S3C2440, and is supported by the
55 The USB hardware is similar to the S3C2410, with extended clock source
76 The RTC hardware is similar to the S3C2410, and is supported by the
83 The watchdog hardware is the same as the S3C2410, and is supported by
95 The IIC hardware is the same as the S3C2410, and is supported by the

12345678910>>...57