Home
last modified time | relevance | path

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

12345678910>>...71

/linux-6.12.1/drivers/media/rc/
Dserial_ir.c67 static struct serial_ir_hw hardware[] = { variable
69 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_HOMEBREW].lock),
83 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO].lock),
94 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO_REMOTE].lock),
105 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_ANIMAX].lock),
113 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IGOR].lock),
164 soutp(UART_MCR, hardware[type].off); in on()
166 soutp(UART_MCR, hardware[type].on); in on()
172 soutp(UART_MCR, hardware[type].on); in off()
174 soutp(UART_MCR, hardware[type].off); in off()
[all …]
/linux-6.12.1/sound/isa/sb/
Dsb_common.c119 switch (chip->hardware) { in snd_sbdsp_probe()
123 chip->hardware = SB_HW_10; in snd_sbdsp_probe()
128 chip->hardware = SB_HW_201; in snd_sbdsp_probe()
131 chip->hardware = SB_HW_20; in snd_sbdsp_probe()
136 chip->hardware = SB_HW_PRO; in snd_sbdsp_probe()
140 chip->hardware = SB_HW_16; in snd_sbdsp_probe()
178 unsigned short hardware, in snd_sbdsp_create() argument
200 (hardware == SB_HW_ALS4000 || in snd_sbdsp_create()
201 hardware == SB_HW_CS5530) ? in snd_sbdsp_create()
210 if (hardware == SB_HW_ALS4000) in snd_sbdsp_create()
[all …]
/linux-6.12.1/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-6.12.1/sound/isa/wss/
Dwss_lib.c410 if ((timeout & CS4231_MCE) == 0 || !(chip->hardware & hw_mask)) in snd_wss_mce_down()
592 if (!(chip->hardware & WSS_HW_AD1848_MASK)) { in snd_wss_calibrate_mute()
600 if (chip->hardware == WSS_HW_INTERWAVE) { in snd_wss_calibrate_mute()
622 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_playback_format()
623 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_playback_format()
637 } else if (chip->hardware == WSS_HW_AD1845) { in snd_wss_playback_format()
659 if (chip->hardware != WSS_HW_INTERWAVE && !chip->single_dma) { in snd_wss_playback_format()
668 if (chip->hardware == WSS_HW_OPL3SA2) in snd_wss_playback_format()
683 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_capture_format()
684 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_capture_format()
[all …]
/linux-6.12.1/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 the ACBEL
44 If you say yes here you get hardware monitoring support for Analog
53 If you say yes here you get hardware monitoring support for Analog
63 If you say yes here you get hardware monitoring support for Analog
73 If you say yes here you get hardware monitoring support for BEL
82 If you say yes here you get hardware monitoring support for BluTek
91 If you say yes here you get hardware monitoring support for
101 If you say yes here you get hardware monitoring support for
112 If you say yes here you get hardware monitoring support for the IBM
[all …]
/linux-6.12.1/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-6.12.1/drivers/tty/ipwireless/
Dtty.c49 struct ipw_hardware *hardware; member
216 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
310 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 1); in set_control_lines()
314 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
321 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 1); in set_control_lines()
325 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
332 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 0); in set_control_lines()
334 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
341 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 0); in set_control_lines()
343 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
[all …]
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
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
58 . . . hardware
60 | MC hardware portals |
69 DPBPs represent hardware buffer pools. Packet I/O is performed in the context
71 hardware resources.
90 | | | | | hardware
92 | I/O hardware portals |
[all …]
/linux-6.12.1/Documentation/networking/devlink/
Ddevlink-dpipe.rst10 While performing the hardware offloading process, much of the hardware
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
38 information about the underlying hardware, this debugging can be made
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
[all …]
/linux-6.12.1/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-6.12.1/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-6.12.1/drivers/char/hw_random/
DKconfig15 of possibly several hardware random number generators.
17 These hardware random number generators do feed into the
44 Generator hardware found on Intel i8xx-based motherboards.
58 Generator hardware found on AMD 76x-based motherboards.
71 Generator hardware found on Atmel AT91 devices.
83 Generator hardware based on Silex Insight BA431 IP.
95 Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
108 hardware found on the Broadcom iProc and STB SoCs.
122 Generator hardware found on the AMD Geode LX.
135 Generator hardware found on Niagara2 cpus.
[all …]
/linux-6.12.1/Documentation/arch/powerpc/
Dptrace.rst5 GDB intends to support the following hardware debug features of BookE
8 4 hardware breakpoints (IAC)
9 2 hardware watchpoints (read, write and read-write) (DAC)
10 2 value conditions for the hardware watchpoints (DVC)
21 Query for GDB to discover the hardware debug features. The main info to
22 be returned here is the minimum alignment for the hardware watchpoints.
24 an 8-byte alignment restriction for hardware watchpoints. We'd like to avoid
28 GDB: this query will return the number of hardware breakpoints, hardware
53 Sets a hardware breakpoint or watchpoint, according to the provided structure::
86 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
[all …]
/linux-6.12.1/Documentation/translations/sp_SP/process/
Dembargoed-hardware-issues.rst4 :Original: Documentation/process/embargoed-hardware-issues.rst
7 Problemas de hardware embargados
13 Los problemas de hardware que resultan en problemas de seguridad son una
17 Los problemas de hardware como Meltdown, Spectre, L1TF, etc. deben
20 vendedores diferentes de OS, distribuciones, vendedores de hardware y
30 El equipo de seguridad de hardware del kernel de Linux es separado del
34 hardware embargados. Los informes de errores de seguridad de software puro
41 <hardware-security@kernel.org>. Esta es una lista privada de oficiales de
51 - PGP: https://www.kernel.org/static/files/hardware-security.asc
52 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
[all …]
/linux-6.12.1/drivers/clk/ingenic/
DKconfig13 Support the clocks provided by the CGU hardware on Ingenic JZ4740
23 Support the clocks provided by the CGU hardware on Ingenic JZ4755
33 Support the clocks provided by the CGU hardware on Ingenic JZ4725B
43 Support the clocks provided by the CGU hardware on Ingenic JZ4760
53 Support the clocks provided by the CGU hardware on Ingenic JZ4770
63 Support the clocks provided by the CGU hardware on Ingenic JZ4780
73 Support the clocks provided by the CGU hardware on Ingenic X1000
83 Support the clocks provided by the CGU hardware on Ingenic X1830
/linux-6.12.1/sound/isa/opti9xx/
Dopti92x-ad1848.c113 unsigned short hardware; member
169 unsigned short hardware) in snd_opti9xx_init() argument
173 chip->hardware = hardware; in snd_opti9xx_init()
174 strcpy(chip->name, snd_opti9xx_names[hardware]); in snd_opti9xx_init()
189 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
192 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
195 switch (hardware) { in snd_opti9xx_init()
199 chip->password = (hardware == OPTi9XX_HW_82C928) ? 0xe2 : 0xe3; in snd_opti9xx_init()
213 chip->mc_base = (hardware == OPTi9XX_HW_82C930) ? 0xf8f : 0xf8d; in snd_opti9xx_init()
222 dev_err(chip->card->dev, "chip %d not supported\n", hardware); in snd_opti9xx_init()
[all …]
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-platform-dfl-fme101 hardware.
108 hardware.
133 Description: Read-Only. It returns hardware threshold1 temperature in
135 threshold, hardware starts 50% or 90% throttling (see
142 Description: Read-Only. It returns hardware threshold2 temperature in
144 threshold, hardware starts 100% throttling.
150 Description: Read-Only. It returns hardware trip threshold temperature in
160 hardware threshold1 (see 'temp1_max'), otherwise 0.
167 hardware threshold2 (see 'temp1_crit'), otherwise 0.
173 Description: Read-Only. Read this file to get the policy of hardware threshold1
[all …]
Dsysfs-class-led-trigger-pattern29 Specify a hardware pattern for the LED, for LED hardware that
31 to some preprogrammed hardware patterns. It deactivates any active
34 Since different LED hardware can have different semantics of
35 hardware patterns, each driver is expected to provide its own
36 description for the hardware patterns in their documentation
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-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
48 alarms offer by the PTP hardware clock.
55 channels offered by the PTP hardware clock.
62 output channels offered by the PTP hardware clock.
69 offered by the PTP hardware clock.
89 pin offered by the PTP hardware clock. The file name
90 is the hardware dependent pin name. Reading from this
[all …]
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-6.12.1/arch/riscv/
DKconfig.socs20 This enables support for SiFive SoC platform hardware.
25 This enables support for Sophgo SoC platform hardware.
36 This enables support for StarFive SoC platform hardware.
44 This enables support for Allwinner sun20i platform hardware,
71 This enables support for Canaan Kendryte series SoC platform hardware.
81 This enables support for Canaan Kendryte K210 SoC platform hardware.
/linux-6.12.1/Documentation/driver-api/media/
Dcec-core.rst7 hardware. It is designed to handle a multiple types of hardware (receivers,
35 The struct cec_adapter represents the CEC adapter hardware. It is created by
61 capabilities of the hardware and which parts are to be handled
128 hardware. They are all called with the mutex adap->lock held.
131 To enable/disable the hardware::
135 This callback enables or disables the CEC hardware. Enabling the CEC hardware
139 hardware is enabled. CEC drivers should not set CEC_CAP_NEEDS_HPD unless
140 the hardware design requires that as this will make it impossible to wake
152 that are not for us. Not all hardware supports this and this function is only
154 (some hardware may always be in 'monitor all' mode).
[all …]
/linux-6.12.1/Documentation/userspace-api/media/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-6.12.1/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
59 EINJ provides a hardware error injection mechanism, it is
80 ERST is a way provided by APEI to save and retrieve hardware

12345678910>>...71