Home
last modified time | relevance | path

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

12345678910>>...33

/linux-3.4.99/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()
217 unsigned short hardware, in snd_sbdsp_create() argument
242 (hardware == SB_HW_ALS4000 || in snd_sbdsp_create()
243 hardware == SB_HW_CS5530) ? in snd_sbdsp_create()
252 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()
162 if (chip->hardware < SB_HW_20) in snd_sb8dsp_midi_input_trigger()
168 if (chip->hardware < SB_HW_20) in snd_sb8dsp_midi_input_trigger()
193 if (chip->hardware >= SB_HW_20) { in snd_sb8dsp_midi_output_write()
279 if (chip->hardware >= SB_HW_20) in snd_sb8dsp_midi()
/linux-3.4.99/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-3.4.99/drivers/staging/media/lirc/
Dlirc_serial.c130 static struct lirc_serial hardware[] = { variable
321 soutp(UART_MCR, hardware[type].off); in on()
323 soutp(UART_MCR, hardware[type].on); in on()
335 soutp(UART_MCR, hardware[type].on); in off()
337 soutp(UART_MCR, hardware[type].off); in off()
668 if ((status & hardware[type].signal_pin_change) in irq_handler()
697 dcd = (status & hardware[type].signal_pin) ? 1 : 0; in irq_handler()
844 LIRC_DRIVER_NAME, (void *)&hardware); in lirc_serial_probe()
897 if (sinp(UART_MSR) & hardware[type].signal_pin) in lirc_serial_probe()
919 free_irq(irq, (void *)&hardware); in lirc_serial_probe()
[all …]
/linux-3.4.99/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-3.4.99/drivers/tty/ipwireless/
Dtty.c48 struct ipw_hardware *hardware; member
250 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
346 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 1); in set_control_lines()
350 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
357 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 1); in set_control_lines()
361 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
368 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 0); in set_control_lines()
370 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
377 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 0); in set_control_lines()
379 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
[all …]
Dmain.c175 ipwireless_init_hardware_v1(ipw->hardware, link->resource[0]->start, in config_ipwireless()
195 ipw->network = ipwireless_network_create(ipw->hardware); in config_ipwireless()
199 ipw->tty = ipwireless_tty_create(ipw->hardware, ipw->network); in config_ipwireless()
203 ipwireless_init_hardware_v2_v3(ipw->hardware); in config_ipwireless()
268 ipw->hardware = ipwireless_hardware_create(); in ipwireless_attach()
269 if (!ipw->hardware) { in ipwireless_attach()
301 if (ipw->hardware != NULL) in ipwireless_detach()
302 ipwireless_hardware_free(ipw->hardware); in ipwireless_detach()
/linux-3.4.99/drivers/char/hw_random/
DKconfig14 of possibly several hardware random number generators.
16 These hardware random number generators do not feed directly
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.
82 Generator hardware found on the AMD Geode LX.
95 Generator hardware found on Niagara2 cpus.
108 Generator hardware found on VIA based motherboards.
121 Number Generator hardware found on the Intel IXP4xx NPU.
134 Generator hardware found on OMAP16xx and OMAP24xx multimedia
[all …]
/linux-3.4.99/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-3.4.99/Documentation/networking/
Dtimestamping.txt19 be generated in software (as before) or in hardware (if the hardware
28 SOF_TIMESTAMPING_TX_HARDWARE: try to obtain send time stamp in hardware
32 as generated by the hardware
35 SOF_TIMESTAMPING_RAW_HARDWARE: return original raw hardware time stamp
36 SOF_TIMESTAMPING_SYS_HARDWARE: return hardware time stamp transformed to
71 time stamp was generated by hardware, then this field is
75 hwtimeraw is the original hardware time stamp. Filled in if
79 hwtimetrans is the hardware time stamp transformed so that it
91 that is expected to do hardware time stamping. The parameter is defined in
108 A driver which supports hardware time stamping shall update the struct
[all …]
Dspider_net.txt28 to receive data from the hardware. A "full" descriptor has data in it,
36 ring is handed off to the hardware, which sequentially fills in the
41 and "tail" pointers, managed by the OS, and a hardware current
43 currently being filled. When this descr is filled, the hardware
46 and everything in front of it should be "empty". If the hardware
50 The tail pointer tails or trails the hardware pointer. When the
51 hardware is ahead, the tail pointer will be pointing at a "full"
56 flowing, then the tail pointer can catch up to the hardware pointer.
64 dma-mapping it so as to make it visible to the hardware. The OS will
91 In the above, the hardware has filled in one descr, number 20. Both
[all …]
/linux-3.4.99/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
46 Sets a hardware breakpoint or watchpoint, according to the provided structure:
79 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
[all …]
/linux-3.4.99/drivers/acpi/apei/
DKconfig20 platform hardware errors (such as that from chipset). It
21 works in so called "Firmware First" mode, that is, hardware
23 Linux by firmware. This way, some non-standard hardware
24 error registers or non-standard hardware link can be checked
25 by firmware to produce more valuable hardware error
46 EINJ provides a hardware error injection mechanism, it is
54 ERST is a way provided by APEI to save and retrieve hardware
/linux-3.4.99/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
64 If you say yes here you get hardware monitoring support for Maxim
74 If you say yes here you get hardware monitoring support for Maxim
84 If you say yes here you get hardware monitoring support for Maxim
94 If you say yes here you get hardware monitoring support for TI
105 If you say yes here you get hardware monitoring support for TI
116 If you say yes here you get hardware monitoring support for Intersil
/linux-3.4.99/sound/isa/opti9xx/
Dopti92x-ad1848.c129 unsigned short hardware; member
199 unsigned short hardware) in snd_opti9xx_init() argument
203 chip->hardware = hardware; in snd_opti9xx_init()
204 strcpy(chip->name, snd_opti9xx_names[hardware]); in snd_opti9xx_init()
219 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
222 chip->mc_base_size = opti9xx_mc_size[hardware]; in snd_opti9xx_init()
225 switch (hardware) { in snd_opti9xx_init()
229 chip->password = (hardware == OPTi9XX_HW_82C928) ? 0xe2 : 0xe3; in snd_opti9xx_init()
243 chip->mc_base = (hardware == OPTi9XX_HW_82C930) ? 0xf8f : 0xf8d; in snd_opti9xx_init()
254 snd_printk(KERN_ERR "chip %d not supported\n", hardware); in snd_opti9xx_init()
[all …]
/linux-3.4.99/Documentation/
Dclk.txt24 The second half of the interface is comprised of the hardware-specific
26 hardware-specific structures needed to model a particular clock. For
28 clk_ops, such as .enable or .set_rate, implies the hardware-specific
31 hardware-specific bits for the hypothetical "foo" hardware.
60 clk_ops pointer in struct clk to perform the hardware-specific parts of
79 Part 3 - hardware clk implementations
82 which abstract the details of struct clk from the hardware-specific bits, and
93 struct clk_gate contains struct clk_hw hw as well as hardware-specific
131 This pattern of abstraction is used for every clock hardware
134 Part 4 - supporting your own clk hardware
[all …]
Dhw_random.txt4 special hardware feature on your CPU or motherboard,
7 sysfs support, plus a hardware-specific driver that plugs
25 the hardware RNG device. This data is NOT CHECKED by any
27 hardware is faulty or has been tampered with). Data is only
28 output if the hardware "has-data" flag is set, but nevertheless
39 "rng_available" attribute lists the hardware-specific drivers
52 About the Intel RNG hardware, from the firmware hub datasheet:
/linux-3.4.99/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
/linux-3.4.99/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
28 This file contains the PTP hardware clock's maximum
37 alarms offer by the PTP hardware clock.
44 channels offered by the PTP hardware clock.
51 output channels offered by the PTP hardware clock.
57 This file indicates whether the PTP hardware clock
/linux-3.4.99/sound/drivers/opl3/
Dopl3_lib.c132 if (opl3->hardware != OPL3_HW_AUTO) in snd_opl3_detect()
137 opl3->hardware = OPL3_HW_OPL2; in snd_opl3_detect()
145 opl3->hardware = OPL3_HW_OPL3; in snd_opl3_detect()
347 unsigned short hardware, in snd_opl3_new() argument
364 opl3->hardware = hardware; in snd_opl3_new()
390 switch (opl3->hardware & OPL3_HW_MASK) { in snd_opl3_init()
408 unsigned short hardware, in snd_opl3_create() argument
416 if ((err = snd_opl3_new(card, hardware, &opl3)) < 0) in snd_opl3_create()
434 switch (opl3->hardware) { in snd_opl3_create()
450 switch (opl3->hardware & OPL3_HW_MASK) { in snd_opl3_create()
[all …]
/linux-3.4.99/Documentation/ptp/
Dptp.txt2 * PTP hardware clock infrastructure for Linux
8 ancillary features of PTP hardware clocks.
12 complete set of PTP hardware clock functionality.
26 ** PTP hardware clock kernel API
31 programming the clock hardware. The clock driver notifies the class
40 ** PTP hardware clock user space API
65 reentrant. Since most hardware implementations treat the time value
72 ** Supported hardware
/linux-3.4.99/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
115 This is the s390 hardware accelerated implementation of the
118 As of z990 the ECB and CBC mode are hardware accelerated.
119 As of z196 the CTR mode is hardware accelerated.
127 This is the s390 hardware accelerated implementation of the
130 As of z9 the ECB and CBC modes are hardware accelerated
132 As of z10 the ECB and CBC modes are hardware accelerated
[all …]
/linux-3.4.99/Documentation/w1/masters/
Dds249024 - While the ds2490 supports a hardware search the code doesn't take
26 - The hardware will detect when devices are attached to the bus on the
39 - The hardware supports normal, flexible, and overdrive bus
45 - The hardware supports detecting some error conditions, such as
50 available, the bulk read will return an error and the hardware will
61 the ds2490 hardware, but if the module was unloaded, then reloaded
66 show 0 bytes written. Detaching qemu from the ds2490 hardware and
/linux-3.4.99/arch/powerpc/kvm/
DKconfig50 This module provides access to the hardware capabilities through
64 This module provides access to the hardware capabilities through
78 If you say Y here, KVM will use the hardware virtualization
80 guest operating systems will run at full hardware speed
102 This module provides access to the hardware capabilities through
127 This module provides access to the hardware capabilities through
/linux-3.4.99/Documentation/x86/x86_64/
Dkernel-stacks18 Used for external hardware interrupts. If this is the first external
19 hardware interrupt (i.e. not a nested hardware interrupt) then the
29 hardware stacks cannot nest without races.
40 interrupt-gate descriptor. When an interrupt occurs and the hardware
41 loads such a descriptor, the hardware automatically sets the new stack
83 Used for hardware debug interrupts (interrupt 1) and for software
86 When debugging a kernel, debug interrupts (both hardware and

12345678910>>...33