Home
last modified time | relevance | path

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

12345

/kernel/linux/linux-5.10/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 <robh@kernel.org>
11 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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
26 cts-gpios:
30 the UART's CTS line.
32 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 <fabio.estevam@nxp.com>
13 - $ref: "serial.yaml"
14 - $ref: "rs485.yaml"
19 - const: fsl,imx1-uart
20 - const: fsl,imx21-uart
[all …]
/kernel/linux/linux-6.6/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 <robh@kernel.org>
11 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 <festevam@gmail.com>
13 - $ref: serial.yaml#
14 - $ref: rs485.yaml#
19 - const: fsl,imx1-uart
20 - const: fsl,imx21-uart
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/drivers/extcon/
Dextcon-max8997.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max8997.c - MAX8997 extcon driver to support MAX8997 MUIC
17 #include <linux/mfd/max8997-private.h>
18 #include <linux/extcon-provider.h>
21 #define DEV_NAME "max8997-muic"
38 { MAX8997_MUICIRQ_ADCError, "muic-ADCERROR" },
39 { MAX8997_MUICIRQ_ADCLow, "muic-ADCLOW" },
40 { MAX8997_MUICIRQ_ADC, "muic-ADC" },
41 { MAX8997_MUICIRQ_VBVolt, "muic-VBVOLT" },
42 { MAX8997_MUICIRQ_DBChg, "muic-DBCHG" },
[all …]
Dextcon-max77693.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max77693.c - MAX77693 extcon driver to support MAX77693 MUIC
17 #include <linux/mfd/max77693-common.h>
18 #include <linux/mfd/max77693-private.h>
19 #include <linux/extcon-provider.h>
23 #define DEV_NAME "max77693-muic"
29 * extcon-max77693 driver use 'default_init_data' to bring up base operation
34 /* STATUS2 - [3]ChgDetRun */
38 /* INTMASK1 - Unmask [3]ADC1KM,[0]ADCM */
43 /* INTMASK2 - Unmask [0]ChgTypM */
[all …]
Dextcon-max14577.c1 // SPDX-License-Identifier: GPL-2.0+
3 // extcon-max14577.c - MAX14577/77836 extcon driver to support MUIC
15 #include <linux/mfd/max14577-private.h>
16 #include <linux/extcon-provider.h>
46 { MAX14577_IRQ_INT1_ADC, "muic-ADC" },
47 { MAX14577_IRQ_INT1_ADCLOW, "muic-ADCLOW" },
48 { MAX14577_IRQ_INT1_ADCERR, "muic-ADCError" },
49 { MAX14577_IRQ_INT2_CHGTYP, "muic-CHGTYP" },
50 { MAX14577_IRQ_INT2_CHGDETRUN, "muic-CHGDETRUN" },
51 { MAX14577_IRQ_INT2_DCDTMR, "muic-DCDTMR" },
[all …]
/kernel/linux/linux-6.6/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.
/kernel/linux/linux-5.10/drivers/tty/serial/8250/
D8250_gsc.c1 // SPDX-License-Identifier: GPL-2.0+
5 * (c) Copyright Matthew Wilcox <willy@debian.org> 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 …]
/kernel/linux/linux-6.6/drivers/tty/serial/8250/
D8250_parisc.c1 // SPDX-License-Identifier: GPL-2.0+
5 * (c) Copyright Matthew Wilcox <willy@debian.org> 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dmediatek-bluetooth.txt1 MediaTek SoC built-in Bluetooth Devices
4 This device is a serial attached device to BTIF device and thus it must be a
5 child node of the serial node with BTIF. The dt-bindings details for BTIF
10 - compatible: Must be
11 "mediatek,mt7622-bluetooth": for MT7622 SoC
12 - clocks: Should be the clock specifiers corresponding to the entry in
13 clock-names property.
14 - clock-names: Should contain "ref" entries.
15 - power-domains: Phandle to the power domain that the device is part of
20 compatible = "mediatek,mt7622-btif",
[all …]
Dqualcomm-bluetooth.txt2 ---------------------
5 attached Qualcomm devices.
7 Serial attached Qualcomm devices shall be a child node of the host UART
8 device the slave device is attached to.
11 - compatible: should contain one of the following:
12 * "qcom,qca6174-bt"
13 * "qcom,qca9377-bt"
14 * "qcom,wcn3990-bt"
15 * "qcom,wcn3991-bt"
16 * "qcom,wcn3998-bt"
[all …]
Dbroadcom-bluetooth.txt2 ---------------------
5 attached Broadcom devices.
7 Serial attached Broadcom devices shall be a child node of the host UART
8 device the slave device is attached to.
12 - compatible: should contain one of the following:
14 * "brcm,bcm4329-bt"
15 * "brcm,bcm4330-bt"
16 * "brcm,bcm43438-bt"
18 * "brcm,bcm43540-bt"
23 - max-speed: see Documentation/devicetree/bindings/serial/serial.yaml
[all …]
Dti-bluetooth.txt2 ---------------------------------
5 attached TI Bluetooth devices. The following chips are included in this
11 TI WiLink devices have a UART interface for providing Bluetooth, FM radio,
18 This bindings follows the UART slave device binding in ../serial/serial.yaml.
21 - compatible: should be one of the following:
23 "ti,wl1271-st"
24 "ti,wl1273-st"
25 "ti,wl1281-st"
26 "ti,wl1283-st"
27 "ti,wl1285-st"
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/
Dmediatek-bluetooth.txt1 MediaTek SoC built-in Bluetooth Devices
4 This device is a serial attached device to BTIF device and thus it must be a
5 child node of the serial node with BTIF. The dt-bindings details for BTIF
10 - compatible: Must be
11 "mediatek,mt7622-bluetooth": for MT7622 SoC
12 - clocks: Should be the clock specifiers corresponding to the entry in
13 clock-names property.
14 - clock-names: Should contain "ref" entries.
15 - power-domains: Phandle to the power domain that the device is part of
20 compatible = "mediatek,mt7622-btif",
[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 <david@lechnology.com>
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 …]
Dbroadcom-bluetooth.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/broadcom-bluetooth.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 This binding describes Broadcom UART-attached bluetooth chips.
18 - brcm,bcm20702a1
19 - brcm,bcm4329-bt
20 - brcm,bcm4330-bt
21 - brcm,bcm4334-bt
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/bluetooth/
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 <neeraj.sanjaykale@nxp.com>
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/arch/arm/mach-s3c/
Ddma-s3c24xx.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2003-2006 Simtec Electronics
16 * can be attached to any DMA source. We therefore let the DMA core handle
39 DMACH_UART0_SRC2, /* s3c2412 second uart sources */
42 DMACH_UART3, /* s3c2443 has extra uart */
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/drivers/bluetooth/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
105 tristate "HCI UART driver"
110 Bluetooth HCI UART driver.
113 UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card
116 Say Y here to compile support for Bluetooth UART devices into the
125 bool "UART (H4) protocol support"
128 UART (H4) is serial protocol for communication between Bluetooth
130 with UART interface, including PCMCIA and CF cards.
132 Say Y here to compile support for HCI UART (H4) protocol.
135 tristate "UART Nokia H4+ protocol support"
[all …]

12345