/freebsd/crypto/openssh/ |
H A D | PROTOCOL.mux | 1 This document describes the multiplexing protocol used by ssh(1)'s 4 Multiplexing starts with a ssh(1) configured to act as a multiplexing 18 Many multiplexing (mux) client requests yield immediate responses from 22 The most common use of multiplexing however is to maintain multiple 37 the multiplexing protocol and start proxying SSH connection protocol 47 When a multiplexing connection is made to a ssh(1) operating as a 206 A client may request the master to stop accepting new multiplexing requests
|
H A D | clientloop.h | 66 /* Multiplexing protocol version */ 69 /* Multiplexing control protocol flags */
|
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
H A D | renesas,rzn1-pinctrl.txt | 28 The child nodes of the pin controller node describe a pin multiplexing 31 - Pin multiplexing sub-nodes: 32 A pin multiplexing sub-node describes how to configure a set of 38 The allowed generic formats for a pin multiplexing sub-node are the 86 Client sub-nodes shall refer to pin multiplexing sub-nodes using the phandle 105 integer array representing pin number and pin multiplexing configuration.
|
H A D | renesas,rza1-pinctrl.txt | 5 Pin multiplexing and GPIO configuration is performed on a per-pin basis 36 The child nodes of the pin controller node describe a pin multiplexing 39 - Pin multiplexing sub-nodes: 40 A pin multiplexing sub-node describes how to configure a set of 53 The allowed generic formats for a pin multiplexing sub-node are the 83 Client sub-nodes shall refer to pin multiplexing sub-nodes using the phandle 102 integer array representing pin number and pin multiplexing configuration.
|
H A D | pinmux-node.yaml | 7 title: Generic Pin Multiplexing Node 23 pin multiplexing nodes: 80 For hardware where pin multiplexing configurations have to be specified for 91 a single pin multiplexing configuration. 100 how pin IDs and pin multiplexing configuration are defined and assembled
|
H A D | renesas,rza2-pinctrl.txt | 4 Pin multiplexing and GPIO configuration is performed on a per-pin basis. 42 - Pin multiplexing sub-nodes: 43 A pin multiplexing sub-node describes how to configure a set of 53 integer array representing pin number and pin multiplexing configuration.
|
H A D | renesas,rzn1-pinctrl.yaml | 23 - description: GPIO Multiplexing Level1 Register Block 24 - description: GPIO Multiplexing Level2 Register Block 51 A pin multiplexing sub-node describes how to configure a set of (or a 58 Integer array representing pin number and pin multiplexing
|
H A D | cortina,gemini-pinctrl.txt | 4 see further arm/gemini.txt. It is a purely group-based multiplexing pin 12 Subnodes of the pin controller contain pin control multiplexing set-up 15 Please refer to pinctrl-bindings.txt for generic pin multiplexing nodes
|
H A D | brcm,bcm2835-gpio.txt | 46 The BCM2835 pin configuration and multiplexing supports the generic bindings. 60 Legacy pin configuration and multiplexing binding: 61 *** (Its use is deprecated, use generic multiplexing and configuration
|
H A D | ste,nomadik.txt | 22 pin multiplexing node layout from the standard pin control bindings 25 Required pin multiplexing subnode properties: 29 group that will be combined with the function to form a multiplexing
|
H A D | renesas,rza1-ports.yaml | 16 Pin multiplexing and GPIO configuration is performed on a per-pin basis 77 A pin multiplexing sub-node describes how to configure a set of (or a 96 Integer array representing pin number and pin multiplexing
|
H A D | pinctrl-zx.txt | 6 controllers work together to control pin multiplexing and configuration in 39 TOP_PMM and AON_IOCFG blocks, as the available multiplexing functions for
|
H A D | renesas,rza2-pinctrl.yaml | 16 Pin multiplexing and GPIO configuration is performed on a per-pin basis. 51 A pin multiplexing sub-node describes how to configure a set of
|
H A D | pinctrl-bindings.txt | 3 Hardware modules that control pin multiplexing or configuration parameters 103 == Generic pin multiplexing node content ==
|
H A D | pinctrl-st.txt | 4 PIO multiplexing block. Each pin supports GPIO functionality (ALT0) 11 ST pinctrl driver controls PIO multiplexing block and also interacts with
|
/freebsd/share/doc/psd/05.sysman/ |
H A D | 1.5.t | 93 Multiplexing requests 97 synchronous and asynchronous multiplexing of operations. 99 Synchronous multiplexing is performed by using the \fIselect\fP call 206 Protocols may be based on communications multiplexing or a rights-passing
|
/freebsd/share/man/man4/man4.aarch64/ |
H A D | rk_pinctrl.4 | 30 .Nd driver for the pin multiplexing on RockChip SoCs 36 device driver provides support for the pin multiplexing device present
|
/freebsd/sys/contrib/device-tree/Bindings/memory-controllers/ |
H A D | ti,gpmc-child.yaml | 208 Address and data multiplexing configuration. 211 1 for address-address-data multiplexing mode and 212 2 for address-data multiplexing mode.
|
H A D | omap-gpmc.txt | 124 - gpmc,mux-add-data Address and data multiplexing configuration. 126 multiplexing mode and 2 for address-data 127 multiplexing mode.
|
/freebsd/share/man/man4/ |
H A D | fdt_pinctrl.4 | 30 .Nd FDT I/O pin multiplexing support 34 Pin multiplexing is a technology used to re-purpose a single
|
/freebsd/sys/contrib/device-tree/Bindings/i2c/ |
H A D | i2c-mux-pinctrl.txt | 3 This binding describes an I2C bus multiplexer that uses pin multiplexing to 4 route the I2C signals, and represents the pin multiplexing configuration
|
H A D | i2c-mux-pinctrl.yaml | 13 This binding describes an I2C bus multiplexer that uses pin multiplexing to route the I2C 14 signals, and represents the pin multiplexing configuration using the pinctrl device tree
|
H A D | i2c-demux-pinctrl.txt | 3 This binding describes an I2C bus demultiplexer that uses pin multiplexing to 4 route the I2C signals, and represents the pin multiplexing configuration using
|
H A D | i2c-demux-pinctrl.yaml | 13 This binding describes an I2C bus demultiplexer that uses pin multiplexing to 14 route the I2C signals, and represents the pin multiplexing configuration
|
/freebsd/sys/contrib/device-tree/Bindings/sound/ |
H A D | samsung-i2s.yaml | 29 multiplexing) is to allow transfer of multiple channel audio data on 45 for playback and capture TDM (Time division multiplexing) to allow
|