Home
last modified time | relevance | path

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

12345678910>>...73

/linux/Documentation/devicetree/bindings/leds/
A Dleds-bcm6328.yaml26 with 0 meaning hardware control enabled and 1 hardware control disabled. This
81 brcm,hardware-controlled:
90 An array of hardware link signal sources. Up to four link hardware
149 brcm,hardware-controlled;
154 brcm,hardware-controlled;
159 brcm,hardware-controlled;
164 brcm,hardware-controlled;
180 brcm,hardware-controlled;
186 brcm,hardware-controlled;
222 brcm,hardware-controlled;
[all …]
/linux/Documentation/devicetree/bindings/spi/
A Dsprd,spi-adi.yaml17 framework for its hardware implementation is alike to SPI bus and its timing
22 users should set ADI registers to access analog chip. For hardware channels,
24 which means we can just link one analog chip address to one hardware channel,
25 then users can access the mapped analog chip address by this hardware channel
26 triggered by hardware components instead of ADI software channels.
29 channels, the first value specifies the hardware channel id which is used to
31 the analog chip address where user want to access by hardware components.
42 thus change the hardware spinlock support to be optional to keep backward
66 description: A list of hardware channels
73 use, 2-49 are hardware channels.
[all …]
/linux/drivers/media/rc/
A Dserial_ir.c67 static struct serial_ir_hw hardware[] = { variable
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()
493 if (hardware[type].send_pulse && hardware[type].send_space) in serial_ir_probe()
495 if (hardware[type].set_send_carrier) in serial_ir_probe()
497 if (hardware[type].set_duty_cycle) in serial_ir_probe()
540 KBUILD_MODNAME, &hardware); in serial_ir_probe()
652 hardware[type].send_space(); in serial_ir_tx()
[all …]
/linux/arch/mips/boot/dts/brcm/
A 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/sound/isa/sb/
A 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/sound/isa/wss/
A Dwss_lib.c1158 unsigned short hardware = 0; in snd_ad1848_probe() local
1180 hardware = WSS_HW_AD1847; in snd_ad1848_probe()
1199 if (hardware) { in snd_ad1848_probe()
1200 chip->hardware = hardware; in snd_ad1848_probe()
1246 hw = chip->hardware; in snd_wss_probe()
1300 switch (chip->hardware) { in snd_wss_probe()
1662 switch (chip->hardware) { in snd_wss_chip_id()
1706 unsigned short hardware, in snd_wss_new() argument
1716 chip->hardware = hardware; in snd_wss_new()
1745 unsigned short hardware, in snd_wss_create() argument
[all …]
/linux/drivers/hwmon/pmbus/
A 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
91 If you say yes here you get hardware monitoring support for
101 If you say yes here you get hardware monitoring support for
139 If you say yes here you get hardware monitoring support for the
172 If you say yes here you get hardware monitoring support for the
[all …]
/linux/Documentation/devicetree/bindings/crypto/
A 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/Documentation/devicetree/bindings/net/
A Dfsl,fman-port.yaml13 The Frame Manager (FMan) supports several types of hardware ports:
31 Specifies the hardware port id.
32 Each hardware port on the FMan has its own hardware PortID.
33 Super set of all hardware Port IDs available at FMan Reference
36 Each hardware port is assigned a 4KB, port-specific page in
37 the FMan hardware port memory region (which is part of the
38 FMan memory map). The first 4 KB in the FMan hardware ports
40 The subsequent 63 4KB pages are allocated to the hardware
/linux/drivers/tty/ipwireless/
A Dtty.c49 struct ipw_hardware *hardware; member
216 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
314 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
325 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
334 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
343 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
436 struct ipw_hardware *hardware, in add_tty() argument
444 ttys[j]->hardware = hardware; in add_tty()
486 if (add_tty(j, hardware, network, in ipwireless_tty_create()
492 if (add_tty(j, hardware, network, in ipwireless_tty_create()
[all …]
/linux/Documentation/devicetree/bindings/mailbox/
A Dmediatek,gce-props.yaml14 single-core command dispatcher for MediaTek hardware. The Command Queue
19 driver. A device driver that uses the CMDQ driver to configure its hardware
21 channel corresponding to a GCE hardware thread to send a message, specifying
22 that the GCE thread to configure its hardware. The mailbox provider can also
23 reserve a mailbox channel to configure GCE hardware register by the specific
33 Some gce-events are hardware-bound and cannot be changed by software.
38 On the other hand, some gce-events are not hardware-bound and can be
40 event ID 855, which is not bound to any hardware, to 1 when the driver
44 to any hardware and is not yet used in any software driver.
45 To determine if the event ID is bound to the hardware or used by a
/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
A 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 |
71 hardware resources.
90 | | | | | hardware
92 | I/O hardware portals |
159 options and associated hardware resources.
[all …]
/linux/Documentation/driver-api/iio/
A 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/Documentation/networking/devlink/
A 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
34 Level Path Compression trie (LPC-trie) in hardware.
38 information about the underlying hardware, this debugging can be made
49 Traditionally it has been used as an alternative model for hardware
85 is hardware counting for a specific table.
[all …]
/linux/drivers/isdn/mISDN/
A 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/drivers/char/hw_random/
A DKconfig15 of possibly several hardware random number generators.
71 Generator hardware found on Atmel AT91 devices.
122 Generator hardware found on the AMD Geode LX.
135 Generator hardware found on Niagara2 cpus.
201 Generator hardware found on Octeon processors.
226 Generator hardware.
365 Generator hardware found on APM X-Gene SoC.
392 Generator hardware found on a PIC32.
433 Generator hardware found on Cavium SoCs.
447 Generator hardware found on Mediatek SoCs.
[all …]
/linux/Documentation/arch/powerpc/
A 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/Documentation/translations/sp_SP/process/
A 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
57 hardware.
59 Oficiales de seguridad de hardware
62 El equipo actual de oficiales de seguridad de hardware:
98 vendedores de hardware y otras partes.
119 Además, el equipo de seguridad de hardware también excluirá al
125 a los oficiales de seguridad de hardware.
[all …]
/linux/drivers/clk/ingenic/
A 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/sound/isa/opti9xx/
A Dopti92x-ad1848.c113 unsigned short hardware; member
169 unsigned short hardware) in snd_opti9xx_init() argument
173 chip->hardware = hardware; in snd_opti9xx_init()
195 switch (hardware) { in snd_opti9xx_init()
237 switch (chip->hardware) { in snd_opti9xx_read()
280 switch (chip->hardware) { in snd_opti9xx_write()
334 switch (chip->hardware) { in snd_opti9xx_configure()
495 if (chip->hardware > OPTi9XX_HW_82C928) { in snd_opti9xx_configure()
887 if (chip->hardware == OPTi9XX_HW_82C928 ||
888 chip->hardware == OPTi9XX_HW_82C929 ||
[all …]
/linux/Documentation/ABI/testing/
A 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
A Dsysfs-platform-dfl-fme101 hardware.
108 hardware.
135 threshold, hardware starts 50% or 90% throttling (see
144 threshold, hardware starts 100% throttling.
160 hardware threshold1 (see 'temp1_max'), otherwise 0.
167 hardware threshold2 (see 'temp1_crit'), otherwise 0.
193 this threshold, hardware starts 50% throttling.
195 As hardware only accepts values in Watts, so input value will
206 this threshold, hardware starts 90% throttling.
218 above hardware threshold1 (see 'power1_max'), otherwise 0.
[all …]
A 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.
/linux/arch/riscv/
A 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/Documentation/driver-api/media/
A Dcec-core.rst7 hardware. It is designed to handle a multiple types of hardware (receivers,
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
154 (some hardware may always be in 'monitor all' mode).
166 (some hardware may always be in 'monitor pin' mode).
223 To log the current CEC hardware status::
271 or LOW_DRIVE if the hardware cannot differentiate or something
272 else entirely. Some hardware only supports OK and FAIL as the
[all …]

Completed in 41 milliseconds

12345678910>>...73