Searched full:link (Results 1 – 25 of 786) sorted by relevance
12345678910>>...32
| /Documentation/networking/dsa/ |
| D | b53.rst | 67 ip link add link eth0 name eth0.1 type vlan id 1
68 ip link add link eth0 name eth0.2 type vlan id 2
69 ip link add link eth0 name eth0.3 type vlan id 3
72 ip link set eth0 up
73 ip link set eth0.1 up
74 ip link set eth0.2 up
75 ip link set eth0.3 up
78 ip link set wan up
79 ip link set lan1 up
80 ip link set lan2 up
[all …]
|
| D | configuration.rst | 101 ip link set eth0 up
104 ip link set lan1 up
105 ip link set lan2 up
106 ip link set lan3 up
113 ip link set eth0 up
116 ip link set lan1 up
117 ip link set lan2 up
118 ip link set lan3 up
121 ip link add name br0 type bridge
124 ip link set dev lan1 master br0
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-setup-link.rst | 13 MEDIA_IOC_SETUP_LINK - Modify the properties of a link
34 To change link properties applications fill a struct
35 :c:type:`media_link_desc` with link identification
36 information (source and sink pad) and the new requested link flags. They
40 The only configurable property is the ``ENABLED`` link flag to
41 enable/disable a link. Links marked with the ``IMMUTABLE`` link flag can
44 Link configuration has no side effect on other links. If an enabled link
45 at the sink pad prevents the link from being enabled, the driver returns
48 Only links marked with the ``DYNAMIC`` link flag can be enabled/disabled
50 non-dynamic link will return an ``EBUSY`` error code.
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 12 What: /sys/kernel/config/most_cdev/<link>
35 configure whether this link will be an input
49 name of the device the link is to be attached to
52 name of the channel the link is to be attached to
59 creation of the link. In case of speculative
65 active link
67 What: /sys/kernel/config/most_video/<link>
90 configure whether this link will be an input
104 name of the device the link is to be attached to
107 name of the channel the link is to be attached to
[all …]
|
| D | sysfs-class-led-trigger-netdev | 21 What: /sys/class/leds/<led>/link
26 Signal the link state of the named network device.
30 If set to 1, the LED's normal state reflects the link state
83 Signal the link speed state of 10Mbps of the named network device.
87 If set to 1, the LED's normal state reflects the link state
91 Present only if the named network device supports 10Mbps link speed.
98 Signal the link speed state of 100Mbps of the named network device.
102 If set to 1, the LED's normal state reflects the link state
106 Present only if the named network device supports 100Mbps link speed.
113 Signal the link speed state of 1000Mbps of the named network device.
[all …]
|
| D | sysfs-devices-mapping | 41 value that means UPI link number X on die Y is connected to UPI
42 link Z on die W and this link between sockets can be monitored
59 UPI link 0 on die 0 is connected to UPI link 1 on die 1
60 UPI link 0 on die 1 is connected to UPI link 0 on die 3
61 UPI link 0 on die 2 is connected to UPI link 1 on die 3
62 UPI link 0 on die 3 is connected to UPI link 0 on die 1
|
| D | sysfs-bus-usb-lvstest | 1 Link Layer Validation Device is a standard device for testing of Super
2 Speed Link Layer tests. These nodes are available in sysfs only when lvs
10 for Link Layer Validation device. It is needed for TD.7.06.
16 Set "U1 timeout" for the downstream port where Link Layer
24 Set "U2 timeout" for the downstream port where Link Layer
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
53 with Link Layer Validation device. It is needed for TD.7.34.
58 Write to this node to issue "Warm Reset" for Link Layer Validation
|
| D | sysfs-class-devlink | 5 Provide a place in sysfs for the device link objects in the
6 kernel at any given time. The name of a device link directory,
15 This file indicates if the device link will ever be
25 'consumer unbind' means the device link will be removed when
28 'supplier unbind' means the device link will be removed when
31 'never' means the device link will not be automatically removed
45 This file indicates if the device link has any impact on the
61 This file indicates the status of the device link. The status
62 of a device link is affected by whether the supplier and
64 drivers. The status of a device link also affects the binding
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt8195-mt6359.yaml | 74 mediatek,dai-link:
81 ".*-dai-link$":
85 Container for dai-link level properties and CODEC sub-nodes.
88 link-name:
89 description: Indicates dai-link name and PCM stream name
116 description: Indicates dai-link clock master.
120 - link-name
128 # Disallow legacy properties if xxx-dai-link nodes are specified
132 ".*-dai-link$": false
154 mm-dai-link {
[all …]
|
| D | google,sc7280-herobrine.yaml | 30 "^dai-link@[0-9a-f]$":
32 Each subnode represents a dai link. Subnodes of each dai links would be
38 link-name:
39 description: Indicates dai-link name and PCM stream name.
45 description: dai link address.
82 - link-name
124 dai-link@0 {
125 link-name = "WCD Playback";
135 dai-link@1 {
136 link-name = "WCD Capture";
[all …]
|
| D | qcom,sm8250.yaml | 61 ".*-dai-link$":
63 Each subnode represents a dai link. Subnodes of each dai links would be
69 link-name:
70 description: Indicates dai-link name and PCM stream name.
103 - link-name
127 mm1-dai-link {
128 link-name = "MultiMedia0";
134 mm2-dai-link {
135 link-name = "MultiMedia2";
141 mm3-dai-link {
[all …]
|
| D | mt8192-mt6359-rt1015-rt5682.yaml | 86 ".*-dai-link$":
91 Container for dai-link level properties and CODEC sub-nodes.
94 link-name:
95 description: Indicates dai-link name and PCM stream name
126 description: Indicates dai-link clock master.
130 - link-name
138 # Disallow legacy properties if xxx-dai-link nodes are specified
142 ".*-dai-link$": false
167 spk-playback-dai-link {
168 link-name = "I2S3";
[all …]
|
| D | google,sc7180-trogdor.yaml | 36 "^dai-link(@[0-9])?$":
38 Each subnode represents a dai link. Subnodes of each dai links would be
44 link-name:
45 description: Indicates dai-link name and PCM stream name.
51 description: dai link address.
73 - link-name
102 dai-link@0 {
103 link-name = "MultiMedia0";
114 dai-link@1 {
115 link-name = "MultiMedia1";
[all …]
|
| D | mt8186-mt6366-da7219-max98357.yaml | 80 mediatek,dai-link:
87 ".*-dai-link$":
91 Container for dai-link level properties and CODEC sub-nodes.
94 link-name:
95 description: Indicates dai-link name and PCM stream name
126 description: Indicates dai-link clock master.
133 - link-name
141 # Disallow legacy properties if xxx-dai-link nodes are specified
145 ".*-dai-link$": false
170 hs-playback-dai-link {
[all …]
|
| D | imx-audio-card.yaml | 21 ".*-dai-link$":
23 Each subnode represents a dai link. Subnodes of each dai links would be
29 link-name:
30 description: Indicates dai-link name and PCM stream name.
71 - link-name
86 pri-dai-link {
87 link-name = "akcodec";
97 fe-dai-link {
98 link-name = "HiFi-ASRC-FE";
104 be-dai-link {
[all …]
|
| D | mt8186-mt6366-rt1019-rt5682s.yaml | 92 mediatek,dai-link:
99 ".*-dai-link$":
103 Container for dai-link level properties and CODEC sub-nodes.
106 link-name:
107 description: Indicates dai-link name and PCM stream name
127 description: Indicates dai-link clock master.
131 - link-name
139 # Disallow legacy properties if xxx-dai-link nodes are specified
143 ".*-dai-link$": false
173 hs-playback-dai-link {
[all …]
|
| D | qcom,apq8016-sbc-sndcard.yaml | 56 ".*-dai-link$":
58 Each subnode represents a dai link. Subnodes of each dai links would be
64 link-name:
65 description: Indicates dai-link name and PCM stream name.
98 - link-name
128 quaternary-dai-link {
129 link-name = "ADV7533";
138 primary-dai-link {
139 link-name = "WCD";
148 tertiary-dai-link {
[all …]
|
| /Documentation/networking/device_drivers/ethernet/ti/ |
| D | cpsw_switchdev.rst | 17 ip -d link show dev sw0p1 | grep switchid
66 ip link add name br0 type bridge
67 ip link set dev br0 type bridge vlan_filtering 0
69 ip link set dev sw0p1 master br0
70 ip link set dev sw0p2 master br0
74 ip link add name br0 type bridge
75 ip link set dev br0 type bridge vlan_filtering 0
77 ip link set dev br0 type bridge vlan_filtering 1
78 ip link set dev sw0p1 master br0
79 ip link set dev sw0p2 master br0
[all …]
|
| /Documentation/driver-api/cxl/ |
| D | access-coordinates.rst | 8 Shared Upstream Link Calculation
12 the endpoints behind a switch being more than the switch upstream link.
16 upstream link being a limiting factor in mind.
47 Min(SW 0 Upstream Link to RP0 BW,
48 Min(SW0SSLBIS for SW0DSP0 (EP0), EP0 DSLBIS, EP0 Upstream Link) +
49 Min(SW0SSLBIS for SW0DSP1 (EP1), EP1 DSLBIS, EP1 Upstream link)) +
50 Min(SW 1 Upstream Link to RP1 BW,
51 Min(SW1SSLBIS for SW1DSP0 (EP2), EP2 DSLBIS, EP2 Upstream Link) +
52 Min(SW1SSLBIS for SW1DSP1 (EP3), EP3 DSLBIS, EP3 Upstream link))) +
54 Min(SW 2 Upstream Link to RP2 BW,
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.yaml | 27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
85 brcm,link-signal-sources:
90 An array of hardware link signal sources. Up to four link hardware
181 brcm,link-signal-sources = <0>;
187 brcm,link-signal-sources = <1>;
273 brcm,link-signal-sources = <0>;
275 /* USB link/activity routed to USB LED */
288 brcm,link-signal-sources = <4>;
289 /* EPHY0 link routed to EPHY0 LED */
[all …]
|
| /Documentation/networking/ |
| D | x25-iface.rst | 21 over the LAPB link. The first byte of the skbuff indicates the meaning of
31 over the LAPB link. The LAPB link should already exist before any data is
36 Establish the LAPB link. If the link is already established then the connect
41 Terminate the LAPB link. If it is already disconnected then the disconnect
55 received over the LAPB link.
59 LAPB link has been established. The same message is used for both a LAPB
60 link connect_confirmation and a connect_indication.
64 LAPB link has been terminated. This same message is used for both a LAPB
65 link disconnect_confirmation and a disconnect_indication.
|
| D | ipvlan.rst | 34 ip link add link <master> name <slave> type ipvlan [ mode MODE ] [ FLAGS ]
41 (a) Following will create IPvlan link with eth0 as master in
44 bash# ip link add link eth0 name ipvl0 type ipvlan
45 (b) This command will create IPvlan link in L2 bridge mode::
47 bash# ip link add link eth0 name ipvl0 type ipvlan mode l2 bridge
51 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
55 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 vepa
163 ip link add link eth0 ipvl0 type ipvlan mode l2
164 ip link add link eth0 ipvl1 type ipvlan mode l2
168 ip link set dev ipvl0 netns ns0
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | ti,ds90ub960.yaml | 7 title: Texas Instruments DS90UB9XX Family FPD-Link Deserializer Hubs
13 The TI DS90UB9XX devices are FPD-Link video deserializers with I2C and GPIO
63 '^link@[0-3]$':
68 description: The link number
87 FPD-Link Input Mode. This should reflect the hardware and the
93 - 0 # FPD-Link III
94 - 1 # FPD-Link IV
96 FPD-Link CDR Mode. This should reflect the hardware and the
112 description: FPD-Link Serializer node
127 description: FPD-Link input 0
[all …]
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | fsl,imx8qxp-pixel-link.yaml | 4 $id: http://devicetree.org/schemas/display/bridge/fsl,imx8qxp-pixel-link.yaml#
7 title: Freescale i.MX8qm/qxp Display Pixel Link
13 The Freescale i.MX8qm/qxp Display Pixel Link(DPL) forms a standard
21 The i.MX8qm/qxp Display Pixel Link is accessed via System Controller Unit(SCU)
27 - fsl,imx8qm-dc-pixel-link
28 - fsl,imx8qxp-dc-pixel-link
33 u8 value representing the display controller index that the pixel link
40 link connects to.
49 description: The pixel link input port node from upstream video source.
54 description: The pixel link output port node to downstream bridge.
[all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 27 In its standard or *managed* form, a device link combines *both* dependency
35 suspend/resume and shutdown ordering is needed, the device link may
40 ``DL_FLAG_PM_RUNTIME`` flag on addition of the device link, the PM core
52 remains in a consistent state: E.g. a device link cannot be added in
55 or the device link needs to be added from a function which is guaranteed
59 Another example for an inconsistent state would be a device link that
62 driver core known about the device link earlier, it wouldn't have probed the
64 presence of the supplier after adding the link, and defer probing on
65 non-presence. [Note that it is valid to create a link from the consumer's
67 know that the supplier is functional already at the link creation time (that is
[all …]
|
12345678910>>...32