Home
last modified time | relevance | path

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

12

/Linux-v5.4/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.
/Linux-v5.4/drivers/tty/serial/8250/
D8250_exar.c3 * Probe module for 8250/16550-type Exar chips PCI serial ports.
136 * Exar UARTs have a SLEEP register that enables or disables each UART in exar_pm()
298 * The Commtech adapters required the MPIOs to be driven low. The Exar in setup_gpio()
341 PROPERTY_ENTRY_U32("exar,first-pin", 0),
418 PROPERTY_ENTRY_U32("exar,first-pin", 10),
445 * For SIMATIC IOT2000, only IOT2040 and its variants have the Exar device,
528 * These Exar UARTs have an extra interrupt indicator that could fire for a
744 /* Exar Corp. XR17C15[248] Dual/Quad/Octal UART */
745 EXAR_DEVICE(EXAR, EXAR_XR17C152, pbn_exar_XR17C15x),
746 EXAR_DEVICE(EXAR, EXAR_XR17C154, pbn_exar_XR17C15x),
[all …]
D8250_exar_st16c554.c39 MODULE_DESCRIPTION("8250 serial probe module for Exar cards");
DKconfig134 tristate "8250/16550 Exar/Commtech PCI/PCIe device support"
263 tristate "Support Exar ST16C554/554D Quad UART"
266 The Uplogix Envoy TU301 uses this Exar Quad UART. If you are
/Linux-v5.4/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)
Dgpio-pca953x.txt36 exar,xra1202
/Linux-v5.4/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
Dvxge-main.h10 * vxge-main.h: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
Dvxge-ethtool.c10 * vxge-ethtool.c: Driver for Exar Corp's X3100 Series 10GbE PCIe I/O
12 * Copyright(c) 2002-2010 Exar Corp.
/Linux-v5.4/drivers/gpio/
Dgpio-exar.c3 * GPIO driver for Exar XR17V35X chip
132 ret = device_property_read_u32(&pdev->dev, "exar,first-pin", in gpio_exar_probe()
201 MODULE_DESCRIPTION("Exar GPIO driver");
Dgpio-xra1403.c3 * GPIO driver for EXAR XRA1403 16-bit GPIO expander
208 { .compatible = "exar,xra1403" },
226 MODULE_DESCRIPTION("GPIO expander driver for EXAR XRA1403");
DKconfig214 on Exar XR17V352/354/358 chips.
1451 tristate "EXAR XRA1403 16-bit GPIO expander"
1454 GPIO driver for EXAR XRA1403 16-bit SPI-based GPIO expander.
DMakefile54 obj-$(CONFIG_GPIO_EXAR) += gpio-exar.o
/Linux-v5.4/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 */
Djsm_cls.c470 /* We have to do it this way, because of the EXAR TXFIFO count bug. */ in cls_copy_data_from_queue_to_uart()
/Linux-v5.4/include/uapi/linux/
Dserial_core.h50 #define PORT_XR17D15X 21 /* Exar XR17D15x UART */
53 #define PORT_XR17V35X 24 /* Exar XR17V35x UARTs */
/Linux-v5.4/drivers/usb/serial/
Dio_usbvend.h479 #define MANUF_UART_EXAR_654_EARLY 0 // Exar 16C654 in Edgeport/4s before 11/98
480 #define MANUF_UART_EXAR_654 1 // Exar 16C654
481 #define MANUF_UART_EXAR_2852 2 // Exar 16C2852
/Linux-v5.4/arch/arm/boot/dts/
Dimx53-ppd.dts303 compatible = "exar,xra1403";
311 compatible = "exar,xra1403";
/Linux-v5.4/Documentation/devicetree/bindings/
Dvendor-prefixes.yaml318 "^exar,.*":
319 description: Exar Corporation
/Linux-v5.4/arch/powerpc/kernel/
Dlegacy_serial.c302 * EXAR ports and we default to the most common case. If your UART in add_legacy_pci_port()

12