[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89f20af4-de3a-01be-baff-014bcca9df82@nvidia.com>
Date: Wed, 19 Jan 2022 14:39:37 +0530
From: Ashish Mhetre <amhetre@...dia.com>
To: Dmitry Osipenko <digetx@...il.com>, <thierry.reding@...il.com>,
<jonathanh@...dia.com>, <linux-tegra@...r.kernel.org>,
<krzysztof.kozlowski@...onical.com>, <linux-kernel@...r.kernel.org>
CC: <Snikam@...dia.com>, <vdumpa@...dia.com>
Subject: Re: [Patch V1 3/4] memory: tegra: add mc-err support for T186
On 1/12/2022 4:54 PM, Dmitry Osipenko wrote:
> External email: Use caution opening links or attachments
>
>
> 12.01.2022 14:22, Dmitry Osipenko пишет:
>> 11.01.2022 21:45, Ashish Mhetre пишет:
>>> #define MC_INT_DECERR_ROUTE_SANITY BIT(20)
>>> #define MC_INT_WCAM_ERR BIT(19)
>>> #define MC_INT_SCRUB_ECC_WR_ACK BIT(18)
>>
>> I don't see where these errors are handled in the code. Is documentation
>> that explains these bits publicly available?
>>
MC_INT_DECERR_ROUTE_SANITY is supposed to be part a of Tegra194
interrupts. I have missed adding it and will update in next version.
MC_INT_WCAM_ERR is a MC channel error and is not applicable in upstream.
I'll remove it.
These bits are defined in same documentation where other errors are
defined.
>
> MC_INT_SCRUB_ECC_WR_ACK shouldn't be a error.
Okay, I 'll remove it.
Powered by blists - more mailing lists