interconnect\- (full) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:interconnect +full:- (Results 1 – 25 of 334) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...14

/freebsd/sys/contrib/device-tree/Bindings/interconnect/
H A D	interconnect.txt	1 Interconnect Provider Device Tree Bindings 4 The purpose of this document is to define a common set of generic interconnect 8 = interconnect providers = 10 The interconnect provider binding is intended to represent the interconnect 11 controllers in the system. Each provider registers a set of interconnect 12 nodes, which expose the interconnect related capabilities of the interconnect 14 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 [all …]
H A D	qcom,qcm2290.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,qcm2290.yaml# 5 $schema: http://devicetree.org/meta-schema [all...]`
H A D	qcom,sdm660.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sdm660.yaml# 5 $schema: http://devicetree.org/meta-schema [all...]`
H A D	qcom,sm6350-rpmh.yaml	`1 # 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 …]`
H A D	qcom,msm8953.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8953.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm MSM8953 Network-On-Chip interconnect 10 - Barnabas Czeman <barnabas.czeman@mainlining.org> 13 The Qualcomm MSM8953 interconnect providers support adjusting the 16 See also: include/dt-bindings/interconnect/qcom,msm8953.h 21 - qcom,msm8953-bimc 22 - qcom,msm8953-pcnoc [all …]`
H A D	qcom,sc7180.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sc7180.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm SC7180 Network-On-Chip Interconnect 10 - Odelu Kukatla <okukatla@codeaurora.org> 13 SC7180 interconnect providers support system bandwidth requirements through 26 - qcom,sc7180-aggre1-noc 27 - qcom,sc7180-aggre2-noc 28 - qcom,sc7180-camnoc-virt [all …]`
H A D	qcom,sm7150-rpmh.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm7150-rpmh.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SM7150 10 - Danila Tikhonov <danila@jiaxyga.com> 13 RPMh interconnect providers support system bandwidth requirements through 16 See also:: include/dt-bindings/interconnect/qcom,sm7150-rpmh.h 19 - $ref: qcom,rpmh-common.yaml# 24 - qcom,sm7150-aggre1-noc [all …]
H A D	qcom,msm8916.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8916.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm MSM8916 Network-On-Chip interconnect 10 - Georgi Djakov <georgi.djakov@linaro.org> 13 The Qualcomm MSM8916 interconnect providers support adjusting the 19 - qcom,msm8916-bimc 20 - qcom,msm8916-pcnoc 21 - qcom,msm8916-snoc [all …]`
H A D	qcom,qcs404.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,qcs404.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm QCS404 Network-On-Chip interconnect 10 - Georgi Djakov <georgi.djakov@linaro.org> 13 The Qualcomm QCS404 interconnect providers support adjusting the 22 - qcom,qcs404-bimc 23 - qcom,qcs404-pcnoc 24 - qcom,qcs404-snoc [all …]`
H A D	qcom,sdm845.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sdm845.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm SDM845 Network-On-Chip Interconnect 10 - Georgi Djakov <georgi.djakov@linaro.org> 13 SDM845 interconnect providers support system bandwidth requirements through 26 - qcom,sdm845-aggre1-noc 27 - qcom,sdm845-aggre2-noc 28 - qcom,sdm845-config-noc [all …]`
H A D	qcom,sc7280-rpmh.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sc7280-rpmh.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SC7280 10 - Bjorn Andersson <andersson@kernel.org> 11 - Konrad Dybcio <konradybcio@kernel.org> 14 RPMh interconnect providers support system bandwidth requirements through 17 See also:: include/dt-bindings/interconnect/qcom,sc7280.h 22 - qcom,sc7280-aggre1-noc [all …]
H A D	qcom,msm8939.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8939.yaml# 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> 13 The Qualcomm MSM8937/MSM8939/MSM8976 interconnect providers support 17 - $ref: qcom,rpm-common.yaml# 22 - qcom,msm8937-bimc 23 - qcom,msm8937-pcnoc [all …]`
H A D	qcom,qdu1000-rpmh.yaml	`1 # 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> 14 RPMh interconnect providers support system bandwidth requirements through 24 - qcom,qdu1000-clk-virt 25 - qcom,qdu1000-gem-noc [all …]`
H A D	qcom,msm8974.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,msm8974.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm MSM8974 Network-On-Chip Interconnect 10 - Brian Masney <masneyb@onstation.org> 13 The Qualcomm MSM8974 interconnect providers support setting system 14 bandwidth requirements between various network-on-chip fabrics. 22 - qcom,msm8974-bimc 23 - qcom,msm8974-cnoc [all …]`
H A D	qcom,sm8450-rpmh.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm8450-rpmh.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SM8450 10 - Bjorn Andersson <andersson@kernel.org> 11 - Konrad Dybcio <konradybcio@kernel.org> 14 RPMh interconnect providers support system bandwidth requirements through 17 See also:: include/dt-bindings/interconnect/qcom,sm8450.h 22 - qcom,sm8450-aggre1-noc [all …]
H A D	qcom,osm-l3.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qco [all...]`
H A D	qcom,sm8550-rpmh.yaml	1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,sm8550-rpmh.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect on SM8550 10 - Abel Vesa <abel.vesa@linaro.org> 11 - Neil Armstrong <neil.armstrong@linaro.org> 14 RPMh interconnect providers support system bandwidth requirements through 21 See also:: include/dt-bindings/interconnect/qcom,sm8550-rpmh.h 26 - qcom,sm8550-aggre1-noc [all …]
H A D	qcom,rpmh-common.yaml	`1 # 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> 14 RPMh interconnect providers support system bandwidth requirements through 22 '#interconnect-cells': 25 qcom,bcm-voters: [all …]`
H A D	qcom,sc8280xp-rpmh.yaml	1 # 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> 14 RPMh interconnect providers support system bandwidth requirements through 17 See also:: include/dt-bindings/interconnect/qcom,sc8280xp.h 22 - qcom,sc8280xp-aggre1-noc [all …]
H A D	qcom,rpmh.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interconnect/qcom,rpmh.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm RPMh Network-On-Chip Interconnect 10 - Georgi Djakov <georgi.djakov@linaro.org> 11 - Odelu Kukatla <quic_okukatla@quicinc.com> 14 RPMh interconnect providers support system bandwidth requirements through 27 - qcom,sc7180-aggre1-noc 28 - qcom,sc7180-aggre2-noc [all …]`
/freebsd/sys/contrib/device-tree/Bindings/bus/
H A D	ti-sysc.txt	1 Texas Instruments sysc interconnect target module wrapper binding 3 Texas Instruments SoCs can have a generic interconnect target module 5 interconnect (Arteris NoC) and L4 interconnect (Sonics s3220). The sysc 8 of the interconnect. 10 Each interconnect target module can have one or more devices connected to 11 it. There is a set of control registers for managing interconnect target 12 module clocks, idle modes and interconnect level resets for the module. 15 space of the first child device IP block managed by the interconnect 20 - compatible shall be one of the following generic types: 23 "ti,sysc-omap2" [all …]
H A D	ti-sysc.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/bus/ti-sysc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Texas Instruments interconnect target module 10 - Tony Lindgren <tony@atomide.com> 13 Texas Instruments SoCs can have a generic interconnect target module 14 for devices connected to various interconnects such as L3 interconnect 15 using Arteris NoC, and L4 interconnect using Sonics s3220. This module 18 than that it is mostly independent of the interconnect. [all …]
H A D	baikal,bt1-axi.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/bus/baikal,bt1-axi.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Baikal-T1 AXI-bus 11 - Serge Semin <fancer.lancer@gmail.com> 14 AXI3-bus is the main communication bus of Baikal-T1 SoC connecting all 15 high-speed peripheral IP-cores with RAM controller and with MIPS P5600 16 cores. Traffic arbitration is done by means of DW AXI Interconnect (so 17 called AXI Main Interconnect) routing IO requests from one block to [all …]
/freebsd/sys/contrib/device-tree/Bindings/soc/imx/
H A D	fsl,imx8mm-vpu-blk-ctrl.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/imx/fsl,imx8mm-vpu-blk-ctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: NXP i.MX8MM VPU blk-ctrl 10 - Lucas Stach <l.stach@pengutronix.de> 13 The i.MX8MM VPU blk-ctrl is a top-level peripheral providing access to 20 - const: fsl,imx8mm-vpu-blk-ctrl 21 - const: syscon 26 '#power-domain-cells': [all …]`
/freebsd/sys/contrib/device-tree/Bindings/display/tegra/
H A D	nvidia,tegra20-host1x.txt	4 - compatible: "nvidia,tegra<chip>-host1x" 5 - reg: Physical base address and length of the controller's registers. 6 For pre-Tegra186, one entry describing the whole register area. 7 For Tegra186, one entry for each entry in reg-names: 8 "vm" - VM region assigned to Linux 9 "hypervisor" - Hypervisor region (only if Linux acts as hypervisor) 10 - interrupts: The interrupt outputs from the controller. 11 - #address-cells: The number of cells used to represent physical base addresses 13 - #size-cells: The number of cells used to represent the size of an address 15 - ranges: The mapping of the host1x address space to the CPU address space. [all …]

12 3 4 5 6 7 8 9 10 >>...14