Home
last modified time | relevance | path

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

123456789

/drivers/staging/media/lirc/
Dlirc_serial.c121 static struct lirc_serial hardware[] = { variable
123 .lock = __SPIN_LOCK_UNLOCKED(hardware[LIRC_HOMEBREW].lock),
140 .lock = __SPIN_LOCK_UNLOCKED(hardware[LIRC_IRDEO].lock),
152 .lock = __SPIN_LOCK_UNLOCKED(hardware[LIRC_IRDEO_REMOTE].lock),
164 .lock = __SPIN_LOCK_UNLOCKED(hardware[LIRC_ANIMAX].lock),
175 .lock = __SPIN_LOCK_UNLOCKED(hardware[LIRC_IGOR].lock),
281 soutp(UART_MCR, hardware[type].off); in on()
283 soutp(UART_MCR, hardware[type].on); in on()
289 soutp(UART_MCR, hardware[type].on); in off()
291 soutp(UART_MCR, hardware[type].off); in off()
[all …]
/drivers/tty/ipwireless/
Dtty.c48 struct ipw_hardware *hardware; member
217 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
313 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 1); in set_control_lines()
317 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
324 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 1); in set_control_lines()
328 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
335 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 0); in set_control_lines()
337 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
344 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 0); in set_control_lines()
346 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
[all …]
Dmain.c183 ipwireless_init_hardware_v1(ipw->hardware, link->resource[0]->start, in config_ipwireless()
203 ipw->network = ipwireless_network_create(ipw->hardware); in config_ipwireless()
207 ipw->tty = ipwireless_tty_create(ipw->hardware, ipw->network); in config_ipwireless()
211 ipwireless_init_hardware_v2_v3(ipw->hardware); in config_ipwireless()
276 ipw->hardware = ipwireless_hardware_create(); in ipwireless_attach()
277 if (!ipw->hardware) { in ipwireless_attach()
309 if (ipw->hardware != NULL) in ipwireless_detach()
310 ipwireless_hardware_free(ipw->hardware); in ipwireless_detach()
Dnetwork.c39 struct ipw_hardware *hardware; member
114 ret = ipwireless_send_packet(network->hardware, in ipwireless_ppp_start_xmit()
130 ret = ipwireless_send_packet(network->hardware, in ipwireless_ppp_start_xmit()
426 network->hardware = hw; in ipwireless_network_create()
444 ipwireless_stop_interrupts(network->hardware); in ipwireless_network_free()
445 ipwireless_associate_network(network->hardware, NULL); in ipwireless_network_free()
/drivers/char/hw_random/
DKconfig14 of possibly several hardware random number generators.
16 These hardware random number generators do not feed directly
45 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.
84 Generator hardware found on the Broadcom BCM63xx SoCs.
97 Generator hardware found on the Broadcom BCM2835 SoCs.
110 hardware found on the Broadcom iProc SoCs.
123 Generator hardware found on the AMD Geode LX.
136 Generator hardware found on Niagara2 cpus.
[all …]
/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()
Ddsp.h106 int hardware; /* conf is processed by hardware */ member
124 int hardware; /* dtmf uses hardware decoding */ member
149 int hardware; /* tones are generated by hardware */ member
163 int hardware; /* echo is generated by hardware */ member
Ddsp_cmx.c168 odsp->name, odsp->echo.hardware, odsp->echo.software, in dsp_cmx_debug()
416 if (!dsp->echo.software && !dsp->echo.hardware) { in dsp_cmx_hardware()
436 dsp->echo.hardware = 0; in dsp_cmx_hardware()
440 dsp->echo.hardware = 1; in dsp_cmx_hardware()
455 dsp->echo.hardware = 1; in dsp_cmx_hardware()
499 dsp->echo.hardware = 1; in dsp_cmx_hardware()
564 conf->hardware = 0; in dsp_cmx_hardware()
569 if (member->dsp->echo.hardware || member->dsp->echo.software) { in dsp_cmx_hardware()
670 conf->hardware = 0; in dsp_cmx_hardware()
745 conf->hardware = 1; in dsp_cmx_hardware()
[all …]
/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 National
54 If you say yes here you get hardware monitoring support for Linear
72 If you say yes here you get hardware monitoring support for Maxim
82 If you say yes here you get hardware monitoring support for Maxim
92 If you say yes here you get hardware monitoring support for Maxim
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 TI
122 If you say yes here you get hardware monitoring support for TI
[all …]
/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"
/drivers/acpi/apei/
DKconfig27 platform hardware errors (such as that from chipset). It
28 works in so called "Firmware First" mode, that is, hardware
30 Linux by firmware. This way, some non-standard hardware
31 error registers or non-standard hardware link can be checked
32 by firmware to produce more valuable hardware error
53 EINJ provides a hardware error injection mechanism, it is
61 ERST is a way provided by APEI to save and retrieve hardware
/drivers/crypto/
DKconfig6 Say Y here to get to see options for hardware crypto devices and
84 This is the s390 hardware accelerated implementation of the
94 This is the s390 hardware accelerated implementation of the
104 This is the s390 hardware accelerated implementation of the
116 This is the s390 hardware accelerated implementation of the
119 As of z990 the ECB and CBC mode are hardware accelerated.
120 As of z196 the CTR mode is hardware accelerated.
128 This is the s390 hardware accelerated implementation of the
131 As of z9 the ECB and CBC modes are hardware accelerated
133 As of z10 the ECB and CBC modes are hardware accelerated
[all …]
/drivers/staging/fsl-mc/
DREADME.txt23 DPAA2 is a hardware architecture designed for high-speeed network
29 A DPAA2 hardware component called the Management Complex (or MC) manages the
30 DPAA2 hardware resources. The MC provides an object-based abstraction for
31 software drivers to use the DPAA2 hardware.
33 The MC uses DPAA2 hardware resources such as queues, buffer pools, and
81 in the DPAA2 hardware. A simple scenario is described illustrating
106 enumerate the contents of the DPRC, discover the hardware
124 All objects in a container share the same hardware "isolation context".
140 utilizing multiple hardware objects. Each object has specialized
143 hardware resources, flexibility, and performance advantages.
[all …]
/drivers/staging/most/Documentation/
Ddriver_usage.txt8 MOST defines the protocol, hardware and software layers necessary to allow
26 The driver consists basically of three layers. The hardware layer, the
33 system architecture. A module of the hardware layer is referred to as an
34 HDM (hardware dependent module). Each module of this layer handles exactly
49 The hardware layer contains so called hardware dependent modules (HDM). For each
50 peripheral interface the hardware supports the driver has a suitable module
58 Host wants to communicate with hardware via MediaLB.
61 Host wants to communicate with the hardware via I2C.
64 Host wants to communicate with the hardware via USB.
111 are needed for the driver to process buffer padding, as expected by hardware,
[all …]
/drivers/ptp/
DKconfig17 microseconds. In addition, with the help of special hardware
36 getting hardware time stamps on the PTP Ethernet packets
50 getting hardware time stamps on the PTP Ethernet packets
69 getting hardware time stamps on the PTP Ethernet packets
82 clock. The hardware supports time stamping of PTP packets
87 hardware time stamps on the PTP Ethernet packets using the
/drivers/parport/
DKconfig12 the architecture might have PC parallel port hardware.
43 tristate "PC-style hardware"
68 Many parallel port chipsets provide hardware that can speed up
106 Say Y here if you need support for the parallel port hardware on
120 tristate "Atari hardware"
124 Say Y here if you need support for the parallel port hardware on
134 tristate "Sparc hardware"
140 actually have pc style hardware instead.
146 Say Y here if you need support for the parallel port hardware on
/drivers/staging/fsl-mc/bus/
DKconfig14 QorIQ Management Complex (fsl-mc). The fsl-mc is a hardware
16 for hardware building-blocks in the SoC that can be used
17 to dynamically create networking hardware objects such as
/drivers/ntb/test/
DKconfig5 doorbells of the ntb hardware. This driver may be used to test that
6 your ntb hardware and drivers are functioning at a basic level.
16 This driver may be used to test that your ntb hardware and drivers are
/drivers/mailbox/
DKconfig4 Mailbox is a framework to control hardware communication between
6 signals. Say Y if your platform supports hardware mailboxes.
32 Mailbox implementation for OMAP family chips with hardware for
79 hardware for interprocessor communication.
/drivers/isdn/
DKconfig49 access ISDN hardware in a device independent way. (For details see
53 three-party conferences (if supported by the specific hardware
56 Select this option and the appropriate hardware driver below if
63 source "drivers/isdn/hardware/Kconfig"
/drivers/media/usb/cx231xx/
DKconfig24 cx231xx hardware has a builtin RX/TX support. However, a few
25 designs opted to not use it, but, instead, some other hardware.
26 This module enables the usage of those other hardware, like the
/drivers/clocksource/
DKconfig158 This must be disabled for hardware validation purposes to detect any
159 hardware anomalies of missing events.
257 the Compare Match Timer (CMT) hardware available in 16/32/48-bit
267 Timer Pulse Unit 2 (MTU2) hardware available on SoCs from Renesas.
268 This hardware comes with 16 bit-timer registers.
277 the 32-bit Timer Unit (TMU) hardware available on a wide range
286 the 48-bit System Timer (STI) hardware available on a SoCs
/drivers/watchdog/
DKconfig17 reboot the machine) and a driver for hardware watchdog boards, which
62 from some situations that the hardware watchdog will recover
217 boards have hardware problems that will cause the machine to simply
453 This is the driver for the hardware watchdog
613 This is the driver for the hardware watchdog on Single Board
636 This is the driver for the hardware watchdog on the ALi M1535 PMU.
647 This is the driver for the hardware watchdog on the ALi M7101 PMU
660 This is the driver for the hardware watchdog on the Fintek
695 This is the driver for the hardware watchdog built in to the
738 This is the driver for the hardware watchdog on the IB700 Single
[all …]
/drivers/firmware/broadcom/
DKconfig6 important hardware configuration as well as some minor user setup.
11 hardware part itself.
/drivers/hsi/controllers/
DKconfig7 tristate "OMAP SSI hardware driver"
12 If you say Y here, you will enable the OMAP SSI hardware driver.

123456789