From: Sumit Gupta <sumitg@nvidia.com> To: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <thierry.reding@gmail.com>, <jonathanh@nvidia.com>, <robh+dt@kernel.org>, <kbuild-all@lists.01.org> Cc: <sumitg@nvidia.com>, <bbasu@nvidia.com>, <vsethi@nvidia.com>, <jsequeira@nvidia.com>, Thierry Reding <treding@nvidia.com> Subject: [Patch v4 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding Date: Thu, 5 May 2022 22:36:31 +0530 [thread overview] Message-ID: <20220505170637.26538-4-sumitg@nvidia.com> (raw) In-Reply-To: <20220505170637.26538-1-sumitg@nvidia.com> Add device-tree binding documentation to represent the axi2apb bridges used by Control Backbone (CBB) 1.0 in Tegra194 SOC. All errors for APB slaves are reported as slave error because APB bas single bit to report error. So, CBB driver needs to further check error status registers of all the axi2apb bridges to find error type. Signed-off-by: Sumit Gupta <sumitg@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com> --- .../arm/tegra/nvidia,tegra194-axi2apb.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml new file mode 100644 index 000000000000..788a13f8aa93 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml @@ -0,0 +1,40 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/arm/tegra/nvidia,tegra194-axi2apb.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: NVIDIA Tegra194 AXI2APB bridge + +maintainers: + - Sumit Gupta <sumitg@nvidia.com> + +properties: + $nodename: + pattern: "^axi2apb@([0-9a-f]+)$" + + compatible: + enum: + - nvidia,tegra194-axi2apb + + reg: + maxItems: 6 + description: Physical base address and length of registers for all bridges + +additionalProperties: false + +required: + - compatible + - reg + +examples: + - | + axi2apb: axi2apb@2390000 { + compatible = "nvidia,tegra194-axi2apb"; + reg = <0x02390000 0x1000>, + <0x023a0000 0x1000>, + <0x023b0000 0x1000>, + <0x023c0000 0x1000>, + <0x023d0000 0x1000>, + <0x023e0000 0x1000>; + }; -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Gupta <sumitg@nvidia.com> To: kbuild-all@lists.01.org Subject: [Patch v4 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding Date: Thu, 05 May 2022 22:36:31 +0530 [thread overview] Message-ID: <20220505170637.26538-4-sumitg@nvidia.com> (raw) In-Reply-To: <20220505170637.26538-1-sumitg@nvidia.com> [-- Attachment #1: Type: text/plain, Size: 1951 bytes --] Add device-tree binding documentation to represent the axi2apb bridges used by Control Backbone (CBB) 1.0 in Tegra194 SOC. All errors for APB slaves are reported as slave error because APB bas single bit to report error. So, CBB driver needs to further check error status registers of all the axi2apb bridges to find error type. Signed-off-by: Sumit Gupta <sumitg@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com> --- .../arm/tegra/nvidia,tegra194-axi2apb.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml new file mode 100644 index 000000000000..788a13f8aa93 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra194-axi2apb.yaml @@ -0,0 +1,40 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/arm/tegra/nvidia,tegra194-axi2apb.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: NVIDIA Tegra194 AXI2APB bridge + +maintainers: + - Sumit Gupta <sumitg@nvidia.com> + +properties: + $nodename: + pattern: "^axi2apb@([0-9a-f]+)$" + + compatible: + enum: + - nvidia,tegra194-axi2apb + + reg: + maxItems: 6 + description: Physical base address and length of registers for all bridges + +additionalProperties: false + +required: + - compatible + - reg + +examples: + - | + axi2apb: axi2apb(a)2390000 { + compatible = "nvidia,tegra194-axi2apb"; + reg = <0x02390000 0x1000>, + <0x023a0000 0x1000>, + <0x023b0000 0x1000>, + <0x023c0000 0x1000>, + <0x023d0000 0x1000>, + <0x023e0000 0x1000>; + }; -- 2.17.1
next prev parent reply other threads:[~2022-05-05 17:07 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-05 17:06 [Patch v4 0/9] CBB driver for Tegra194, Tegra234 & Tegra-Grace Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 1/9] soc: tegra: set ERD bit to mask inband errors Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 2/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 CBB1.0 binding Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta [this message] 2022-05-05 17:06 ` [Patch v4 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding Sumit Gupta 2022-05-05 17:06 ` [Patch v4 4/9] arm64: tegra: Add node for CBB1.0 in Tegra194 SOC Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 5/9] soc: tegra: cbb: Add CBB1.0 driver for Tegra194 Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 6/9] dt-bindings: arm: tegra: Add NVIDIA Tegra234 CBB2.0 binding Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 7/9] arm64: tegra: Add node for CBB2.0 in Tegra234 SOC Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 8/9] soc: tegra: cbb: Add driver for Tegra234 CBB2.0 Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-05 17:06 ` [Patch v4 9/9] soc: tegra: cbb: Add support for tegra-grace SOC Sumit Gupta 2022-05-05 17:06 ` Sumit Gupta 2022-05-06 4:22 ` kernel test robot 2022-05-09 10:37 ` Sumit Gupta 2022-05-09 10:37 ` Sumit Gupta
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220505170637.26538-4-sumitg@nvidia.com \ --to=sumitg@nvidia.com \ --cc=bbasu@nvidia.com \ --cc=devicetree@vger.kernel.org \ --cc=jonathanh@nvidia.com \ --cc=jsequeira@nvidia.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.com \ --cc=treding@nvidia.com \ --cc=vsethi@nvidia.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.