Home
last modified time | relevance | path

Searched +full:uart +full:- +full:attached (Results 1 – 25 of 71) sorted by relevance

123

/linux-6.14.4/Documentation/devicetree/bindings/serial/
Dserial.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <[email protected]>
11 - Greg Kroah-Hartman <[email protected]>
18 Each enabled UART may have an optional "serialN" alias in the "aliases" node,
19 where N is the port number (non-negative decimal integer) as printed on the
28 cts-gpios:
32 the UART's CTS line.
34 dcd-gpios:
[all …]
Dfsl-imx-uart.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serial/fsl-imx-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX Universal Asynchronous Receiver/Transmitter (UART)
10 - Fabio Estevam <[email protected]>
15 - const: fsl,imx1-uart
16 - const: fsl,imx21-uart
17 - items:
18 - enum:
[all …]
Dserial-peripheral-props.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/serial/serial-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common Properties for Serial-attached Devices
10 - Rob Herring <[email protected]>
11 - Greg Kroah-Hartman <[email protected]>
14 Devices connected over serial/UART, expressed as children of a serial
19 max-speed:
28 current-speed:
[all …]
/linux-6.14.4/tools/arch/x86/dell-uart-backlight-emulator/
DREADME1 Emulator for DELL0501 UART attached backlight controller
2 --------------------------------------------------------
5 board connected to an UART.
7 In DSDT this uart port will be defined as:
12 With the DELL0501 indicating that we are dealing with an UART with
13 the backlight controller board attached.
16 the drivers/platform/x86/dell/dell-uart-backlight.c driver without access
20 1. A (desktop) PC with a 16550 UART on the motherboard and a standard DB9
21 connector connected to this UART.
25 4. A DSDT overlay for the desktop PC replacing the _HID of the 16550 UART
[all …]
/linux-6.14.4/drivers/extcon/
Dextcon-max8997.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max8997.c - MAX8997 extcon driver to support MAX8997 MUIC
8 #include <linux/devm-helpers.h>
18 #include <linux/mfd/max8997-private.h>
19 #include <linux/extcon-provider.h>
22 #define DEV_NAME "max8997-muic"
39 { MAX8997_MUICIRQ_ADCError, "muic-ADCERROR" },
40 { MAX8997_MUICIRQ_ADCLow, "muic-ADCLOW" },
41 { MAX8997_MUICIRQ_ADC, "muic-ADC" },
42 { MAX8997_MUICIRQ_VBVolt, "muic-VBVOLT" },
[all …]
Dextcon-max77693.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max77693.c - MAX77693 extcon driver to support MAX77693 MUIC
8 #include <linux/devm-helpers.h>
18 #include <linux/mfd/max77693-common.h>
19 #include <linux/mfd/max77693-private.h>
20 #include <linux/extcon-provider.h>
24 #define DEV_NAME "max77693-muic"
30 * extcon-max77693 driver use 'default_init_data' to bring up base operation
35 /* STATUS2 - [3]ChgDetRun */
39 /* INTMASK1 - Unmask [3]ADC1KM,[0]ADCM */
[all …]
Dextcon-max14577.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max14577.c - MAX14577/77836 extcon driver to support MUIC
9 #include <linux/devm-helpers.h>
16 #include <linux/mfd/max14577-private.h>
17 #include <linux/extcon-provider.h>
47 { MAX14577_IRQ_INT1_ADC, "muic-ADC" },
48 { MAX14577_IRQ_INT1_ADCLOW, "muic-ADCLOW" },
49 { MAX14577_IRQ_INT1_ADCERR, "muic-ADCError" },
50 { MAX14577_IRQ_INT2_CHGTYP, "muic-CHGTYP" },
51 { MAX14577_IRQ_INT2_CHGDETRUN, "muic-CHGDETRUN" },
[all …]
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
9 cables attached. For example, an external connector of a device
11 host USB ports. Many of 30-pin connectors including PDMI are
25 tristate "X-Power AXP288 EXTCON support"
30 and USB MUX switching by X-Power AXP288 PMIC.
42 and UART data to use a common connector port.
87 microphone and UART data to use a common connector port.
105 enable a system with an integrated USB OTG dual-role transceiver to
106 function as an USB OTG dual-role device.
195 using Chrome OS EC based USB Type-C ports.
[all …]
/linux-6.14.4/drivers/iio/imu/bno055/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
9 tristate "Bosch BNO055 attached via UART"
14 Enable this to support Bosch BNO055 IMUs attached via UART.
20 tristate "Bosch BNO055 attached via I2C bus"
25 Enable this to support Bosch BNO055 IMUs attached via I2C bus.
/linux-6.14.4/drivers/tty/serial/8250/
D8250_parisc.c1 // SPDX-License-Identifier: GPL-2.0+
5 * (c) Copyright Matthew Wilcox <[email protected]> 2001-2002
18 #include <asm/parisc-device.h>
25 struct uart_8250_port uart; in serial_init_chip() local
30 if (!dev->irq && (dev->id.sversion == 0xad)) in serial_init_chip()
31 dev->irq = iosapic_serial_irq(dev); in serial_init_chip()
34 if (!dev->irq) { in serial_init_chip()
40 if (parisc_parent(dev)->id.hw_type != HPHW_IOA) in serial_init_chip()
41 dev_info(&dev->dev, in serial_init_chip()
44 (unsigned long long)dev->hpa.start); in serial_init_chip()
[all …]
D8250_platform.c1 // SPDX-License-Identifier: GPL-2.0+
3 * Universal/legacy platform driver for 8250/16550-type serial ports
6 * ISA-compatible 8250/16550 ports
30 * This option is unsafe when used on edge-triggered interrupts.
41 * SERIAL_PORT_DFNS tells us about built-in ports that have no
84 struct uart_port *port = &up->port; in __serial8250_isa_init_ports()
86 port->iobase = old_serial_port[i].port; in __serial8250_isa_init_ports()
87 port->irq = irq_canonicalize(old_serial_port[i].irq); in __serial8250_isa_init_ports()
88 port->irqflags = 0; in __serial8250_isa_init_ports()
89 port->uartclk = old_serial_port[i].baud_base * 16; in __serial8250_isa_init_ports()
[all …]
/linux-6.14.4/drivers/platform/x86/
Dserdev_helpers.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * In some cases UART attached devices which require an in kernel driver,
4 * e.g. UART attached Bluetooth HCIs are described in the ACPI tables
7 * This causes the kernel to create a /dev/ttyS# char-device for the UART
8 * instead of creating an in kernel serdev-controller + serdev-device pair
12 * create a serdev-controller device for these UARTs instead of a /dev/ttyS#.
14 * Instantiating the actual serdev-device to bind to is up to pdx86 code,
15 * this header provides a helper for getting the serdev-controller device.
33 /* Walk host -> uart-ctrl -> port -> serdev-ctrl */ in get_serdev_controller_from_parent()
52 return ERR_PTR(-ENODEV); in get_serdev_controller_from_parent()
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/net/bluetooth/
Dmediatek,bluetooth.txt1 MediaTek UART based Bluetooth Devices
4 This device is a serial attached device to UART device and thus it must be a
5 child node of the serial node with UART.
13 - compatible: Must be
14 "mediatek,mt7663u-bluetooth": for MT7663U device
15 "mediatek,mt7668u-bluetooth": for MT7668U device
16 - vcc-supply: Main voltage regulator
21 - pinctrl-names: Should be "default", "runtime"
22 - pinctrl-0: Should contain UART RXD low when the device is powered up to
24 - pinctrl-1: Should contain UART mode pin ctrl
[all …]
Dnxp,88w8987-bt.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/bluetooth/nxp,88w8987-bt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This binding describes UART-attached NXP bluetooth chips. These chips
11 are dual-radio chips supporting WiFi and Bluetooth. The bluetooth
12 works on standard H4 protocol over 4-wire UART. The RTS and CTS lines
14 asserts break signal over UART-TX line to put the chip into power save
15 state. De-asserting break wakes up the BT chip.
18 - Neeraj Sanjay Kale <[email protected]>
[all …]
Dti,bluetooth.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - David Lechner <[email protected]>
14 attached TI Bluetooth devices. The following chips are included in this
20 TI WiLink devices have a UART interface for providing Bluetooth, FM radio,
27 This bindings follows the UART slave device binding in ../serial/serial.yaml.
32 - ti,cc2560
33 - ti,wl1271-st
34 - ti,wl1273-st
[all …]
Dbrcm,bluetooth.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <[email protected]>
13 This binding describes Broadcom UART-attached bluetooth chips.
18 - items:
19 - enum:
20 - infineon,cyw43439-bt
21 - const: brcm,bcm4329-bt
22 - enum:
[all …]
/linux-6.14.4/drivers/platform/chrome/
Dcros_ec_uart.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * UART interface for ChromeOS Embedded Controller
5 * Copyright 2020-2022 Google LLC.
23 * EC sends contiguous bytes of response packet on UART AP RX.
40 * struct response_info - Encapsulate EC response related
51 * @status: Re-init to 0 before sending a cmd. Updated to 1 when
67 * struct cros_ec_uart - information about a uart-connected EC
69 * @serdev: serdev uart device we are connected to.
70 * @baudrate: UART baudrate of attached EC device.
71 * @flowcontrol: UART flowcontrol of attached device.
[all …]
/linux-6.14.4/Documentation/networking/device_drivers/can/
Dcan327.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
7 --------
14 -----------
26 -------------
33 order to fake full-duplex operation.
36 enough to implement simple request-response protocols (such as OBD II),
39 Most ELM327s come as nondescript serial devices, attached via USB or
50 -----------
59 ----------------------------------
65 be attached on a command prompt as follows::
[all …]
/linux-6.14.4/arch/arm64/boot/dts/freescale/
Dimx8mp-dhcom-drc02.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
6 * DHCM-iMX8ML8-C160-R204-F1638-SPI16-E2-CAN2-RTC-I-01D2
7 * DHCOM PCB number: 660-100 or newer
8 * DRC02 PCB number: 568-100 or newer
11 /dts-v1/;
13 #include <dt-bindings/leds/common.h>
14 #include <dt-bindings/phy/phy-imx8-pcie.h>
15 #include "imx8mp-dhcom-som.dtsi"
19 compatible = "dh,imx8mp-dhcom-drc02", "dh,imx8mp-dhcom-som",
23 stdout-path = &uart1;
[all …]
/linux-6.14.4/drivers/bluetooth/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
117 tristate "HCI UART driver"
123 Bluetooth HCI UART driver.
126 UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card
129 Say Y here to compile support for Bluetooth UART devices into the
138 bool "UART (H4) protocol support"
141 UART (H4) is serial protocol for communication between Bluetooth
143 with UART interface, including PCMCIA and CF cards.
145 Say Y here to compile support for HCI UART (H4) protocol.
148 tristate "UART Nokia H4+ protocol support"
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/ptp/
Dtimestamper.txt3 This binding supports non-PHY devices that snoop the MII bus and
9 Non-PHY MII time stamping drivers typically talk to the control
10 interface over another bus like I2C, SPI, UART, or via a memory mapped
20 compatible = "ines,ptp-ctrl";
26 ethernet-phy@1 {
34 ethernet-phy@2 {
40 In this example, time stamps from the MII bus attached to phy@1 will
/linux-6.14.4/drivers/gpio/
Dgpio-exar.c1 // SPDX-License-Identifier: GPL-2.0-only
25 * The Device Configuration and UART Configuration Registers
26 * for each UART channel take 1KB of memory address space.
50 unsigned int pin = exar_gpio->first_pin + (offset % 16); in exar_offset_to_sel_addr()
54 return addr + (cascaded ? exar_gpio->cascaded_offset : 0); in exar_offset_to_sel_addr()
60 unsigned int pin = exar_gpio->first_pin + (offset % 16); in exar_offset_to_lvl_addr()
64 return addr + (cascaded ? exar_gpio->cascaded_offset : 0); in exar_offset_to_lvl_addr()
70 unsigned int pin = exar_gpio->first_pin + (offset % 16); in exar_offset_to_bit()
81 if (regmap_test_bits(exar_gpio->regmap, addr, BIT(bit))) in exar_get_direction()
93 return !!(regmap_test_bits(exar_gpio->regmap, addr, BIT(bit))); in exar_get_value()
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/google,cros-ec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benson Leung <[email protected]>
11 - Guenter Roeck <[email protected]>
22 - description:
24 const: google,cros-ec-i2c
25 - description:
27 const: google,cros-ec-spi
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/gnss/
Du-blox,neo-6m.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/gnss/u-blox,neo-6m.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-blox GNSS Receiver
10 - $ref: gnss-common.yaml#
11 - $ref: /schemas/serial/serial-peripheral-props.yaml#
14 - Johan Hovold <[email protected]>
17 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.
22 - u-blox,neo-6m
[all …]
/linux-6.14.4/Documentation/trace/coresight/
Dcoresight-ect.rst1 .. SPDX-License-Identifier: GPL-2.0
11 --------------------
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
27 # #<-----------: : +---# ETR #
31 channels. When an input trigger becomes active, the attached channel will
32 become active. Any output trigger attached to that channel will also
[all …]

123