[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd90ba80-9aac-e406-9066-64e975e5b10b@broadcom.com>
Date: Mon, 9 Dec 2019 10:02:53 -0800
From: Ray Jui <ray.jui@...adcom.com>
To: Marc Zyngier <maz@...nel.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
Rayagonda Kokatanur <rayagonda.kokatanur@...adcom.com>,
linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/2] Add iProc IDM device support
On 12/7/19 9:39 AM, Marc Zyngier wrote:
> On Mon, 2 Dec 2019 15:31:25 -0800
> Ray Jui <ray.jui@...adcom.com> wrote:
>
>> The Broadcom iProc IDM device allows control and monitoring of ASIC internal
>> bus transactions. Most importantly, it can be configured to detect bus
>> transaction timeout. In such case, critical information such as transaction
>> address that caused the error, bus master ID of the transaction that caused
>> the error, and etc., are made available from the IDM device.
>
> This seems to have many of the features of an EDAC device reporting
> uncorrectable errors.
>
> Is there any reason why it is not implemented as such?
>
> Thanks,
>
> M.
>
I thought EDAC errors (in fact, in our case, that's fatal rather than
uncorrectable) are mostly for DDR. Is my understanding incorrect?
Thanks,
Ray
Powered by blists - more mailing lists