Searched +full:g +full:- +full:link (Results 1 – 25 of 228) sorted by relevance
12345678910
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 19 functions with live state, and best-effort approaches which can be helpful for 38 * The return code is non-zero to indicate that the trace is not reliable. 47 function should attempt to detect such cases and return a non-zero error 52 3. Compile-time analysis 76 -------------------------------------- 84 * Dynamically generated code (e.g. eBPF) or foreign code (e.g. EFI runtime 89 architectures verify that a stacktrace ends at an expected location, e.g. 95 * On a specific stack expected for a kernel entry point (e.g. if the 99 ------------------------------- 101 Unwinding typically relies on code following specific conventions (e.g. [all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | nixge.txt | 4 - compatible: Should be "ni,xge-enet-3.00", but can be "ni,xge-enet-2.00" for 5 older device trees with DMA engines co-located in the address map, 7 - reg: Address and length of the register set for the device. It contains the 8 information of registers in the same order as described by reg-names. 9 - reg-names: Should contain the reg names 12 - interrupts: Should contain tx and rx interrupt 13 - interrupt-names: Should be "rx" and "tx" 14 - phy-mode: See ethernet.txt file in the same directory. 15 - nvmem-cells: Phandle of nvmem cell containing the MAC address 16 - nvmem-cell-names: Should be "address" [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-xdata | 1 What: /sys/class/misc/drivers/dw-xdata-pcie.<device>/write 6 will create write TLPs frames - from the Root Complex to the 12 Usage e.g. 13 echo 1 > /sys/class/misc/dw-xdata-pcie.<device>/write 15 echo 0 > /sys/class/misc/dw-xdata-pcie.<device>/write 17 The user can read the current PCIe link throughput generated 20 Usage e.g. 21 cat /sys/class/misc/dw-xdata-pcie.<device>/write 26 What: /sys/class/misc/dw-xdata-pcie.<device>/read 31 will create read TLPs frames - from the Endpoint to the Root [all …]
|
| D | sysfs-class-net | 35 Values vary based on the lower-level protocol used by the 45 Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC 53 Bitmask to allow forwarding of link local frames with address 54 01-80-C2-00-00-0X on a bridge device. Only values that set bits 57 Default value 0 does not forward any link local frames. 62 0 01-80-C2-00-00-00 Bridge Group Address used for STP 63 1 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE 64 2 01-80-C2-00-00-02 (Link Aggregation) 802.3ad 68 care when forwarding control frames e.g. 802.1X-PAE or LLDP. 76 string, e.g: ff:ff:ff:ff:ff:ff for an Ethernet broadcast MAC [all …]
|
| /Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 14 - `Overview`_ 15 - `Acquiring Firmware`_ 16 - `Devlink Info`_ 17 - `Configure Device`_ 18 - `Statistics`_ 25 are also incorporated in the companies' family of Agilio SmartNICs. The SR-IOV 35 Firmware files on the host filesystem contain card type (`AMDA-*` string), media 40 `linux-firmware.git` repository. 46 ----------------- [all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,glink-rpm-edge.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/qcom,glink-rpm-edge.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm G-Link RPM edge 10 Qualcomm G-Link edge, a FIFO based mechanism for communication with Resource 14 - Bjorn Andersson <andersson@kernel.org> 18 const: qcom,glink-rpm 30 - description: rpm_hlos mailbox in APCS 32 qcom,remote-pid: [all …]
|
| D | qcom,glink-edge.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/qcom,glink-edge.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm G-Link Edge communication channel nodes 10 - Bjorn Andersson <bjorn.andersson@linaro.org> 13 Qualcomm G-Link subnode represents communication edge, channels and devices 20 - qcom,glink-channels 27 - qcom,glink-channels 34 - qcom,glink-channels [all …]
|
| /Documentation/networking/device_drivers/wwan/ |
| D | t7xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 3 .. Copyright (C) 2020-21 Intel Corporation 8 t7xx driver for MTK PCIe based T700 5G modem 11 for data exchange over PCIe interface between Host platform & MediaTek's T700 5G modem. 13 application (e.g. Modem Manager) could easily manage the MBIM interface to enable 26 - mbimcli (included with the libmbim [2] library), and 27 - Modem Manager [3] 32 - open the MBIM control channel 33 - configure network connection settings 34 - connect to network [all …]
|
| D | iosm.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 3 .. Copyright (C) 2020-21 Intel Corporation 24 - mbimcli (included with the libmbim [2] library), and 25 - Modem Manager [3] 29 - open the MBIM control channel 30 - configure network connection settings 31 - connect to network 32 - configure IP network interface 37 described in [1] Mobile Broadband Interface Model v1.0 Errata-1. 40 ---------------------------------- [all …]
|
| /Documentation/networking/ |
| D | representors.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 used to control internal switching on SmartNICs. For the closely-related port 10 representors on physical (multi-port) switches, see 14 ---------- 16 Since the mid-2010s, network cards have started offering more complex 17 virtualisation capabilities than the legacy SR-IOV approach (with its simple 18 MAC/VLAN-based switching model) can support. This led to a desire to offload 19 software-defined networks (such as OpenVSwitch) to these NICs to specify the 24 virtual switches and IOV devices. Just as each physical port of a Linux- 36 As a virtual link endpoint, the representor can be configured like any other [all …]
|
| D | cdc_mbim.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems 12 devices, aka "3G/LTE modems". 24 ----------- 26 :Valid Range: N/Y (0-1) 51 - mbimcli (included with the libmbim [3] library), and 52 - ModemManager [4] 57 - open the control channel 58 - configure network connection settings 59 - connect to network [all …]
|
| 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 19 impacts only Layer 3 and above so L2 tools (e.g., LLDP) are not affected 30 ------ 34 +-----------------------------+ 35 | vrf-blue | ===> route table 10 36 +-----------------------------+ 38 +------+ +------+ +-------------+ 40 +------+ +------+ +-------------+ [all …]
|
| D | bonding.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 Corrections, HA extensions: 2000/10/03-15: 13 - Willy Tarreau <willy at meta-x.org> 14 - Constantine Gavrilov <const-g at xpert.com> 15 - Chad N. Tindel <ctindel at ieee dot org> 16 - Janice Girouard <girouard at us dot ibm dot com> 17 - Jay Vosburgh <fubar at us dot ibm dot com> 22 - Mitch Williams <mitch.a.williams at intel.com> 31 Additionally, link integrity monitoring may be performed. 35 the original tools from extreme-linux and beowulf sites will not work [all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | tplink,safeloader-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: TP-Link SafeLoader partitions 10 TP-Link home routers store various data on flash (e.g. bootloader, 14 Flash space layout of TP-Link devices is stored on flash itself using 15 a custom ASCII-based format. That format was first found in TP-Link 17 CFE and U-Boot bootloaders. 21 calibration data). Others are semi-static (like kernel). Finally some [all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | ixgbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 8 Copyright(c) 1999-2018 Intel Corporation. 13 - Identifying Your Adapter 14 - Command Line Parameters 15 - Additional Configurations 16 - Known Issues 17 - Support 36 ---------------------------------- 38 82599-BASED ADAPTERS 41 - If your 82599-based Intel(R) Network Adapter came with Intel optics or is an [all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | mt9v032.txt | 1 * Aptina 1/3-Inch WVGA CMOS Digital Image Sensor 3 The Aptina MT9V032 is a 1/3-inch CMOS active pixel digital image sensor with 5 two-wire serial interface. 9 - compatible: value should be either one among the following 16 (g) "aptina,mt9v034" for MT9V034 color sensor 21 - link-frequencies: List of allowed link frequencies in Hz. Each frequency is 22 expressed as a 64-bit big-endian integer. 23 - reset-gpios: GPIO handle which is connected to the reset pin of the chip. 24 - standby-gpios: GPIO handle which is connected to the standby pin of the chip. 27 Documentation/devicetree/bindings/media/video-interfaces.txt. [all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 14 mere parent/child relationship, e.g. between siblings, and have the 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 57 device ``->probe`` callback or a boot-time PCI quirk. 59 Another example for an inconsistent state would be a device link that 61 ``->probe`` callback while the supplier hasn't started to probe yet: Had the 62 driver core known about the device link earlier, it wouldn't have probed the [all …]
|
| /Documentation/sound/designs/ |
| D | timestamping.rst | 7 - Trigger_tstamp is the system time snapshot taken when the .trigger 11 estimate with a delay. In the latter two cases, the low-level driver 17 - tstamp is the current system timestamp updated during the last 19 The difference (tstamp - trigger_tstamp) defines the elapsed time. 29 - ``avail`` reports how much can be written in the ring buffer 30 - ``delay`` reports the time it will take to hear a new sample after all 43 ascii-art, this could be represented as follows (for the playback 47 --------------------------------------------------------------> time 50 analog link dma app FullBuffer 53 |< codec delay >|<--hw delay-->|<queued samples>|<---avail->| [all …]
|
| /Documentation/translations/zh_TW/arch/arm64/ |
| D | hugetlbpage.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 .. include:: ../../disclaimer-zh_TW.rst 8 Hu Haowen <2023002089@link.tyut.edu.cn> 15 兩點 - 17 - 大頁的大小 18 - TLBs 支持的條目大小 23 ----------------------- 30 ------------- 40 支持以下大頁尺寸配置 - 43 - CONT PTE PMD CONT PMD PUD [all …]
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 7 Documentation/maintainer/pull-requests.rst) should be signed with the 9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same 10 key for the project, you can set it in the configuration and use the ``-s`` 11 flag. To set the default ``key-id`` use:: 34 ---------------------------------------- 39 patch to a subsystem tree, it is a good idea to provide a Link: tag with a 42 The link tag will look like this:: 44 Link: https://lore.kernel.org/r/<message-id> 50 $ cat >.git/hooks/applypatch-msg <<'EOF' 52 . git-sh-setup [all …]
|
| /Documentation/block/ |
| D | cmdline-partition.rst | 15 blkdevparts=<blkdev-def>[;<blkdev-def>] 16 <blkdev-def> := <blkdev-id>:<partdef>[,<partdef>] 17 <partdef> := <size>[@<offset>](part-name) 19 <blkdev-id> 24 partition size, in bytes, such as: 512, 1m, 1G. 27 K, M, G, T, P, E. 29 "-" is used to denote all remaining space. 35 K, M, G, T, P, E. 37 (part-name) 39 create a link to block device partition with the name "PARTNAME". [all …]
|
| /Documentation/sound/soc/ |
| D | dpcm.rst | 9 various digital endpoints during the PCM stream runtime. e.g. PCM0 can route 18 DPCM re-uses all the existing component codec, platform and DAI drivers without 23 ------------------------------------- 26 document for all examples :- 32 PCM0 <------------> * * <----DAI0-----> Codec Headset 34 PCM1 <------------> * * <----DAI1-----> Codec Speakers 36 PCM2 <------------> * * <----DAI2-----> MODEM 38 PCM3 <------------> * * <----DAI3-----> BT 40 * * <----DAI4-----> DMIC 42 * * <----DAI5-----> FM [all …]
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | configure-git.rst | 1 .. include:: ../disclaimer-zh_CN.rst 3 :Original: Documentation/maintainer/configure-git.rst 16 Documentation/maintainer/pull-requests.rst 中使用的标记分支应使用开发人员的 17 GPG公钥进行签名。可以通过将 ``-u`` 标志传递给 ``git tag`` 来创建签名标记。 40 ------------------------------- 47 Link: https://lore.kernel.org/r/<message-id> 51 .. code-block:: none 54 $ cat >.git/hooks/applypatch-msg <<'EOF' 56 . git-sh-setup 57 perl -pi -e 's|^Message-Id:\s*<?([^>]+)>?$|Link: https://lore.kernel.org/r/$1|g;' "$1" [all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-funcs.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _media-user-func: 13 media-func-open 14 media-func-close 15 media-func-ioctl 16 media-ioc-device-info 17 media-ioc-g-topology 18 media-ioc-enum-entities 19 media-ioc-enum-links 20 media-ioc-setup-link [all …]
|
| /Documentation/scsi/ |
| D | scsi_fc_transport.rst | 1 .. SPDX-License-Identifier: GPL-2.0 40 -------- 44 Virtualization (NPIV) mechanism, a point-to-point connection to a Fabric 47 physical link to the switch for communication. Each N_Port_ID can have a 48 unique view of the fabric based on fabric zoning and array lun-masking 49 (just like a normal non-NPIV adapter). Using the Virtual Fabric (VF) 57 The FC transport is now recognizing a new object - a vport. A vport is 58 an entity that has a world-wide unique World Wide Port Name (wwpn) and 72 At this time, the transport is written to create only NPIV-based 73 vports. However, consideration was given to VF-based vports and it [all …]
|
12345678910