Home
last modified time | relevance | path

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

12345678910>>...76

/linux-6.3-rc2/Documentation/devicetree/bindings/leds/
A Dleds-bcm6328.yaml26 with 0 meaning hardware control enabled and 1 hardware control disabled. This
85 brcm,hardware-controlled:
94 An array of hardware link signal sources. Up to four link hardware
153 brcm,hardware-controlled;
158 brcm,hardware-controlled;
163 brcm,hardware-controlled;
168 brcm,hardware-controlled;
184 brcm,hardware-controlled;
190 brcm,hardware-controlled;
226 brcm,hardware-controlled;
[all …]
/linux-6.3-rc2/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-6.3-rc2/drivers/media/rc/
A Dserial_ir.c66 static struct serial_ir_hw hardware[] = { variable
163 soutp(UART_MCR, hardware[type].off); in on()
165 soutp(UART_MCR, hardware[type].on); in on()
171 soutp(UART_MCR, hardware[type].on); in off()
173 soutp(UART_MCR, hardware[type].off); in off()
492 if (hardware[type].send_pulse && hardware[type].send_space) in serial_ir_probe()
494 if (hardware[type].set_send_carrier) in serial_ir_probe()
496 if (hardware[type].set_duty_cycle) in serial_ir_probe()
539 KBUILD_MODNAME, &hardware); in serial_ir_probe()
651 hardware[type].send_space(); in serial_ir_tx()
[all …]
/linux-6.3-rc2/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-6.3-rc2/sound/isa/sb/
A Dsb_common.c118 switch (chip->hardware) { in snd_sbdsp_probe()
122 chip->hardware = SB_HW_10; in snd_sbdsp_probe()
127 chip->hardware = SB_HW_201; in snd_sbdsp_probe()
130 chip->hardware = SB_HW_20; in snd_sbdsp_probe()
135 chip->hardware = SB_HW_PRO; in snd_sbdsp_probe()
139 chip->hardware = SB_HW_16; in snd_sbdsp_probe()
177 unsigned short hardware, in snd_sbdsp_create() argument
199 (hardware == SB_HW_ALS4000 || in snd_sbdsp_create()
200 hardware == SB_HW_CS5530) ? in snd_sbdsp_create()
209 if (hardware == SB_HW_ALS4000) in snd_sbdsp_create()
[all …]
/linux-6.3-rc2/sound/isa/wss/
A Dwss_lib.c1155 unsigned short hardware = 0; in snd_ad1848_probe() local
1177 hardware = WSS_HW_AD1847; in snd_ad1848_probe()
1196 if (hardware) { in snd_ad1848_probe()
1197 chip->hardware = hardware; in snd_ad1848_probe()
1243 hw = chip->hardware; in snd_wss_probe()
1296 switch (chip->hardware) { in snd_wss_probe()
1660 switch (chip->hardware) { in snd_wss_chip_id()
1704 unsigned short hardware, in snd_wss_new() argument
1714 chip->hardware = hardware; in snd_wss_new()
1743 unsigned short hardware, in snd_wss_create() argument
[all …]
/linux-6.3-rc2/drivers/hwmon/pmbus/
A DKconfig21 If you say yes here you get hardware monitoring support for generic
35 If you say yes here you get hardware monitoring support for Analog
44 If you say yes here you get hardware monitoring support for Analog
54 If you say yes here you get hardware monitoring support for BEL
63 If you say yes here you get hardware monitoring support for BluTek
72 If you say yes here you get hardware monitoring support for
82 If you say yes here you get hardware monitoring support for
102 If you say yes here you get hardware monitoring support for Delta
120 If you say yes here you get hardware monitoring support for the
153 If you say yes here you get hardware monitoring support for the
[all …]
/linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/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-6.3-rc2/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-6.3-rc2/drivers/char/hw_random/
A DKconfig15 of possibly several hardware random number generators.
70 Generator hardware found on Atmel AT91 devices.
120 Generator hardware found on the AMD Geode LX.
133 Generator hardware found on Niagara2 cpus.
199 Generator hardware found on Octeon processors.
224 Generator hardware.
354 Generator hardware found on APM X-Gene SoC.
381 Generator hardware found on a PIC32.
421 Generator hardware found on Cavium SoCs.
435 Generator hardware found on Mediatek SoCs.
[all …]
/linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-class-led-trigger-pattern19 Specify a hardware pattern for the LED, for LED hardware that
21 to some preprogrammed hardware patterns. It deactivates any active
24 Since different LED hardware can have different semantics of
25 hardware patterns, each driver is expected to provide its own
26 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.
A 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 …]
A 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.3-rc2/Documentation/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-6.3-rc2/Documentation/process/
A Dembargoed-hardware-issues.rst3 Embargoed hardware issues
16 hardware vendors and other parties. For some of the issues, software
28 The team only handles the coordination of embargoed hardware security
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
46 While hardware security issues are often handled by the affected hardware
48 identified a potential hardware flaw.
53 The current team of hardware security officers:
87 keep hardware security issues under embargo for coordination between
90 The Linux kernel community has successfully handled hardware security
[all …]
/linux-6.3-rc2/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-6.3-rc2/drivers/acpi/apei/
A 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
67 ERST is a way provided by APEI to save and retrieve hardware
/linux-6.3-rc2/sound/isa/opti9xx/
A Dopti92x-ad1848.c112 unsigned short hardware; member
168 unsigned short hardware) in snd_opti9xx_init() argument
172 chip->hardware = hardware; in snd_opti9xx_init()
194 switch (hardware) { in snd_opti9xx_init()
236 switch (chip->hardware) { in snd_opti9xx_read()
279 switch (chip->hardware) { in snd_opti9xx_write()
333 switch (chip->hardware) { in snd_opti9xx_configure()
494 if (chip->hardware > OPTi9XX_HW_82C928) { in snd_opti9xx_configure()
886 if (chip->hardware == OPTi9XX_HW_82C928 ||
887 chip->hardware == OPTi9XX_HW_82C929 ||
[all …]
/linux-6.3-rc2/Documentation/devicetree/bindings/serial/
A Dnvidia,tegra194-tcu.yaml14 The TCU is a system for sharing a hardware UART instance among multiple
18 with the hardware implementing the TCU.
40 transmitting data from and to the hardware UART.
42 - description: mailbox for receiving data from hardware UART
43 - description: mailbox for transmitting data to hardware UART

Completed in 23 milliseconds

12345678910>>...76