Home
last modified time | relevance | path

Searched +full:network +full:- +full:on +full:- +full:chip (Results 1 – 25 of 67) sorted by relevance

123

/Documentation/devicetree/bindings/devfreq/event/
Dsamsung,exynos-nocp.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/devfreq/event/samsung,exynos-nocp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos NoC (Network on Chip) Probe
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
14 The Samsung Exynos542x SoC has a NoC (Network on Chip) Probe for NoC bus.
16 that the Network on Chip (NoC) probes detects are transported over the
17 network infrastructure to observer units. You can configure probes to capture
[all …]
/Documentation/devicetree/bindings/interconnect/
Dqcom,msm8974.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm MSM8974 Network-On-Chip Interconnect
10 - Brian Masney <masneyb@onstation.org>
14 bandwidth requirements between various network-on-chip fabrics.
22 - qcom,msm8974-bimc
23 - qcom,msm8974-cnoc
24 - qcom,msm8974-mmssnoc
25 - qcom,msm8974-ocmemnoc
[all …]
Dqcom,rpm-common.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,rpm-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect
10 - Konrad Dybcio <konradybcio@kernel.org>
14 through manual requests based on either predefined values or as indicated by
19 '#interconnect-cells':
21 - const: 2
22 - const: 1
[all …]
Dqcom,sc8280xp-rpmh.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,sc8280xp-rpmh.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect on SC8280XP
10 - Bjorn Andersson <andersson@kernel.org>
11 - Konrad Dybcio <konradybcio@kernel.org>
17 See also:: include/dt-bindings/interconnect/qcom,sc8280xp.h
22 - qcom,sc8280xp-aggre1-noc
23 - qcom,sc8280xp-aggre2-noc
[all …]
Dqcom,rpm.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPM Network-On-Chip Interconnect
10 - Georgi Djakov <djakov@kernel.org>
18 - $ref: qcom,rpm-common.yaml#
26 - qcom,msm8909-bimc
27 - qcom,msm8909-pcnoc
28 - qcom,msm8909-snoc
29 - qcom,msm8916-bimc
[all …]
Dqcom,sa8775p-rpmh.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,sa8775p-rpmh.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect on SA8775P
10 - Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
16 See also:: include/dt-bindings/interconnect/qcom,sa8775p.h
21 - qcom,sa8775p-aggre1-noc
22 - qcom,sa8775p-aggre2-noc
23 - qcom,sa8775p-clk-virt
[all …]
Dqcom,rpmh-common.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,rpmh-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect
10 - Georgi Djakov <djakov@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
22 '#interconnect-cells':
25 qcom,bcm-voters:
26 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
Dqcom,qdu1000-rpmh.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,qdu1000-rpmh.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm RPMh Network-On-Chip Interconnect on QDU1000
10 - Georgi Djakov <djakov@kernel.org>
11 - Odelu Kukatla <quic_okukatla@quicinc.com>
24 - qcom,qdu1000-clk-virt
25 - qcom,qdu1000-gem-noc
26 - qcom,qdu1000-mc-virt
[all …]
Dqcom,sm6350-rpmh.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,sm6350-rpmh.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm SM6350 RPMh Network-On-Chip Interconnect
10 - Luca Weiss <luca.weiss@fairphone.com>
13 Qualcomm RPMh-based interconnect provider on SM6350.
16 - $ref: qcom,rpmh-common.yaml#
21 - qcom,sm6350-aggre1-noc
22 - qcom,sm6350-aggre2-noc
[all …]
Dqcom,msm8939.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm MSM8937/MSM8939/MSM8976 Network-On-Chip interconnect
10 - Konrad Dybcio <konradybcio@kernel.org>
17 - $ref: qcom,rpm-common.yaml#
22 - qcom,msm8937-bimc
23 - qcom,msm8937-pcnoc
24 - qcom,msm8937-snoc
25 - qcom,msm8939-bimc
[all …]
Dinterconnect.txt14 etc. The consumer drivers set constraints on interconnect path (or endpoints)
15 depending on the use case. Interconnect providers can also be interconnect
16 consumers, such as in the case where two network-on-chip fabrics interface
20 - compatible : contains the interconnect provider compatible string
21 - #interconnect-cells : number of cells in a interconnect specifier needed to
28 compatible = "qcom,msm8916-snoc";
29 #interconnect-cells = <1>;
31 clock-names = "bus_clk", "bus_a_clk";
41 can be multiple interconnect providers on a SoC and the consumer may consume
42 multiple paths from different providers depending on use case and the
[all …]
/Documentation/networking/device_drivers/ethernet/davicom/
Ddm9000.rst1 .. SPDX-License-Identifier: GPL-2.0
4 DM9000 Network driver
9 Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>
13 ------------
15 This file describes how to use the DM9000 platform-device based network driver
18 The driver supports three DM9000 variants, the DM9000E which is the first chip
25 ----------------------------
37 An example from arch/arm/mach-s3c/mach-bast.c is::
91 -------------
113 The chip is connected to an external PHY.
[all …]
/Documentation/devicetree/bindings/net/
Dibm,emac.txt7 below, the node for the OPB bus on which the EMAC sits must have a
8 correct clock-frequency property.
13 - device_type : "network"
15 - compatible : compatible list, contains 2 entries, first is
16 "ibm,emac-CHIP" where CHIP is the host ASIC (440gx,
18 "ibm,emac4". For Axon, thus, we have: "ibm,emac-axon",
20 - interrupts : <interrupt mapping for EMAC IRQ and WOL IRQ>
21 - reg : <registers mapping>
22 - local-mac-address : 6 bytes, MAC address
23 - mal-device : phandle of the associated McMAL node
[all …]
/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dkconfig.rst1 .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
34 | built-in into mlx5_core.ko.
39 …g (DCB) Support <https://enterprise-support.nvidia.com/s/article/howto-auto-config-pfc-and-ets-on-…
53 | Flow-based classifiers, such as those registered through
54 | `tc-flower(8)`, are processed by the device, rather than the
61 | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering.
62 | https://enterprise-support.nvidia.com/s/article/howto-configure-arfs-on-connectx-4
67 | Enables :ref:`IPSec XFRM cryptography-offload acceleration <xfrm_device>`.
72 | Build support for MACsec cryptography-offload acceleration in the NIC.
77 | Enables ethtool receive network flow classification, which allows user defined
[all …]
/Documentation/arch/arm/
Dixp4xx.rst2 Release Notes for Linux on Intel's IXP4xx Network Processor
6 -------------------------------------------------------------------------
10 Intel's IXP4xx network processor is a highly integrated SOC that
11 is targeted for network applications, though it has become popular
14 that support different network offload functions such as encryption,
17 integration such as an on-chip I2C controller.
19 For more information on the various versions of the CPU, see:
21 http://developer.intel.com/design/network/products/npfamily/ixp4xx.htm
24 stripped of much of the network intelligence.
28 Linux currently supports the following features on the IXP4xx chips:
[all …]
/Documentation/devicetree/bindings/perf/
Darm,ni.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Arm NI (Network-on-Chip Interconnect) Performance Monitors
10 - Robin Murphy <robin.murphy@arm.com>
14 const: arm,ni-700
18 - description: Complete configuration register space
26 - compatible
27 - reg
28 - interrupts
/Documentation/scsi/
Dbnx2fc.rst1 .. SPDX-License-Identifier: GPL-2.0
9 transparent. Devices discovered on the SAN will be registered and unregistered
13 depend on the state of the network interfaces to operate. As such, the network
15 It is recommended that the network interfaces be configured to be brought up
20 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
26 1. Ensure that fcoe-utils package is installed.
28 2. Configure the interfaces on which bnx2fc driver has to operate on.
32 b. copy cfg-ethx to cfg-eth5 if FCoE has to be enabled on eth5.
34 d. Edit all the cfg-eth files to set "no" for DCB_REQUIRED** field, and
44 5. "Symbolic Name" in 'fcoeadm -i' output would display if bnx2fc has claimed
[all …]
/Documentation/devicetree/bindings/arm/omap/
Dl3-noc.txt1 * TI - L3 Network On Chip (NoC)
7 - compatible : Should be "ti,omap3-l3-smx" for OMAP3 family
8 Should be "ti,omap4-l3-noc" for OMAP4 family
9 Should be "ti,omap5-l3-noc" for OMAP5 family
10 Should be "ti,dra7-l3-noc" for DRA7 family
11 Should be "ti,am4372-l3-noc" for AM43 family
12 - reg: Contains L3 register address range for each noc domain.
13 - ti,hwmods: "l3_main_1", ... One hwmod for each noc domain.
18 compatible = "ti,omap4-l3-noc", "simple-bus";
19 #address-cells = <1>;
[all …]
/Documentation/devicetree/bindings/ata/
Dintel,ixp4xx-compact-flash.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/ata/intel,ixp4xx-compact-flash.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The IXP4xx network processors have a CompactFlash interface that presents
16 or two chip select areas and address translating logic on the board. The
17 node must be placed inside a chip select node on the IXP4xx expansion bus.
21 const: intel,ixp4xx-compact-flash
25 - description: Command interface registers
[all …]
/Documentation/admin-guide/perf/
Darm-ni.rst2 Arm Network-on Chip Interconnect PMU
5 NI-700 and friends implement a distinct PMU for each clock domain within the
Dstarfive_starlink_pmu.rst6 StarLink Coherent Network on Chip (CNoC) that connects multiple CPU
43 $ perf stat -a -e /starfive_starlink_pmu/cycles/ sleep 1
46 Attaching to a task is not supported, only system-wide counting is supported.
/Documentation/networking/device_drivers/hamradio/
Dz8530drv.rst1 .. SPDX-License-Identifier: GPL-2.0
5 SCC.C - Linux driver for Z8530 based HDLC cards for AX.25
14 1. ftp://ftp.ccac.rwth-aachen.de/pub/jr/z8530drv-utils_3.0-3.tar.gz
16 2. ftp://ftp.pspt.fi/pub/ham/linux/ax25/z8530drv-utils_3.0-3.tar.gz
20 Linux Kernel AX.25 documentation and programs, is available on
38 Unlike the versions below 2.4 this driver is a real network device
41 AX.25-HOWTO on how to emulate a KISS TNC on network device drivers.
54 please read 'man insmod' that comes with module-init-tools.
64 of your rc.*-files. This has to be done BEFORE you can
77 chip 1
[all …]
/Documentation/networking/
Drepresentors.rst1 .. SPDX-License-Identifier: GPL-2.0
5 Network Function Representors
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
20 network connectivity of each function. The resulting designs are variously
[all …]
Dswitchdev.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Copyright |copy| 2014-2015 Scott Feldman <sfeldma@gmail.com>
14 The Ethernet switch device driver model (switchdev) is an in-kernel driver
19 an example setup using a data-center-class switch ASIC chip. Other setups
20 with SR-IOV or soft switches, such as OVS, are possible.
25 User-space tools
28 +-------------------------------------------------------------------+
31 +--------------+-------------------------------+
32 | Network stack |
35 +----------------------------------------------+
[all …]
/Documentation/networking/device_drivers/ethernet/cirrus/
Dcs89x0.rst1 .. SPDX-License-Identifier: GPL-2.0
19 Linux Network Interface Driver ver. 2.00 <kernel 2.3.48>
33 2.1 CS8900-based Adapter Configuration
34 2.2 CS8920-based Adapter Configuration
46 5.2.1 Diagnostic Self-Test
47 5.2.2 Diagnostic Network Test
66 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
67 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
68 computers on 10 Mbps Ethernet networks. The adapters are designed for operation
69 in 16-bit ISA or EISA bus expansion slots and are available in
[all …]

123