Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Thierry Reding <thierry.reding@gmail.com>
To:     Sumit Gupta <sumitg@nvidia.com>, linux-tegra@vger.kernel.org,
        linux-kernel@vger.kernel.org, jonathanh@nvidia.com
Cc:     bbasu@nvidia.com
Subject: Re: [Patch 1/4] soc/tegra: cbb: use correct master_id mask for cbb noc in Tegra194
Date:   Fri, 11 Nov 2022 15:41:30 +0100
Message-Id: <166817763540.519550.6000067127559043663.b4-ty@nvidia.com>
In-Reply-To: <20221109135717.3809-1-sumitg@nvidia.com>
References: <20221109135717.3809-1-sumitg@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

From: Thierry Reding <treding@nvidia.com>

On Wed, 9 Nov 2022 19:27:14 +0530, Sumit Gupta wrote:
> In Tegra194 SoC, master_id bit range is different between
> cluster NOC and CBB NOC. Currently same bit range is used
> which results in wrong master_id value. Due to this,
> illegal accesses from the CCPLEX master do not result in a
> crash as expected. Fix this by using the correct range for
> the CBB NOC.
> Finally, it is only necessary to extract the master_id when
> the erd_mask_inband_err flag is set because when this is not
> set, a crash is always triggered.
> 
> [...]

Applied, thanks!

[1/4] soc/tegra: cbb: use correct master_id mask for cbb noc in Tegra194
      (no commit info)
[2/4] soc/tegra: cbb: update slave maps for Tegra234
      (no commit info)
[3/4] soc/tegra: cbb: add checks for potential out of bound errors
      (no commit info)
[4/4] soc/tegra: cbb: check firewall before enabling error reporting
      (no commit info)

Best regards,
-- 
Thierry Reding <treding@nvidia.com>