Searched +full:serial +full:- +full:id (Results 1 – 25 of 325) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/sound/ |
| D | serial-midi.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 5 $id: http://devicetree.org/schemas/sound/serial-midi.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Generic Serial MIDI Interface 11 - Daniel Kaehn <kaehndan@gmail.com> 14 Generic MIDI interface using a serial device. This denotes that a serial device is 17 child node of a serial node. 20 parent serial device. If the standard MIDI baud of 31.25 kBaud is needed 22 configure the clocks of the parent serial device so that a requested baud of 38.4 kBaud [all …]
|
| D | fsl,audmix.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/fsl,audmix.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Shengjiu Wang <shengjiu.wang@nxp.com> 11 - Frank Li <Frank.Li@nxp.com> 14 The Audio Mixer is a on-chip functional module that allows mixing of two 15 audio streams into a single audio stream. Audio Mixer has two input serial 17 modules (SAI). Each input serial interface carries 8 audio channels in its 21 Audio Mixer is also a serial audio interface. Like input interfaces it has [all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | qcom,msm-uart.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/serial/qcom,msm-uart.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm MSM SoC Serial UART 10 - Bjorn Andersson <andersson@kernel.org> 11 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 14 The MSM serial UART hardware is designed for low-speed use cases where a 15 dma-engine isn't needed. From a software perspective it's mostly compatible 16 with the MSM serial UARTDM except that it only supports reading and writing [all …]
|
| D | arm,dcc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/arm,dcc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ARM DCC (Data communication channel) serial emulation 10 - Michal Simek <michal.simek@amd.com> 13 ARM DCC (Data communication channel) serial emulation interface available 14 via JTAG can be also used as one of serial line tightly coupled with every 22 - compatible 27 - | [all …]
|
| D | litex,liteuart.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 5 $id: http://devicetree.org/schemas/serial/litex,liteuart.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: LiteUART serial controller 11 - Karol Gugala <kgugala@antmicro.com> 12 - Mateusz Holenko <mholenko@antmicro.com> 15 LiteUART serial controller is a part of the LiteX FPGA SoC builder. It supports 16 multiple CPU architectures, currently including e.g. OpenRISC and RISC-V. 29 - compatible [all …]
|
| 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 …]
|
| D | maxim,max310x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/maxim,max310x.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Maxim MAX310X Advanced Universal Asynchronous Receiver-Transmitter (UART) 10 - Hugo Villeneuve <hvilleneuve@dimonoff.com> 15 - maxim,max3107 16 - maxim,max3108 17 - maxim,max3109 18 - maxim,max14830 [all …]
|
| D | sifive-serial.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/serial/sifive-serial.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: SiFive asynchronous serial interface (UART) 10 - Pragnesh Patel <pragnesh.patel@sifive.com> 11 - Paul Walmsley <paul.walmsley@sifive.com> 12 - Palmer Dabbelt <palmer@sifive.com> 15 - $ref: serial.yaml# 20 - enum: [all …]
|
| D | nuvoton,ma35d1-serial.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/nuvoton,ma35d1-serial.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Min-Jen Chen <mjchen@nuvoton.com> 11 - Jacky Huang <ychuang3@nuvoton.com> 14 - $ref: serial.yaml 18 const: nuvoton,ma35d1-uart 30 - compatible 31 - reg [all …]
|
| D | st,asc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/st,asc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: STMicroelectronics STi SoCs Serial Port 10 - Patrice Chotard <patrice.chotard@foss.st.com> 13 - $ref: serial.yaml# 28 st,hw-flow-ctrl: 32 st,force-m1: 33 description: When set, force asc to be in Mode-1. This is recommended for [all …]
|
| D | esp,esp32-acm.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 5 $id: http://devicetree.org/schemas/serial/esp,esp32-acm.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Max Filippov <jcmvbkbc@gmail.com> 14 Fixed function USB CDC-ACM gadget controller of the Espressif ESP32S3 SoC. 17 - $ref: serial.yaml# 21 const: esp,esp32s3-acm 30 - compatible 31 - reg [all …]
|
| D | qcom,serial-geni-qcom.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/serial/qcom,serial-geni-qcom.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Andy Gross <agross@kernel.org> 11 - Bjorn Andersson <bjorn.andersson@linaro.org> 14 - $ref: /schemas/serial/serial.yaml# 19 - qcom,geni-uart 20 - qcom,geni-debug-uart 25 clock-names: [all …]
|
| D | via,vt8500-uart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/serial/via,vt8500-uart.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Alexey Charkov <alchark@gmail.com> 14 - $ref: serial.yaml 19 - via,vt8500-uart # up to WM8850/WM8950 20 - wm,wm8880-uart # for WM8880 and later 32 - compatible 33 - clocks [all …]
|
| D | brcm,bcm6345-uart.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/serial/brcm,bcm6345-uart.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rafał Miłecki <rafal@milecki.pl> 13 - $ref: serial.yaml# 17 const: brcm,bcm6345-uart 28 clock-names: 34 - reg 35 - interrupts [all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 7 The ``devlink-info`` mechanism enables device drivers to report device 10 The original motivation for the ``devlink-info`` API was twofold: 12 - making it possible to automate device and firmware management in a fleet 13 of machines in a vendor-independent fashion (see also 14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`); 15 - name the per component FW versions (as opposed to the crowded ethtool 18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver 19 versions is generally discouraged - here, and via any other Linux API. 21 .. list-table:: List of top level info objects [all …]
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 6 platform bus: platform_device, and platform_driver. This pseudo-bus 8 like those used to integrate peripherals on many system-on-chip 16 entities in the system. This includes legacy port-based devices and 18 into system-on-chip platforms. What they usually have in common 28 u32 id; 62 Or, in common situations where the device is known not to be hot-pluggable, 86 As a rule, platform specific (and often board-specific) setup code will 102 a kernel for a specific target board. Such board-specific kernels are 113 calls to clk_get(&pdev->dev, clock_name) return them as needed. 119 on a non-driver role: the driver registers its platform device, rather than [all …]
|
| /Documentation/usb/ |
| D | usb-serial.rst | 2 USB serial 8 The USB serial driver currently supports a number of different USB to 9 serial converter products, as well as some devices that use a serial 19 Currently the driver can handle up to 256 different serial interfaces at 45 -------------------------------------- 58 ----------------------------------------------- 72 This goes against the current documentation for pilot-xfer and other 77 (this is usually /dev/ttyUSB1 if you do not have any other usb-serial 99 Kroah-Hartman at greg@kroah.com 103 ------------------- [all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | marvell,88w8897.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/bluetooth/marvell,88w8897.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 This documents the binding structure and common properties for serial 14 - Rob Herring <robh@kernel.org> 19 - mrvl,88w8897 20 - mrvl,88w8997 22 max-speed: true 25 - compatible [all …]
|
| D | mediatek,mt7622-bluetooth.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7622-bluetooth.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MediaTek SoC built-in Bluetooth 10 This device is a serial attached device to BTIF device and thus it must be a 11 child node of the serial node with BTIF. The dt-bindings details for BTIF 12 device can be known via Documentation/devicetree/bindings/serial/8250.yaml. 15 - Sean Wang <sean.wang@mediatek.com> 18 - $ref: bluetooth-controller.yaml# [all …]
|
| D | ti,bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/bluetooth/ti,bluetooth.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - David Lechner <david@lechnology.com> 13 This documents the binding structure and common properties for serial 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 …]
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr5.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr5.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LPDDR5 SDRAM compliant to JEDEC JESD209-5 10 - Krzysztof Kozlowski <krzk@kernel.org> 13 - $ref: jedec,lpddr-props.yaml# 18 - pattern: "^lpddr5-[0-9a-f]{2},[0-9a-f]{4}$" 19 - const: jedec,lpddr5 21 serial-id: [all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,geni-se.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/qcom/qcom,geni-se.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: GENI Serial Engine QUP Wrapper Controller 10 - Bjorn Andersson <bjorn.andersson@linaro.org> 14 is a programmable module for supporting a wide range of serial interfaces 15 like UART, SPI, I2C, I3C, etc. A single QUP module can provide upto 8 Serial 16 Interfaces, using its internal Serial Engines. The GENI Serial Engine QUP 18 representing a serial engine. [all …]
|
| /Documentation/devicetree/bindings/fpga/ |
| D | xlnx,fpga-slave-serial.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/fpga/xlnx,fpga-slave-serial.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Xilinx Slave Serial SPI FPGA 10 - Nava kishore Manne <nava.kishore.manne@amd.com> 13 Xilinx Spartan-6 and 7 Series FPGAs support a method of loading the bitstream 14 over what is referred to as slave serial interface.The slave serial link is 21 https://www.xilinx.com/support/documentation/application_notes/xapp583-fpga-configuration.pdf 24 - $ref: /schemas/spi/spi-peripheral-props.yaml# [all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | kontron,sl28-vpd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: NVMEM layout of the Kontron SMARC-sAL28 vital product data 10 - Michael Walle <michael@walle.cc> 13 The vital product data (VPD) of the sl28 boards contains a serial 15 on-board ethernet devices are derived from this base MAC address by 22 const: kontron,sl28-vpd 24 serial-number: [all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | stih407-c8sectpfe.txt | 14 - compatible : Should be "stih407-c8sectpfe" 16 - reg : Address and length of register sets for each device in 17 "reg-names" 19 - reg-names : The names of the register addresses corresponding to the 21 - c8sectpfe: c8sectpfe registers 22 - c8sectpfe-ram: c8sectpfe internal sram 24 - clocks : phandle list of c8sectpfe clocks 25 - clock-names : should be "c8sectpfe" 26 See: Documentation/devicetree/bindings/clock/clock-bindings.txt 28 - pinctrl-names : a pinctrl state named tsin%d-serial or tsin%d-parallel (where %d is tsin-num) [all …]
|
12345678910>>...13