Searched +full:link +full:- +full:name (Results 1 – 25 of 297) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/sound/ |
| D | mt8195-mt6359.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mt8195-mt6359.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Trevor Wu <trevor.wu@mediatek.com> 16 - $ref: sound-card-common.yaml# 21 - mediatek,mt8195_mt6359_rt1019_rt5682 22 - mediatek,mt8195_mt6359_rt1011_rt5682 23 - mediatek,mt8195_mt6359_max98390_rt5682 27 description: User specified audio sound card name [all …]
|
| D | qcom,sm8250.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org> 19 - items: 20 - enum: 21 - lenovo,yoga-c630-sndcard 22 - qcom,db845c-sndcard 23 - const: qcom,sdm845-sndcard 24 - items: [all …]
|
| D | google,sc7280-herobrine.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/google,sc7280-herobrine.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Google SC7280-Herobrine ASoC sound card driver 10 - Judy Hsiao <judyhsiao@chromium.org> 16 - $ref: sound-card-common.yaml# 21 - google,sc7280-herobrine 23 "#address-cells": 26 "#size-cells": [all …]
|
| D | google,sc7180-trogdor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/google,sc7180-trogdor.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Google SC7180-Trogdor ASoC sound card driver 10 - Rohit kumar <quic_rohkumar@quicinc.com> 11 - Cheng-Yi Chiang <cychiang@chromium.org> 17 - $ref: sound-card-common.yaml# 22 - google,sc7180-trogdor 23 - google,sc7180-coachz [all …]
|
| D | mt8192-mt6359-rt1015-rt5682.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mt8192-mt6359-rt1015-rt5682.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jiaxin Yu <jiaxin.yu@mediatek.com> 11 - Shane Chien <shane.chien@mediatek.com> 17 - $ref: sound-card-common.yaml# 22 - mediatek,mt8192_mt6359_rt1015_rt5682 23 - mediatek,mt8192_mt6359_rt1015p_rt5682 24 - mediatek,mt8192_mt6359_rt1015p_rt5682s [all …]
|
| D | imx-audio-card.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/imx-audio-card.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Shengjiu Wang <shengjiu.wang@nxp.com> 13 - $ref: sound-card-common.yaml# 18 - fsl,imx-audio-card 21 ".*-dai-link$": 23 Each subnode represents a dai link. Subnodes of each dai links would be 29 link-name: [all …]
|
| D | mt8186-mt6366-da7219-max98357.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mt8186-mt6366-da7219-max98357.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jiaxin Yu <jiaxin.yu@mediatek.com> 16 - $ref: sound-card-common.yaml# 21 - mediatek,mt8186-mt6366-da7219-max98357-sound 23 audio-routing: 24 $ref: /schemas/types.yaml#/definitions/non-unique-string-array 35 - HDMI1 [all …]
|
| D | qcom,apq8016-sbc-sndcard.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/sound/qcom,apq8016-sbc-sndcard.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org> 11 - Stephan Gerhold <stephan@gerhold.net> 16 - qcom,apq8016-sbc-sndcard 17 - qcom,msm8916-qdsp6-sndcard 21 - description: Microphone I/O mux register address 22 - description: Speaker I/O mux register address [all …]
|
| D | mt8186-mt6366-rt1019-rt5682s.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mt8186-mt6366-rt1019-rt5682s.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jiaxin Yu <jiaxin.yu@mediatek.com> 16 - $ref: sound-card-common.yaml# 21 - mediatek,mt8186-mt6366-rt1019-rt5682s-sound 22 - mediatek,mt8186-mt6366-rt5682s-max98360-sound 23 - mediatek,mt8186-mt6366-rt5650-sound 25 audio-routing: [all …]
|
| D | mediatek,mt8365-mt6357.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mediatek,mt8365-mt6357.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alexandre Mergnat <amergnat@baylibre.com> 14 const: mediatek,mt8365-mt6357 16 pinctrl-names: 19 - const: default 20 - const: dmic 21 - const: miso_off [all …]
|
| D | mediatek,mt8188-mt6359.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mediatek,mt8188-mt6359.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Trevor Wu <trevor.wu@mediatek.com> 13 - $ref: sound-card-common.yaml# 18 - mediatek,mt8188-es8326 19 - mediatek,mt8188-mt6359-evb 20 - mediatek,mt8188-nau8825 21 - mediatek,mt8188-rt5682s [all …]
|
| /Documentation/networking/dsa/ |
| D | b53.rst | 1 .. SPDX-License-Identifier: GPL-2.0 20 The switch is, if possible, configured to enable a Broadcom specific 4-bytes 30 configuration described in the :ref:`dsa-config-showcases`. 33 ---------------------------------- 38 See :ref:`dsa-tagged-configuration`. 41 ------------------------------------- 48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`. 54 In difference to the configuration described in :ref:`dsa-vlan-configuration` 64 .. code-block:: sh 67 ip link add link eth0 name eth0.1 type vlan id 1 [all …]
|
| D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 .. _dsa-config-showcases: 13 ----------------------- 42 - when a DSA user interface is brought up, the conduit interface is 44 - when the conduit interface is brought down, all DSA user interfaces are 71 * lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3) 72 * lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7) 73 * lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11) 76 * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255) 79 * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255) [all …]
|
| /Documentation/netlink/specs/ |
| D | rt_link.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 3 name: rt-link 4 protocol: netlink-raw 8 Link configuration over rtnetlink. 11 - 12 name: ifinfo-flags 15 - 16 name: up 17 - 18 name: broadcast [all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 9 # mount -t configfs none /sys/kernel/config/ 12 What: /sys/kernel/config/most_cdev/<link> 22 configure the sub-buffer size for this channel 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 60 configuration, the creation is post-poned until 65 active link 67 What: /sys/kernel/config/most_video/<link> [all …]
|
| 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, 7 denoted as ... above, is of the form <supplier>--<consumer> 8 where <supplier> is the supplier bus:device name and <consumer> 9 is the consumer bus:device name. 15 This file indicates if the device link will ever be 21 - 'consumer unbind' 22 - 'supplier unbind' 23 - 'never' 25 'consumer unbind' means the device link will be removed when [all …]
|
| D | configfs-usb-gadget-ecm | 1 What: /config/usb-gadget/gadget/functions/ecm.name 8 - network device interface name associated with 11 - queue length multiplier for high and 14 - MAC address of host's end of this 15 Ethernet over USB link 17 - MAC address of device's end of this 18 Ethernet over USB link
|
| D | configfs-usb-gadget-ncm | 1 What: /config/usb-gadget/gadget/functions/ncm.name 7 ifname - network device interface name associated with 9 qmult - queue length multiplier for high and 11 host_addr - MAC address of host's end of this 12 Ethernet over USB link 13 dev_addr - MAC address of device's end of this 14 Ethernet over USB link
|
| D | sysfs-bus-fcoe | 4 Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org 13 per-port settings and finally write to the fcoe_ctlr_device's 19 fcoe_ctlr_device's sysfs name to this file will log the 28 Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org 31 1) Write interface name to ctlr_create 2) Configure the FCoE 34 writing its name, i.e. ctlr_X to the ctlr_delete file. 58 Link Error Status Block (LESB) link failure count. 61 Link Error Status Block (LESB) virtual link 65 Link Error Status Block (LESB) missed FCoE 66 Initialization Protocol (FIP) Keep-Alives (FKA). [all …]
|
| /Documentation/networking/device_drivers/ethernet/ti/ |
| D | cpsw_switchdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0 17 ip -d link show dev sw0p1 | grep switchid 20 ATTR{phys_port_name}!="", NAME="sw0$attr{phys_port_name}" 26 - The new (cpsw_new.c) driver is operating in dual-emac mode by default, thus 30 - optimized promiscuous mode: The P0_UNI_FLOOD (both ports) is enabled in 36 - learning disabled on ports as it make not too much sense for 37 segregated ports - no forwarding in HW. 38 - enabled basic support for devlink. 47 name switch_mode type driver-specific 50 name ale_bypass type driver-specific [all …]
|
| D | am65_nuss_cpsw_switchdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0 14 ip -d link show dev sw0p1 | grep switchid 17 ATTR{phys_port_name}!="", NAME="sw0$attr{phys_port_name}" 23 - The driver is operating in multi-mac mode by default, thus 29 See Documentation/networking/devlink/am65-nuss-cpsw-switch.rst 38 name switch_mode value true cmode runtime 40 This can be done regardless of the state of Port's netdev devices - UP/DOWN, but 45 When the both interfaces joined the bridge - CPSW switch driver will enable 56 name switch_mode value true cmode runtime 58 ip link add name br0 type bridge [all …]
|
| /Documentation/networking/ |
| D | vrf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 routing and forwarding domains (aka VRFs, VRF-lite to be specific) in the 12 Linux network stack. One use case is the multi-tenancy problem where each 30 ------ 34 +-----------------------------+ 35 | vrf-blue | ===> route table 10 36 +-----------------------------+ 38 +------+ +------+ +-------------+ 40 +------+ +------+ +-------------+ 42 +------+ +------+ [all …]
|
| D | ipvlan.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 exception of using L3 for mux-ing /demux-ing among slaves. This property makes 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 61 IPvlan has two modes of operation - L2 and L3. For a given master device, [all …]
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details 11 low-level userspace applications, with a new kernel release, the users 12 of sysfs must follow some rules to use an as-abstract-as-possible way to 21 - Do not use libsysfs 23 offer any abstraction, it exposes all the kernel driver-core 31 - sysfs is always at ``/sys`` 38 - devices are only "devices" 39 There is no such thing like class-, bus-, physical devices, 41 just simply a "device". Class-, bus-, physical, ... types are just 47 - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``) [all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-setup-link.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 10 Name chapter 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 [all …]
|
12345678910>>...12