devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: devicetree@vger.kernel.org, kbuild-all@lists.01.org,
	linux-tegra@vger.kernel.org, Thierry Reding <treding@nvidia.com>,
	jsequeira@nvidia.com, bbasu@nvidia.com,
	linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
	robh+dt@kernel.org, vsethi@nvidia.com, jonathanh@nvidia.com
Subject: Re: [Patch v5 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding
Date: Wed, 11 May 2022 09:47:31 -0500	[thread overview]
Message-ID: <20220511144731.GA286675-robh@kernel.org> (raw)
In-Reply-To: <20220506111217.8833-4-sumitg@nvidia.com>

On Fri, 06 May 2022 16:42:11 +0530, Sumit Gupta wrote:
> 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
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-05-11 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 11:12 [Patch v5 0/9] CBB driver for Tegra194, Tegra234 & Tegra-Grace Sumit Gupta
2022-05-06 11:12 ` [Patch v5 1/9] soc: tegra: set ERD bit to mask inband errors Sumit Gupta
2022-05-06 11:12 ` [Patch v5 2/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 CBB1.0 binding Sumit Gupta
2022-05-11 14:46   ` Rob Herring
2022-05-11 16:12     ` Sumit Gupta
2022-05-06 11:12 ` [Patch v5 3/9] dt-bindings: arm: tegra: Add NVIDIA Tegra194 axi2apb binding Sumit Gupta
2022-05-11 14:47   ` Rob Herring [this message]
2022-05-06 11:12 ` [Patch v5 4/9] arm64: tegra: Add node for CBB1.0 in Tegra194 SOC Sumit Gupta
2022-05-06 11:12 ` [Patch v5 5/9] soc: tegra: cbb: Add CBB1.0 driver for Tegra194 Sumit Gupta
2022-05-06 11:12 ` [Patch v5 6/9] dt-bindings: arm: tegra: Add NVIDIA Tegra234 CBB2.0 binding Sumit Gupta
2022-05-11 14:49   ` Rob Herring
2022-05-11 16:14     ` Sumit Gupta
2022-05-06 11:12 ` [Patch v5 7/9] arm64: tegra: Add node for CBB2.0 in Tegra234 SOC Sumit Gupta
2022-05-06 11:12 ` [Patch v5 8/9] soc: tegra: cbb: Add driver for Tegra234 CBB2.0 Sumit Gupta
2022-05-06 11:12 ` [Patch v5 9/9] soc: tegra: cbb: Add support for tegra-grace SOC 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=20220511144731.GA286675-robh@kernel.org \
    --to=robh@kernel.org \
    --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=sumitg@nvidia.com \
    --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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).