| /freebsd/sys/contrib/device-tree/Bindings/serial/ |
| H A D | serial.yaml | 1 # 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 …]
|
| H A D | fsl-imx-uart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serial/fsl-im
[all...] |
| H A D | fsl-imx-uart.txt | 1 * Freescale i.MX Universal Asynchronous Receiver/Transmitter (UART)
4 - compatible : Should be "fsl,<soc>-uart"
5 - reg : Address and length of the register set for the device
6 - interrupts : Should contain uart interrupt
9 - fsl,dte-mode : Indicate the uart works in DTE mode. The uart works
11 - fsl,inverted-tx , fsl,inverted-rx : Indicate that the hardware attached
15 - rs485-rts-delay, rs485-rts-active-low, rs485-rx-during-tx,
16 linux,rs485-enabled-at-boot-time: see rs485.txt. Note that for RS485
17 you must enable either the "uart-has-rtscts" or the "rts-gpios"
18 properties. In case you use "uart-has-rtscts" the signal that controls
[all …]
|
| H A D | serial-peripheral-props.yaml | 1 # 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 <robh@kernel.org>
11 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
14 Devices connected over serial/UART, expressed as children of a serial
19 max-speed:
28 current-speed:
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | qualcomm-bluetooth.txt | 2 ---------------------
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 …]
|
| H A D | mediatek-bluetooth.txt | 1 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 …]
|
| H A D | broadcom-bluetooth.txt | 2 ---------------------
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 …]
|
| H A D | ti-bluetooth.txt | 2 ---------------------------------
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 …]
|
| H A D | ti,bluetooth.yaml | 1 # 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 …]
|
| H A D | broadcom-bluetooth.yaml | 1 # 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 - items:
19 - enum:
20 - infineon,cyw43439-bt
21 - const: brcm,bcm4329-bt
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/net/bluetooth/ |
| H A D | mediatek,bluetooth.txt | 1 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 …]
|
| H A D | nxp,88w8987-bt.yaml | 1 # 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 …]
|
| H A D | ti,bluetooth.yaml | 1 # 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 …]
|
| H A D | brcm,bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
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 - items:
19 - enum:
20 - infineon,cyw43439-bt
21 - const: brcm,bcm4329-bt
22 - enum:
[all …]
|
| /freebsd/share/man/man5/ |
| H A D | device.hints.5 | 2 .\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
88 .Bl -tag -width ".Li disabled" -compact -offset indent
90 specifies a bus to which the device is attached.
127 .Bl -tag -width ".Pa /sys/ Ns Ar ARCH Ns Pa /conf/GENERIC.hints" -compact
139 .Xr uart 4
141 .Bd -literal -offset indent
142 hint.uart.0.at="isa"
143 hint.uart.0.port="0x3F8"
144 hint.uart.0.flags="0x10"
145 hint.uart.0.irq="4"
[all …]
|
| /freebsd/sys/dev/uart/ |
| H A D | uart_if.m | 1 #-
33 #include <dev/uart/uart.h>
34 #include <dev/uart/uart_bus.h>
36 # The UART hardware interface. The core UART code is hardware independent.
37 # The details of the hardware are abstracted by the UART hardware interface.
39 INTERFACE uart;
52 # attach() - attach hardware.
53 # This method is called when the device is being attached. All resources
55 # high-level (ie tty) initialization has been done yet.
61 # detach() - detach hardware.
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | uart.4 | 1 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
32 .Nm uart
35 .Cd "device uart"
38 .Cd "device uart"
41 .Cd "device uart"
45 .Cd hint.uart.0.disabled="1"
46 .Cd hint.uart.0.baud="38400"
47 .Cd hint.uart.0.port="0x3f8"
48 .Cd hint.uart.0.flags="0x10"
[all …]
|
| H A D | gpio.4 | 34 .Bd -ragged -offset indent
44 .Bd -ragged -offset indent
60 .Bd -ragged -offset indent
69 .Bd -ragged -offset indent
75 .Li RISC-V
77 .Bd -ragged -offset indent
90 .Dq General-Purpose Input/Output.
114 attached to
117 .Bl -tag -width ".Va hint.driver.unit.pin_list"
121 where the device is attached.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/gnss/ |
| H A D | u-blox.txt | 1 u-blox GNSS Receiver DT binding
3 The u-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.
10 - compatible : Must be one of
12 "u-blox,neo-6m"
13 "u-blox,neo-8"
14 "u-blox,neo-m8"
16 - vcc-supply : Main voltage regulator
19 - reg : DDC (I2C) slave address
22 - reg : SPI chip select address
25 - reg : Number of the USB hub port or the USB host-controller port
[all …]
|
| H A D | u-blox,neo-6m.yaml | 1 # 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 <johan@kernel.org>
17 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.
22 - u-blox,neo-6m
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | google,cros-ec.yaml | 1 # 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 <bleung@chromium.org>
11 - Guenter Roeck <groeck@chromium.org>
22 - description:
24 const: google,cros-ec-i2c
25 - description:
27 const: google,cros-ec-spi
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/ptp/ |
| H A D | timestamper.txt | 3 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
|
| /freebsd/sys/contrib/edk2/Include/Protocol/ |
| H A D | DevicePath.h | 8 Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
9 SPDX-License-Identifier: BSD-2-Clause-Patent
29 /// Device Path guid definition for backward-compatible with EFI1.1.
56 UINT8 Length[2]; ///< Specific Device Path data. Type and Sub-Type define
62 /// Device Path protocol definition for backward-compatible with EFI1.1.
137 /// The Vendor Device Path allows the creation of vendor-defined Device Paths. A vendor must
144 /// Vendor-assigned GUID that defines the data that follows.
148 /// Vendor-defined variable size data.
200 /// Device's PnP hardware ID stored in a numeric 32-bit
201 /// compressed EISA-type ID. This value must match the
[all …]
|
| /freebsd/sys/dts/arm/ |
| H A D | imx53x.dtsi | 34 #address-cells = <1>;
35 #size-cells = <1>;
43 #address-cells = <1>;
44 #size-cells = <0>;
50 d-cache-line-size = <32>;
51 i-cache-line-size = <32>;
52 d-cache-size = <0x8000>;
53 i-cache-size = <0x8000>;
54 l2-cache-line-size = <32>;
55 l2-cache-line = <0x40000>;
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/bus/ |
| H A D | socionext,uniphier-system-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/bus/socionext,uniphier-system-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The UniPhier System Bus is an external bus that connects on-board devices to
11 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
16 within each bank to the CPU-viewed address. The needed setup includes the
21 - Masahiro Yamada <yamada.masahiro@socionext.com>
25 const: socionext,uniphier-system-bus
30 "#address-cells":
[all …]
|