Searched full:cable (Results 1 – 25 of 95) sorted by relevance
1234
| /Documentation/devicetree/bindings/power/supply/ |
| D | charger-manager.txt | 11 - subnode <cable> :
12 - cm-cable-name : name of charger cable - one of USB, USB-HOST,
15 - cm-cable-extcon : name of extcon dev
16 (optional) - cm-cable-min : minimum current of cable
17 (optional) - cm-cable-max : maximum current of cable
77 cable@0 {
78 cm-cable-name = "USB";
79 cm-cable-extcon = "extcon-dev.0";
80 cm-cable-min = <475000>;
81 cm-cable-max = <500000>;
[all …]
|
| /Documentation/driver-api/usb/ |
| D | typec.rst | 22 the roles and alternate modes of ports, partners and cable plugs when the port
39 The cable and the two plugs on it may also be optionally presented as their own
40 devices under /sys/class/typec/. The cable attached to the port "port0" port
41 will be named port0-cable and the plug on the SOP Prime end (see USB Power
43 Double Prime end "port0-plug1". The parent of a cable will always be the port,
44 and the parent of the cable plugs will always be the cable.
46 If the port, partner or cable plug supports Alternate Modes, every supported
102 After successful connection of a cable that supports USB Power Delivery
103 Structured VDM "Discover Identity", the port driver needs to register the cable
105 in the cable or not. So a cable capable of SOP Prime communication, but not SOP
[all …]
|
| D | typec_bus.rst | 81 Cable plug alternate modes
84 The alternate mode drivers are not bound to cable plug alternate mode devices,
86 requires, a cable that responds to SOP Prime, and optionally SOP Double Prime
87 messages, the driver for that alternate mode must request handle to the cable
118 Cable Plug operations
|
| D | usb3-debug-port.rst | 19 3) have a USB 3.0 super-speed A-to-A debugging cable.
62 the debug host. The cable used to connect these two ports
63 should be a USB 3.0 super-speed A-to-A debugging cable.
126 speed A-to-A debugging cable. You can see /dev/ttyDBC0 created
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-typec | 115 What: /sys/class/typec/<port>-{partner|cable}/usb_power_delivery_revision
120 specification of the port partner or cable, or 0.0 when USB
215 USB Type-C cable devices (eg. /sys/class/typec/port0-cable/)
217 Note: Electronically Marked Cables will have a device also for one cable plug
218 (eg. /sys/class/typec/port0-plug0). If the cable is active and has also SOP
223 What: /sys/class/typec/<port>-cable/type
228 cable if it is known. If the product type of the cable is not
231 When the cable product type is detected, uvevent is also raised
232 with PRODUCT_TYPE showing the product type of the cable.
238 active Active Cable
[all …]
|
| D | sysfs-class-extcon | 35 The /sys/class/extcon/.../state shows and stores the cable
65 interface associated with each cable cannot update
66 multiple cable states of an extcon device simultaneously.
68 What: /sys/class/extcon/.../cable.x/name
72 The /sys/class/extcon/.../cable.x/name shows the name of cable
75 What: /sys/class/extcon/.../cable.x/state
79 The /sys/class/extcon/.../cable.x/state shows and stores the
80 state of cable "x" (integer between 0 and 31) of an extcon
|
| D | sysfs-bus-counter-104-quad-8 | 6 encoder cable fault (not connected or loose wires) is detected
15 Whether detection of differential encoder cable faults for the
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-class-typec | 4 What: /sys/class/typec/<port|partner|cable>/<dev>/svid
11 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/
20 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description
27 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo
34 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active
39 for entering/exiting the mode with partners and cable plugs, and
|
| /Documentation/networking/ |
| D | plip.rst | 26 LapLink null-printer cable [can also work in turbo mode, with a PLIP
27 cable]. [The protocol used to pack IP packages, is a simple one
35 The PLIP cable is all that's needed to connect two Linux boxes, and it
72 PLIP driver is signaled whenever data is sent to it via the cable, such that
118 printer "null" cable to transfer data four bits at a time using
126 Parallel Transfer Mode 0 Cable
129 The cable for the first transfer mode is a standard
130 printer "null" cable which transfers data four bits at a time using
137 A cable that implements this protocol is available commercially as a
138 "Null Printer" or "Turbo Laplink" cable. It can be constructed with
[all …]
|
| /Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 8 as NextLevel) SURFboard1000 internal cable modem board. This is an ISA card
9 which is used by a number of cable TV companies to provide cable modem access.
10 It's a one-way downstream-only cable modem, meaning that your upstream net link
24 to configure the cable modem and network interface (usually called "cm0");
27 cable modem easy.
37 - http://web.archive.org/web/%2E/http://linuxpower.cx/~cable/
93 phone number, and frequency for the cable modem. Also edit pap-secrets
109 connect successfully the cable modem interface will come up and you'll see a
117 The command "cmconfig cm0" will give you information about the cable modem
194 (and typically during a lengthy download through the cable modem)!
|
| D | index.rst | 3 Cable Modem Device Drivers
|
| /Documentation/spi/ |
| D | butterfly.rst | 6 a parallel port adapter cable, together with an "AVR Butterfly" to run
10 develop firmware for this, and flash it using this adapter cable.
12 You can make this adapter from an old printer cable and solder things
25 The first cable connections will hook Linux up to one SPI bus, with the
45 (c) cable in the chipselect.
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-property-cable-systems.rst | 3 .. _frontend-property-cable-systems:
6 Properties used on cable delivery systems
15 The DVB-C Annex-A is the widely used cable standard. Transmission uses
|
| D | frontend.rst | 10 systems: Terrestrial, cable and Satellite. Currently, the following
16 - Cable systems: DVB-C Annex A/C, ClearQAM (DVB-C Annex B)
|
| D | fe-type-t.rst | 67 - For ATSC standard (terrestrial) or for DVB-C Annex B (cable) used
70 - ``SYS_ATSC`` (terrestrial) or ``SYS_DVBC_ANNEX_B`` (cable)
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 85 for bus resets takes place, you have to establish any FireWire cable
110 2) Establish a working FireWire cable connection:
112 Any FireWire cable, as long at it provides electrically and mechanically
120 on both machines in the kernel log when the cable is plugged in
158 which is connected to the debugged machine over the FireWire cable).
162 With the FireWire cable connected, the OHCI-1394 driver on the debugging
|
| /Documentation/scsi/ |
| D | lpfc.rst | 29 Cable pull and temporary device Loss:
32 received from the midlayer. In the cases where a cable was pulled, link
33 jitter, or a device temporarily loses connectivity (due to its cable
|
| /Documentation/input/devices/ |
| D | xpad.rst | 111 adapter cable to break out the proprietary connector's pins to USB.
114 Such a cable is pretty easy to build. The Controller itself is a USB
119 You just need to solder a USB connector onto the cable and keep the
124 Thanks to the trip splitter found on the cable you don't even need to cut the
125 original one. You can buy an extension cable and cut that instead. That way,
133 Once you have the adapter cable, if needed, and the controller connected
|
| /Documentation/arm/sti/ |
| D | stih415-overview.rst | 9 for satellite, cable, terrestrial and IP-STB markets.
|
| D | stih416-overview.rst | 9 for satellite, cable, terrestrial and IP-STB markets.
|
| D | stih407-overview.rst | 9 and server/connected client application for satellite, cable, terrestrial
|
| /Documentation/networking/device_drivers/ |
| D | index.rst | 13 cable/index
|
| /Documentation/firmware-guide/acpi/ |
| D | intel-pmc-mux.rst | 20 configure the cable plug orientation and mode (with Alternate Modes). The driver
95 should not configure them according to the cable plug orientation. This can
96 happen for example if a retimer on the platform handles the cable plug
|
| /Documentation/fb/ |
| D | pvr2fb.rst | 51 cable:X cable type. This can be any of the following: vga, rgb, and
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,spdif.yaml | 14 processor to receive and transmit digital audio via an coaxial cable or
15 a fibre cable.
|
1234