Home
last modified time | relevance | path

Searched full:exar (Results 1 – 25 of 75) sorted by relevance

123

/kernel/linux/linux-5.10/drivers/net/ethernet/neterion/
DKconfig3 # Exar device configuration
7 bool "Neterion (Exar) devices"
15 the questions about Neterion/Exar cards. If you say Y, you will be
21 tristate "Neterion (Exar) Xframe 10Gb Ethernet Adapter"
24 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
36 tristate "Neterion (Exar) X3100 Series 10GbE PCIe Server Adapter"
39 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
41 Neterion, which was later acquired by Exar. So, the adapters might be
DMakefile3 # Makefile for the Exar network device drivers.
/kernel/linux/linux-4.19/drivers/net/ethernet/neterion/
DKconfig2 # Exar device configuration
6 bool "Neterion (Exar) devices"
14 the questions about Neterion/Exar cards. If you say Y, you will be
20 tristate "Neterion (Exar) Xframe 10Gb Ethernet Adapter"
23 This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
35 tristate "Neterion (Exar) X3100 Series 10GbE PCIe Server Adapter"
38 This driver supports Exar Corp's X3100 Series 10 GbE PCIe
40 Neterion, which was later acquired by Exar. So, the adapters might be
DMakefile2 # Makefile for the Exar network device drivers.
/kernel/linux/linux-4.19/drivers/tty/serial/8250/
D8250_exar.c3 * Probe module for 8250/16550-type Exar chips PCI serial ports.
226 * The Commtech adapters required the MPIOs to be driven low. The Exar in setup_gpio()
279 PROPERTY_ENTRY_U32("exar,first-pin", 0),
356 PROPERTY_ENTRY_U32("exar,first-pin", 10),
453 * These Exar UARTs have an extra interrupt indicator that could fire for a
718 /* Exar Corp. XR17C15[248] Dual/Quad/Octal UART */
719 EXAR_DEVICE(EXAR, EXAR_XR17C152, pbn_exar_XR17C15x),
720 EXAR_DEVICE(EXAR, EXAR_XR17C154, pbn_exar_XR17C15x),
721 EXAR_DEVICE(EXAR, EXAR_XR17C158, pbn_exar_XR17C15x),
723 /* Exar Corp. XR17V[48]35[248] Dual/Quad/Octal/Hexa PCIe UARTs */
[all …]
/kernel/linux/linux-5.10/drivers/tty/serial/8250/
D8250_exar.c3 * Probe module for 8250/16550-type Exar chips PCI serial ports.
144 * Exar UARTs have a SLEEP register that enables or disables each UART in exar_pm()
325 * The Commtech adapters required the MPIOs to be driven low. The Exar in setup_gpio()
378 PROPERTY_ENTRY_U32("exar,first-pin", 0),
455 PROPERTY_ENTRY_U32("exar,first-pin", 10),
482 * For SIMATIC IOT2000, only IOT2040 and its variants have the Exar device,
565 * These Exar UARTs have an extra interrupt indicator that could fire for a
821 /* Exar Corp. XR17C15[248] Dual/Quad/Octal UART */
822 EXAR_DEVICE(EXAR, XR17C152, pbn_exar_XR17C15x),
823 EXAR_DEVICE(EXAR, XR17C154, pbn_exar_XR17C15x),
[all …]
D8250_exar_st16c554.c39 MODULE_DESCRIPTION("8250 serial probe module for Exar cards");
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/
Dgpio-xra1403.txt1 GPIO Driver for XRA1403 16-BIT GPIO Expander With Reset Input from EXAR
18 - compatible = "exar,xra1403".
35 compatible = "exar,xra1403";
Dgpio-exar.txt1 Exportable MPIO interface of Exar UART chips
4 - exar,first-pin: first exportable pins (0..15)
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/
Dgpio-xra1403.txt1 GPIO Driver for XRA1403 16-BIT GPIO Expander With Reset Input from EXAR
18 - compatible = "exar,xra1403".
35 compatible = "exar,xra1403";
Dgpio-exar.txt1 Exportable MPIO interface of Exar UART chips
4 - exar,first-pin: first exportable pins (0..15)
/kernel/linux/linux-4.19/drivers/net/ethernet/neterion/vxge/
Dvxge-version.h10 * vxge-version.h: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
Dvxge-ethtool.h10 * vxge-ethtool.h: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
DMakefile2 # Makefile for Exar Corp's X3100 Series 10 GbE PCIe I/O
/kernel/linux/linux-5.10/drivers/net/ethernet/neterion/vxge/
Dvxge-version.h10 * vxge-version.h: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
Dvxge-ethtool.h10 * vxge-ethtool.h: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
DMakefile3 # Makefile for Exar Corp's X3100 Series 10 GbE PCIe I/O
/kernel/linux/linux-5.10/drivers/gpio/
Dgpio-exar.c3 * GPIO driver for Exar XR17V35X chip
135 ret = device_property_read_u32(&pdev->dev, "exar,first-pin", in gpio_exar_probe()
207 MODULE_DESCRIPTION("Exar GPIO driver");
Dgpio-xra1403.c3 * GPIO driver for EXAR XRA1403 16-bit GPIO expander
207 { .compatible = "exar,xra1403" },
225 MODULE_DESCRIPTION("GPIO expander driver for EXAR XRA1403");
/kernel/linux/linux-4.19/drivers/gpio/
Dgpio-exar.c2 * GPIO driver for Exar XR17V35X chip
135 ret = device_property_read_u32(&pdev->dev, "exar,first-pin", in gpio_exar_probe()
207 MODULE_DESCRIPTION("Exar GPIO driver");
Dgpio-xra1403.c2 * GPIO driver for EXAR XRA1403 16-bit GPIO expander
219 { .compatible = "exar,xra1403" },
237 MODULE_DESCRIPTION("GPIO expander driver for EXAR XRA1403");
/kernel/linux/linux-5.10/drivers/tty/serial/jsm/
Djsm_neo.c50 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_cts_flow_control()
82 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_rts_flow_control()
121 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixon_flow_control()
159 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixoff_flow_control()
200 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_input_flow_control()
238 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_output_flow_control()
310 * EXAR chip bug - RX FIFO COUNT - Fudge factor. in neo_copy_data_from_uart_to_queue()
312 * This resolves a problem/bug with the Exar chip that sometimes in neo_copy_data_from_uart_to_queue()
516 * We have to do it this way, because of the EXAR TXFIFO count bug. in neo_copy_data_from_queue_to_uart()
868 * should encapsulate all 3... At least, thats what Exar says. in neo_parse_lsr()
[all …]
Djsm.h289 * These are the EXTENDED definitions for the Exar 654's Interrupt
332 u8 reserved1[0x2ff - 0x200]; /* U Reserved by Exar */
334 u8 reserved2[0x37f - 0x340]; /* U Reserved by Exar */
343 * Exar made them different than their earlier design. (XR16C854)
408 #define UART_17158_IER_RSVD1 0x10 /* Reserved by Exar */
/kernel/linux/linux-4.19/drivers/tty/serial/jsm/
Djsm_neo.c50 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_cts_flow_control()
82 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_rts_flow_control()
121 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixon_flow_control()
159 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixoff_flow_control()
200 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_input_flow_control()
238 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_output_flow_control()
310 * EXAR chip bug - RX FIFO COUNT - Fudge factor. in neo_copy_data_from_uart_to_queue()
312 * This resolves a problem/bug with the Exar chip that sometimes in neo_copy_data_from_uart_to_queue()
516 * We have to do it this way, because of the EXAR TXFIFO count bug. in neo_copy_data_from_queue_to_uart()
866 * should encapsulate all 3... At least, thats what Exar says. in neo_parse_lsr()
[all …]
Djsm.h289 * These are the EXTENDED definitions for the Exar 654's Interrupt
332 u8 reserved1[0x2ff - 0x200]; /* U Reserved by Exar */
334 u8 reserved2[0x37f - 0x340]; /* U Reserved by Exar */
343 * Exar made them different than their earlier design. (XR16C854)
408 #define UART_17158_IER_RSVD1 0x10 /* Reserved by Exar */

123