Searched full:link (Results 1 – 25 of 434) sorted by relevance
12345678910>>...18
| /Documentation/networking/dsa/ |
| D | configuration.rst | 92 ip link set eth0 up
95 ip link set lan1 up
96 ip link set lan2 up
97 ip link set lan3 up
105 ip link set eth0 up
108 ip link set lan1 up
109 ip link set lan2 up
110 ip link set lan3 up
113 ip link add name br0 type bridge
116 ip link set dev lan1 master br0
[all …]
|
| 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 …]
|
| /Documentation/media/uapi/mediactl/ |
| D | media-ioc-setup-link.rst | 19 MEDIA_IOC_SETUP_LINK - Modify the properties of a link
42 To change link properties applications fill a struct
43 :c:type:`media_link_desc` with link identification
44 information (source and sink pad) and the new requested link flags. They
48 The only configurable property is the ``ENABLED`` link flag to
49 enable/disable a link. Links marked with the ``IMMUTABLE`` link flag can
52 Link configuration has no side effect on other links. If an enabled link
53 at the sink pad prevents the link from being enabled, the driver returns
56 Only links marked with the ``DYNAMIC`` link flag can be enabled/disabled
58 non-dynamic link will return an ``EBUSY`` error code.
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
59 - brcm,link-signal-sources : An array of hardware link
60 signal sources. Up to four link hardware signals can get muxed into
127 brcm,link-signal-sources = <0>;
132 brcm,link-signal-sources = <1>;
205 brcm,link-signal-sources = <0>;
207 /* USB link/activity routed to USB LED */
218 brcm,link-signal-sources = <4>;
219 /* EPHY0 link routed to EPHY0 LED */
[all …]
|
| /Documentation/networking/ |
| D | ipvlan.txt | 25 ip link add link <master> name <slave> type ipvlan [ mode MODE ] [ FLAGS ]
31 (a) Following will create IPvlan link with eth0 as master in
33 bash# ip link add link eth0 name ipvl0 type ipvlan
34 (b) This command will create IPvlan link in L2 bridge mode.
35 bash# ip link add link eth0 name ipvl0 type ipvlan mode l2 bridge
37 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
39 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 vepa
125 ip link add link eth0 ipvl0 type ipvlan mode l2
126 ip link add link eth0 ipvl1 type ipvlan mode l2
129 ip link set dev ipvl0 netns ns0
[all …]
|
| D | vrf.txt | 60 e.g, ip link add vrf-blue type vrf table 10
61 ip link set dev vrf-blue up
82 ip link set dev eth1 master vrf-blue
144 $ ip link add dev NAME type vrf table ID
153 $ ip [-d] link show type vrf
157 $ ip -d link show type vrf
159 link/ether 72:b3:ba:91:e2:24 brd ff:ff:ff:ff:ff:ff promiscuity 0
162 link/ether b6:6f:6e:f6:da:73 brd ff:ff:ff:ff:ff:ff promiscuity 0
165 link/ether 36:62:e8:7d:bb:8c brd ff:ff:ff:ff:ff:ff promiscuity 0
168 link/ether e6:28:b8:63:70:bb brd ff:ff:ff:ff:ff:ff promiscuity 0
[all …]
|
| D | sfp-phylink.rst | 14 phylink supports conventional phylib-based setups, fixed link setups
25 In PHY mode, we use phylib to read the current link settings from
28 negotiation being enabled on the link.
52 The link should be forced up or down appropriately in the
66 :c:func:`mac_link_down` functions must not force the MAC side link
77 three parts dealing with link-down, link-up and reconfiguring the
167 fixed link properties, and will also contain the sfp property.
172 of_phy_connect() was also passed a function pointer for link updates.
189 these functions. The old link update function for
197 when the in-band link state changes - otherwise the link will never
[all …]
|
| D | x25-iface.txt | 16 over the LAPB link. The first byte of the skbuff indicates the meaning of
26 over the LAPB link. The LAPB link should already exist before any data is
31 Establish the LAPB link. If the link is already established then the connect
36 Terminate the LAPB link. If it is already disconnected then the disconnect
50 received over the LAPB link.
54 LAPB link has been established. The same message is used for both a LAPB
55 link connect_confirmation and a connect_indication.
59 LAPB link has been terminated. This same message is used for both a LAPB
60 link disconnect_confirmation and a disconnect_indication.
|
| /Documentation/devicetree/bindings/sound/ |
| D | amlogic,axg-sound-card.txt | 16 - dai-link: Container for dai-link level properties and the CODEC
20 Required dai-link properties:
24 Required TDM Backend dai-link properties:
27 Optional TDM Backend dai-link properties:
40 Backend dai-link subnodes:
42 - codec: dai-link representing backend links should have at least one subnode.
43 One subnode for each codec of the dai-link.
44 dai-link representing frontend links have no codec, therefore have no
83 dai-link@0 {
87 dai-link@1 {
[all …]
|
| D | qcom,sdm845.txt | 28 - link-name:
31 Definition: User friendly name for dai link
63 mm1-dai-link {
64 link-name = "MultiMedia1";
70 pri-mi2s-dai-link {
71 link-name = "PRI MI2S Playback";
|
| D | qcom,apq8016-sbc.txt | 37 Dai-link subnode properties and subnodes:
39 Required dai-link subnodes:
46 -link-name : Name of the dai link.
70 internal-dai-link@0 {
80 external-dai-link@0 {
81 link-name = "ADV7533";
|
| D | soc-ac97link.txt | 1 AC97 link bindings
8 "ac97-running": AC97-link is active
9 "ac97-reset": AC97-link reset state
10 "ac97-warm-reset": AC97-link warm reset state
|
| D | simple-card.txt | 20 dai-link sub nodes are ignored.
32 - simple-audio-card,dai-link : Container for dai-link level
36 DAI link. See the examples and the
39 Dai-link subnode properties and subnodes:
41 If dai-link subnode is omitted and the subnode properties are directly
45 Required dai-link subnodes:
50 Optional dai-link subnode properties:
55 - frame-master : Indicates dai-link frame master.
57 - bitclock-master : Indicates dai-link bit clock master.
60 dai-link uses bit clock inversion.
[all …]
|
| D | qcom,apq8096.txt | 62 - link-name:
65 Definition: User friendly name for dai link
99 mm1-dai-link {
100 link-name = "MultiMedia1";
106 hdmi-dai-link {
107 link-name = "HDMI Playback";
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.txt | 35 - link : Should be a list of phandles to other switch's DSA
63 - fixed-link : Fixed-link subnode describing a link to a non-MDIO
65 Documentation/devicetree/bindings/net/fixed-link.txt
108 link = <&switch1port6
110 fixed-link {
119 fixed-link {
161 link = <&switch2port9>;
163 fixed-link {
172 link = <&switch0port5>;
173 fixed-link {
[all …]
|
| /Documentation/ABI/testing/ |
| 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-bus-fcoe | 51 lesb/link_fail: Link Error Status Block (LESB) link failure count.
53 lesb/vlink_fail: Link Error Status Block (LESB) virtual link
56 lesb/miss_fka: Link Error Status Block (LESB) missed FCoE
59 lesb/symb_err: Link Error Status Block (LESB) symbolic error count.
61 lesb/err_block: Link Error Status Block (LESB) block error count.
63 lesb/fcs_error: Link Error Status Block (LESB) Fibre Channel
100 "Disconnected" - No link to the FCF/fabric
108 link flapping adapter doesn't continually advance the count
|
| D | sysfs-class-net-qmi | 8 Set this to 'Y' to change the network device link
11 The netdev will change to reflect the link framing
14 frames with an ethernet header over the USB link. The
17 without any L2 header over the USB link.
22 link framing mode, changing this setting to 'Y' if the
|
| /Documentation/driver-api/ |
| D | device_link.rst | 31 In its standard or *managed* form, a device link combines *both* dependency
39 suspend/resume and shutdown ordering is needed, the device link may
44 ``DL_FLAG_PM_RUNTIME`` flag on addition of the device link, the PM core
56 remains in a consistent state: E.g. a device link cannot be added in
59 or the device link needs to be added from a function which is guaranteed
63 Another example for an inconsistent state would be a device link that
66 driver core known about the device link earlier, it wouldn't have probed the
68 presence of the supplier after adding the link, and defer probing on
69 non-presence. [Note that it is valid to create a link from the consumer's
71 know that the supplier is functional already at the link creation time (that is
[all …]
|
| /Documentation/misc-devices/ |
| D | spear-pcie-gadget.txt | 33 link :gives ltssm status.
46 link :write UP to enable ltsmm DOWN to disable
94 go for link up now.
95 # echo UP >> link
97 It will have to be insured that, once link up is done on gadget, then only host
100 /*wait till link is up*/
101 # cat link
116 go for link up now
117 # echo UP >> link
119 wait till link is up
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | uniphier-usb3-ssphy.txt | 19 "gio", "link" - for Pro4 SoC
20 "phy", "phy-ext", "link" - for PXs3 SoC, "phy-ext" is optional.
21 "phy", "link" - for others
25 "gio", "link" - for Pro4 SoC
26 "phy", "link" - for others
50 clock-names = "link", "phy";
52 reset-names = "link", "phy";
|
| D | uniphier-usb3-hsphy.txt | 19 "gio", "link" - for Pro4 SoC
20 "phy", "phy-ext", "link" - for PXs3 SoC, "phy-ext" is optional.
21 "phy", "link" - for others
25 "gio", "link" - for Pro4 SoC
26 "phy", "link" - for others
59 clock-names = "link", "phy";
61 reset-names = "link", "phy";
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl-enetc.txt | 4 external) there are two supported link modes specified by
86 2. The ENETC port is an internal port or has a fixed-link external
89 In this case, the ENETC port node defines a fixed link connection,
90 as specified by Documentation/devicetree/bindings/net/fixed-link.txt.
94 - fixed-link : "fixed-link" node, defined in "fixed-link.txt".
100 fixed-link {
|
| /Documentation/scsi/ |
| D | scsi_fc_transport.txt | 40 physical link to the switch for communication. Each N_Port_ID can have a
84 a new scsi_host for the vport and link its object under the vport.
88 This could be used in the future to link the object onto a vm-specific
90 a symbolic link to the vport object will be placed in the physical
146 but it will not be active on the FC link.
194 independent of the adapter's link state.
195 - Instantiation of the vport on the FC link via ELS traffic, etc.
196 This is equivalent to a "link up" and successful link initialization.
208 The vport has been successfully been created on the FC link.
213 on the FC link. This is equivalent to a physical port with the
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | uniphier-regulator.txt | 24 "gio", "link" - for Pro4 and Pro5 SoCs
25 "link" - for others
29 "gio", "link" - for Pro4 and Pro5 SoCs
30 "link" - for others
47 clock-names = "link";
49 reset-names = "link";
|
12345678910>>...18