From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] EDAC: Add AMD Seattle SoC EDAC
Date: Tue, 20 Oct 2015 19:36:39 +0200 [thread overview]
Message-ID: <20151020173639.GH31130@pd.tnic> (raw)
In-Reply-To: <20151020172654.GC4943@leverpostej>
On Tue, Oct 20, 2015 at 06:26:55PM +0100, Mark Rutland wrote:
> > Btw, how much of this is implementing generic A57 functionality?
>
> The driver is entirely A57 generic.
>
> > If a lot, can we make this a generic a57_edac driver so that multiple
> > vendors can use it?
>
> Yes.
Ok, cool.
> > How fast and how ugly can something like that become?
>
> Not sure I follow.
In the sense that some vendor might require just a little bit different
handling or maybe wants to read some vendor-specific registers in
addition to the architectural ones.
Then we'll start adding vendor-specific hacks to that generic driver.
And therefore the question how fast and how ugly such hacks would
become.
I guess we'll worry about that when we get there...
So Brijesh, if you only need generic, architectural functionality,
please call it arm64_edac or so and let's add it so that other arm64
vendors can use it too.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Brijesh Singh <brijeshkumar.singh@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
dougthompson@xmission.com, mchehab@osg.samsung.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] EDAC: Add AMD Seattle SoC EDAC
Date: Tue, 20 Oct 2015 19:36:39 +0200 [thread overview]
Message-ID: <20151020173639.GH31130@pd.tnic> (raw)
In-Reply-To: <20151020172654.GC4943@leverpostej>
On Tue, Oct 20, 2015 at 06:26:55PM +0100, Mark Rutland wrote:
> > Btw, how much of this is implementing generic A57 functionality?
>
> The driver is entirely A57 generic.
>
> > If a lot, can we make this a generic a57_edac driver so that multiple
> > vendors can use it?
>
> Yes.
Ok, cool.
> > How fast and how ugly can something like that become?
>
> Not sure I follow.
In the sense that some vendor might require just a little bit different
handling or maybe wants to read some vendor-specific registers in
addition to the architectural ones.
Then we'll start adding vendor-specific hacks to that generic driver.
And therefore the question how fast and how ugly such hacks would
become.
I guess we'll worry about that when we get there...
So Brijesh, if you only need generic, architectural functionality,
please call it arm64_edac or so and let's add it so that other arm64
vendors can use it too.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-10-20 17:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:23 [PATCH] EDAC: Add AMD Seattle SoC EDAC Brijesh Singh
2015-10-19 19:23 ` Brijesh Singh
2015-10-19 20:14 ` Borislav Petkov
2015-10-19 20:14 ` Borislav Petkov
2015-10-19 20:52 ` Mark Rutland
2015-10-19 20:52 ` Mark Rutland
2015-10-20 16:44 ` Brijesh Singh
2015-10-20 16:44 ` Brijesh Singh
2015-10-20 16:44 ` Brijesh Singh
2015-10-20 16:57 ` Borislav Petkov
2015-10-20 16:57 ` Borislav Petkov
2015-10-20 16:57 ` Borislav Petkov
2015-10-20 17:26 ` Mark Rutland
2015-10-20 17:26 ` Mark Rutland
2015-10-20 17:26 ` Mark Rutland
2015-10-20 17:36 ` Borislav Petkov [this message]
2015-10-20 17:36 ` Borislav Petkov
2015-10-20 17:41 ` Mark Rutland
2015-10-20 17:41 ` Mark Rutland
2015-10-20 17:41 ` Mark Rutland
2015-10-20 19:16 ` Brijesh Singh
2015-10-20 19:16 ` Brijesh Singh
2015-10-20 19:16 ` Brijesh Singh
2015-10-21 1:55 ` Hanjun Guo
2015-10-21 1:55 ` Hanjun Guo
2015-10-21 1:55 ` Hanjun Guo
2015-10-21 9:35 ` Borislav Petkov
2015-10-21 9:35 ` Borislav Petkov
2015-10-21 9:35 ` Borislav Petkov
2015-10-21 10:01 ` Andre Przywara
2015-10-21 10:01 ` Andre Przywara
2015-10-21 10:01 ` Andre Przywara
2015-10-21 16:22 ` Brijesh Singh
2015-10-21 16:22 ` Brijesh Singh
2015-10-21 16:22 ` Brijesh Singh
2015-10-23 1:38 ` Hanjun Guo
2015-10-23 1:38 ` Hanjun Guo
2015-10-23 1:38 ` Hanjun Guo
2015-10-20 17:25 ` Mark Rutland
2015-10-20 17:25 ` Mark Rutland
2015-10-20 17:25 ` Mark Rutland
2015-10-21 1:45 ` Hanjun Guo
2015-10-21 1:45 ` Hanjun Guo
2015-10-21 1:45 ` Hanjun Guo
2015-10-20 2:21 ` Hanjun Guo
2015-10-20 2:21 ` Hanjun Guo
2015-10-20 21:26 ` Brijesh Singh
2015-10-20 21:26 ` Brijesh Singh
2015-10-21 1:35 ` Hanjun Guo
2015-10-21 1:35 ` Hanjun Guo
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=20151020173639.GH31130@pd.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.