/linux/drivers/net/ethernet/neterion/ |
H A D | Kconfig | 3 # 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.
|
H A D | Makefile | 3 # Makefile for the Exar network device drivers.
|
H A D | s2io-regs.h | 3 * Copyright(c) 2002-2010 Exar Corp.
|
/linux/drivers/tty/serial/8250/ |
H A D | 8250_exar.c | 3 * Probe module for 8250/16550-type Exar chips PCI serial ports. 305 * exar_mpio_config_output() - Configure an Exar MPIO as an output 348 * _exar_mpio_set() - Set an Exar MPIO output high or low 423 * Exar UARTs have a SLEEP register that enables or disables each UART in exar_pm() 597 * Some Exar UARTs have an auto-tristate feature while others require setting 1109 * The Commtech adapters required the MPIOs to be driven low. The Exar in setup_gpio() 1166 PROPERTY_ENTRY_U32("exar,first-pin", 0), 1278 PROPERTY_ENTRY_U32("exar,first-pin", 10), 1311 * For SIMATIC IOT2000, only IOT2040 and its variants have the Exar device, 1401 * These Exar UARTs have an extra interrupt indicator that could fire for a [all …]
|
H A D | 8250_exar_st16c554.c | 39 MODULE_DESCRIPTION("8250 serial probe module for Exar cards");
|
H A D | Kconfig | 150 tristate "8250/16550 Exar/Commtech PCI/PCIe device support" 284 tristate "Support Exar ST16C554/554D Quad UART" 287 The Uplogix Envoy TU301 uses this Exar Quad UART. If you are
|
/linux/Documentation/devicetree/bindings/gpio/ |
H A D | gpio-xra1403.txt | 1 GPIO Driver for XRA1403 16-BIT GPIO Expander With Reset Input from EXAR 18 - compatible = "exar,xra1403". 35 compatible = "exar,xra1403";
|
H A D | gpio-exar.txt | 1 Exportable MPIO interface of Exar UART chips 4 - exar,first-pin: first exportable pins (0..15)
|
H A D | gpio-pca95xx.yaml | 24 - exar,xra1202
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | enumeration.rst | 597 Exar XR17V3521, soldered on the main board. This UART chip also includes 601 07:00.0 Serial controller: Exar Corp. XR17V3521 Dual PCIe UART (rev 03) 617 07:00.0 Serial controller: Exar Corp. XR17V3521 Dual PCIe UART (rev 03) <-- Exar 628 +-14.1-[05-09]----00.0-[06-09]--+-01.0-[07]----00.0 <-- Exar 634 To describe this Exar device on the PCI bus, we must start from the ACPI name 673 ACPI description for the Exar PCIe UART, also adding the list of its GPIO line 686 Device (EXAR) 721 dsdt.dsl table, whereas the device names "BRG1", "BRG2" and "EXAR" are 722 created analyzing the position of the Exar UART in the PCI bus topology.
|
/linux/drivers/watchdog/ |
H A D | exar_wdt.c | 4 * Exar/MaxLinear UART chips like the XR28V38x. 224 .identity = "Exar/MaxLinear XR28V38x Watchdog", 384 /* search for active Exar watchdogs on all possible locations */ in exar_wdt_init() 428 MODULE_DESCRIPTION("Exar/MaxLinear Watchdog Driver");
|
H A D | Kconfig | 1184 tristate "Exar Watchdog Timer" 1189 in some Exar/MaxLinear UART chips like the XR28V38x.
|
/linux/drivers/gpio/ |
H A D | gpio-xra1403.c | 3 * GPIO driver for EXAR XRA1403 16-bit GPIO expander 198 { .compatible = "exar,xra1403" }, 216 MODULE_DESCRIPTION("GPIO expander driver for EXAR XRA1403");
|
H A D | Kconfig | 291 on Exar XR17V352/354/358 chips. 1829 tristate "EXAR XRA1403 16-bit GPIO expander" 1832 GPIO driver for EXAR XRA1403 16-bit SPI-based GPIO expander.
|
H A D | Makefile | 65 obj-$(CONFIG_GPIO_EXAR) += gpio-exar.o
|
/linux/drivers/tty/serial/jsm/ |
H A D | jsm.h | 284 * These are the EXTENDED definitions for the Exar 654's Interrupt 327 u8 reserved1[0x2ff - 0x200]; /* U Reserved by Exar */ 329 u8 reserved2[0x37f - 0x340]; /* U Reserved by Exar */ 338 * Exar made them different than their earlier design. (XR16C854) 403 #define UART_17158_IER_RSVD1 0x10 /* Reserved by Exar */
|
/linux/include/uapi/linux/ |
H A D | serial_core.h | 24 #define PORT_XR17D15X 21 /* Exar XR17D15x UART */ 27 #define PORT_XR17V35X 24 /* Exar XR17V35x UARTs */
|
/linux/arch/arm/boot/dts/intel/ixp/ |
H A D | intel-ixp42x-arcom-vulcan.dts | 79 * 8250-compatible Exar XR16L2551 2 x UART 84 compatible = "exar,xr16l2551", "ns8250";
|
/linux/Documentation/devicetree/bindings/memory-controllers/ |
H A D | intel,ixp4xx-expansion-bus-controller.yaml | 97 compatible = "exar,xr16l2551", "ns8250";
|
/linux/drivers/usb/serial/ |
H A D | io_usbvend.h | 480 #define MANUF_UART_EXAR_654_EARLY 0 // Exar 16C654 in Edgeport/4s before 11/98 481 #define MANUF_UART_EXAR_654 1 // Exar 16C654 482 #define MANUF_UART_EXAR_2852 2 // Exar 16C2852
|
H A D | Kconfig | 638 tristate "USB MaxLinear/Exar USB to Serial driver" 640 Say Y here if you want to use MaxLinear/Exar USB to Serial converter
|
H A D | xr_serial.c | 3 * MaxLinear/Exar USB to Serial driver 1109 MODULE_DESCRIPTION("MaxLinear/Exar USB to Serial driver");
|
/linux/arch/arm/boot/dts/nxp/imx/ |
H A D | imx53-ppd.dts | 333 compatible = "exar,xra1403"; 341 compatible = "exar,xra1403";
|
/linux/arch/powerpc/kernel/ |
H A D | legacy_serial.c | 304 * EXAR ports and we default to the most common case. If your UART in add_legacy_pci_port()
|
/linux/Documentation/devicetree/bindings/ |
H A D | vendor-prefixes.yaml | 503 "^exar,.*": 504 description: Exar Corporation
|