Searched +full:usb +full:- +full:to +full:- +full:serial (Results 1 – 25 of 88) sorted by relevance
1234
| /Documentation/usb/ |
| D | gadget_serial.rst | 2 Linux Gadget Serial Driver v2.0
7 (updated 8-May-2008 for v2.3)
11 ----------------------
23 License along with this program; if not, write to the Free
25 MA 02111-1307 USA.
27 This document and the gadget serial driver itself are
35 -------------
36 Versions of the gadget serial driver are available for the
38 version 2.3 or later of the gadget serial driver in a 2.6
42 Windows and know how to configure and build Linux kernels, run
[all …]
|
| 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
10 interface from userspace to talk to the device.
19 Currently the driver can handle up to 256 different serial interfaces at
22 The major number that the driver uses is 188 so to use the driver,
36 will print to the system log, which node(s) the device has been bound
37 to.
45 --------------------------------------
48 device, including providing a unit to test with.
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic USB Controller
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
16 pattern: "^usb(@.*)?"
20 List of all the USB PHYs on this HCD
22 phy-names:
24 Name specifier for the USB PHY
[all …]
|
| D | fsl-usb.txt | 1 Freescale SOC USB controllers
3 The device node for a USB controller that is part of a Freescale
5 Practice : Universal Serial Bus" with the following modifications
9 - compatible : Should be "fsl-usb2-mph" for multi port host USB
10 controllers, or "fsl-usb2-dr" for dual role USB controllers
11 or "fsl,mpc5121-usb2-dr" for dual role USB controllers of MPC5121.
12 Wherever applicable, the IP version of the USB controller should
13 also be mentioned (for eg. fsl-usb2-dr-v2.2 for bsc9132).
14 - phy_type : For multi port host USB controllers, should be one of
15 "ulpi", or "serial". For dual role USB controllers, should be
[all …]
|
| D | aspeed,usb-vhub.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/usb/aspeed,usb-vhub.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: ASPEED USB 2.0 Virtual Hub Controller
11 - Benjamin Herrenschmidt <benh@kernel.crashing.org>
14 The ASPEED USB 2.0 Virtual Hub Controller implements 1 set of USB Hub
15 register and several sets of Device and Endpoint registers to support
16 the Virtual Hub's downstream USB devices.
26 - aspeed,ast2400-usb-vhub
[all …]
|
| D | usb251xb.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/usb/usb251xb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip USB 2.0 Hi-Speed Hub Controller
10 - Richard Leitner <richard.leitner@skidata.com>
15 - microchip,usb2422
16 - microchip,usb2512b
17 - microchip,usb2512bi
18 - microchip,usb2513b
[all …]
|
| D | nvidia,tegra20-ehci.txt | 1 Tegra SOC USB controllers
3 The device node for a USB controller that is part of a Tegra
5 Practice : Universal Serial Bus" with the following modifications
9 - compatible : For Tegra20, must contain "nvidia,tegra20-ehci".
10 For Tegra30, must contain "nvidia,tegra30-ehci". Otherwise, must contain
11 "nvidia,<chip>-ehci" plus at least one of the above, where <chip> is
13 - nvidia,phy : phandle of the PHY that the controller is connected to.
14 - clocks : Must contain one entry, for the module clock.
15 See ../clocks/clock-bindings.txt for details.
16 - resets : Must contain an entry for each entry in reset-names.
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LEDs connected to Broadcom BCM6328 controller
10 - Álvaro Fernández Rojas <noltari@gmail.com>
14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
15 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
17 as spi-gpio. See
20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
[all …]
|
| /Documentation/driver-api/tty/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Teletypewriter (TTY) layer takes care of all those serial devices. Including
16 contains a reference to operations which could be performed on the TTYs. It is
23 short ldisc; in C, struct tty_ldisc_ops). Its task is to transform characters
26 processing, and more. The transformed characters are passed further to
29 In-detail description of the named TTY structures is in separate documents:
45 :doc:`Serial <../serial/driver>` and :doc:`USB Serial <../../usb/usb-serial>`
46 layers first. Drivers for serial devices can often use one of these specific
47 layers to implement a serial driver. Only special devices should be handled
48 directly by the TTY Layer. If you are about to write such a driver, read on.
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | xilinx.txt | 5 of standard device types (network, serial, etc.) and miscellaneous
10 Each IP-core has a set of parameters which the FPGA designer can use to
12 extract the device parameters relevant to device drivers and copy them
15 to be recompiled every time the FPGA bitstream is resynthesized.
17 The new approach is to export the parameters into the device tree and
19 parameters which used to be exported as #defines will now become
20 properties of the device node. In general, device nodes for IP-cores
23 (name): (generic-name)@(base-address) {
24 compatible = "xlnx,(ip-core-name)-(HW_VER)"
27 interrupt-parent = <&interrupt-controller-phandle>;
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | stericsson,dma40.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DMA40 DMA Engine
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: dma-controller.yaml#
16 "#dma-cells":
20 table for DB8500 which is the only ASIC known to use DMA40:
30 8: Synchronous Serial Port SSP0
31 9: Synchronous Serial Port SSP1
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-peak_usb | 5 Contact: Stephane Grosjean <s.grosjean@peak-system.com>
7 PEAK PCAN-USB devices support user-configurable CAN channel
8 identifiers. Contrary to a USB serial number, these identifiers
10 if a USB device exports multiple CAN interfaces, each of them
12 This attribute provides read-only access to the currently
18 set to zero.
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 5 xHCI compatible USB host controllers (i.e. super-speed
8 is fully compliant with the USB framework and provides
9 the equivalent of a very high performance full-duplex
10 serial link for debug purpose.
14 to the Debug Capability. Otherwise, it will be assigned
15 to xHCI.
17 Writing "enable" to this attribute will enable the DbC
19 to the DbC device. Writing "disable" to this attribute
21 port will roll back to the xHCI.
32 presented in the USB device descriptor by this xhci debug
[all …]
|
| D | sysfs-bus-usb | 1 What: /sys/bus/usb/devices/<INTERFACE>/authorized
4 This allows to authorize (1) or deauthorize (0)
6 in contrast to the device authorization.
9 by writing INTERFACE to /sys/bus/usb/drivers_probe
10 This allows to avoid side-effects with drivers
15 What: /sys/bus/usb/devices/usbX/interface_authorized_default
22 What: /sys/bus/usb/device/.../authorized
28 drivers, non-authorized one are not. By default, wired
29 USB devices are authorized.
31 What: /sys/bus/usb/drivers/.../new_id
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 14 debug port, you need to::
19 3) have a USB 3.0 super-speed A-to-A debugging cable.
30 super-speed port). The debug device is fully compliant with
31 the USB framework and provides the equivalent of a very high
32 performance full-duplex serial link between the debug target
38 DbC has been designed to log early printk messages. One use for
41 Other uses include simpler, lockless logging instead of a full-
44 On the debug target system, you need to customize a debugging
51 append a host controller index to this kernel parameter. This
56 USB subsystem by adding below kernel boot parameter::
[all …]
|
| D | persist.rst | 1 .. _usb-persist:
3 USB device persistence during system suspend
13 According to the USB specification, when a USB bus is suspended the
14 bus must continue to supply suspend current (around 1-5 mA). This
16 detect connect-change events (devices being plugged in or unplugged).
19 If a USB device's power session is interrupted then the system is
20 required to behave as though the device has been unplugged. It's a
22 has no way to know what has actually happened. Perhaps the same
26 By default, Linux behaves according to the spec. If a USB host
28 wakes up all the devices attached to that controller are treated as
[all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
16 11 = /dev/kmsg Writes to this come out as printk's, reads
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
27 /dev/initrd refers to a RAM disk which was preloaded
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
[all …]
|
| /Documentation/arch/arm/sa1100/ |
| D | cerf.rst | 7 The Intrinsyc CerfBoard is a StrongARM 1110-based computer on a board
9 controller, an RS232-compatible serial port, a USB function port, and
19 - CompactFlash+ slot (select PCMCIA in General Setup and any options
21 - Onboard Crystal CS8900 Ethernet controller (Cerf CS8900A support in
23 - Serial ports with a serial console (hardcoded to 38400 8N1)
25 In order to get this kernel onto your Cerf, you need a server that runs
27 evaluation kit on how to use the bootloader. This series of commands
30 make ARCH=arm CROSS_COMPILE=arm-linux- cerfcube_defconfig
31 make ARCH=arm CROSS_COMPILE=arm-linux- zImage
32 make ARCH=arm CROSS_COMPILE=arm-linux- modules
|
| /Documentation/devicetree/bindings/gnss/ |
| 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#
13 - Johan Hovold <johan@kernel.org>
16 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.
21 - u-blox,neo-6m
22 - u-blox,neo-8
[all …]
|
| /Documentation/arch/arm/stm32/ |
| D | stm32mp13-overview.rst | 6 ------------
8 The STM32MP131/STM32MP133/STM32MP135 are Cortex-A MPU aimed at various applications.
11 - One Cortex-A7 application core
12 - Standard memories interface support
13 - Standard connectivity, widely inherited from the STM32 MCU family
14 - Comprehensive security support
18 - Cortex-A7 core running up to @900MHz
19 - FMC controller to connect SDRAM, NOR and NAND memories
20 - QSPI
21 - SD/MMC/SDIO support
[all …]
|
| D | stm32mp151-overview.rst | 6 ------------
8 The STM32MP151 is a Cortex-A MPU aimed at various applications.
11 - Single Cortex-A7 application core
12 - Standard memories interface support
13 - Standard connectivity, widely inherited from the STM32 MCU family
14 - Comprehensive security support
18 - Cortex-A7 core running up to @800MHz
19 - FMC controller to connect SDRAM, NOR and NAND memories
20 - QSPI
21 - SD/MMC/SDIO support
[all …]
|
| /Documentation/driver-api/ |
| D | pps.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PPS - Pulse Per Second
22 --------
24 LinuxPPS provides a programming interface (API) to define in the
29 can use it to adjust system clock time.
31 A PPS source can be connected to a serial port (usually to the Data
32 Carrier Detect pin) or to a parallel port (ACK-pin) or to a special
34 case when a new pulse arrives the system must apply to it a timestamp
38 GPS receiver as PPS source, to obtain a wallclock-time with
39 sub-millisecond synchronisation to UTC.
[all …]
|
| /Documentation/networking/ |
| D | cdc_mbim.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems
7 The cdc_mbim driver supports USB devices conforming to the "Universal
8 Serial Bus Communications Class Subclass Specification for Mobile
10 "Universal Serial Bus Communications Class Subclass Specifications for
24 -----------
26 :Valid Range: N/Y (0-1)
36 unbind/bind is required to make the change effective for NCM/MBIM
37 functions bound to the "wrong" driver
44 provides a userspace interface to the MBIM control channel, and will
[all …]
|
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
16 This node represents the multi-function "Hollywood" chip, which packages
21 - compatible : Should be "nintendo,hollywood"
30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
31 - reg : should contain the VI registers location and length
32 - interrupts : should contain the VI interrupt
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
42 - reg : should contain the PI registers location and length
52 - #interrupt-cells : <1>
[all …]
|
| /Documentation/input/joydev/ |
| D | joystick.rst | 3 .. _joystick-doc:
9 and similar devices. It is based on a larger project aiming to support all
14 linux-input@vger.kernel.org
16 send "subscribe linux-input" to majordomo@vger.kernel.org to subscribe to it.
25 ---------
27 For testing and other purposes (for example serial devices), there is a set
29 usually packaged as ``joystick``, ``input-utils``, ``evtest``, and so on.
31 ``inputattach`` utility is required if your joystick is connected to a
32 serial port.
35 ------------
[all …]
|
1234