From: Borislav Petkov <bp@alien8.de>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Michal Simek <monstr@monstr.eu>,
Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>,
dougthompson@xmission.com, linux-edac@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net, sorenb@xilinx.com, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kpc528@gmail.com,
kalluripunnaiahchoudary@gmail.com, punnaia@xilinx.com
Subject: Re: [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller
Date: Thu, 10 Apr 2014 12:00:47 +0200 [thread overview]
Message-ID: <20140410100047.GG29093@pd.tnic> (raw)
In-Reply-To: <5e0042b6-f169-4025-8fd7-9d70c2ed0cf6@AM1EHSMHS012.ehs.local>
On Thu, Apr 10, 2014 at 11:49:57AM +0200, Michal Simek wrote:
> I agree with you that we can use shorter name. I have checked this
> with Punnaiah and I can't see any problem to have more edac drivers
> in the system. For zynq there is primary ddr controller which is
> target by this driver. Then we are talking about L2 in another thread.
> Because zynq has programmable logic next to chip where you can add
> soft memory controller (we have these hw designs) on the same bus then
> there could be others edac drivers. I would say how many you like till
> pins on the package.
I knew you were gonna say something like that! :-)
Then you'll have to check whether edac can even stomach more than one
drivers in parallel. TTBOMK, no one has ever done this so far... Yadda
yadda.
But before you do all that, you need to check whether edac is really
what you're looking for, as I put it in my other mail.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-04-10 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:23 [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller Punnaiah Choudary Kalluri
2014-04-03 15:00 ` Michal Simek
2014-04-08 20:40 ` Borislav Petkov
[not found] ` <20140408204047.GQ30077-fF5Pk5pvG8Y@public.gmane.org>
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 11:03 ` Borislav Petkov
2014-04-09 17:45 ` punnaiah choudary kalluri
2014-04-09 17:48 ` Borislav Petkov
2014-04-10 6:01 ` Michal Simek
2014-04-10 9:21 ` Borislav Petkov
2014-04-10 9:49 ` Michal Simek
2014-04-10 10:00 ` Borislav Petkov [this message]
2014-04-10 10:05 ` Borislav Petkov
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
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=20140410100047.GG29093@pd.tnic \
--to=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=dougthompson@xmission.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kalluripunnaiahchoudary@gmail.com \
--cc=kpc528@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=pawel.moll@arm.com \
--cc=punnaia@xilinx.com \
--cc=punnaiah.choudary.kalluri@xilinx.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=sorenb@xilinx.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).