[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dde86fec-ca92-a2a9-2d63-42c33c8594b0@amazon.com>
Date: Sun, 22 Sep 2019 09:55:36 +0300
From: "Shenhar, Talel" <talel@...zon.com>
To: James Morse <james.morse@....com>
CC: Marc Zyngier <maz@...nel.org>, <robh+dt@...nel.org>,
<tglx@...utronix.de>, <jason@...edaemon.net>,
<mark.rutland@....com>, <nicolas.ferre@...rochip.com>,
<mchehab+samsung@...nel.org>, <shawn.lin@...k-chips.com>,
<gregkh@...uxfoundation.org>, <dwmw@...zon.co.uk>,
<benh@...nel.crashing.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>
Subject: Re: [UNVERIFIED SENDER] Re: [UNVERIFIED SENDER] Re: [PATCH v2 2/3]
soc: amazon: al-pos: Introduce Amazon's Annapurna Labs POS driver
On 9/19/2019 5:42 PM, James Morse wrote:
> Hi guys,
>
> On 12/09/2019 10:19, Shenhar, Talel wrote:
>> On 9/12/2019 11:50 AM, Marc Zyngier wrote:
>>> On Thu, 12 Sep 2019 07:50:03 +0100,
>>> "Shenhar, Talel" <talel@...zon.com> wrote:
>>>> On 9/11/2019 5:15 PM, Marc Zyngier wrote:
>>>>> On Tue, 10 Sep 2019 20:05:09 +0100,
>>>>> Talel Shenhar <talel@...zon.com> wrote:
>>>>>
>> James, will love your input from EDAC point of view, does it make sense to plug
>> un-correctable only event to EDAC?
> I think this device is an example of something like a "Fabric switch units" in
> Documentation/driver-api/edac.rst. It makes sense that it should be described as a
> 'device' to edac. You can then use the existing user-space tools to control/report/monitor
> the values.
Thank you James,
Will port this logic to be edac device.
>
>
> Thanks,
>
> James
Powered by blists - more mailing lists