From: Borislav Petkov <bp@alien8.de>
To: "Shenhar, Talel" <talel@amazon.com>
Cc: krzysztof.kozlowski@linaro.org, talelshenhar@gmail.com,
shellykz@amazon.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: RFC on drivers/memory vs drivers/edac memory mapping for DDR Controller
Date: Mon, 2 Jan 2023 14:43:32 +0100 [thread overview]
Message-ID: <Y7LfhB5IrLcFzPOi@zn.tnic> (raw)
In-Reply-To: <2511c7aa-8ce6-a803-a1ea-6121df79c677@amazon.com>
On Mon, Jan 02, 2023 at 02:17:24PM +0200, Shenhar, Talel wrote:
> * We want to introduce driver that reads DDR controller RAS register and
> notify for ECC errors by using EDAC MC API found in drivers/edac.
> * We also want to have a capability to dynamically change DDR refresh rate
> based on thermal values (best to be done in drivers/memory ?).
Is there any particular reason to want to report the errors through EDAC?
Or can't you simply read the RAS register in your memory driver and dump error
info from there so that you have a single driver that does it all?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-02 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 12:17 RFC on drivers/memory vs drivers/edac memory mapping for DDR Controller Shenhar, Talel
2023-01-02 12:47 ` Krzysztof Kozlowski
2023-01-02 13:44 ` Shenhar, Talel
2023-01-02 13:59 ` Krzysztof Kozlowski
2023-01-02 16:21 ` Shenhar, Talel
2023-01-02 16:25 ` Krzysztof Kozlowski
2023-01-03 13:12 ` Shenhar, Talel
2023-01-03 13:23 ` Krzysztof Kozlowski
2023-01-03 13:47 ` Shenhar, Talel
2023-01-03 14:02 ` Krzysztof Kozlowski
2023-01-03 14:24 ` Krzysztof Kozlowski
2023-01-03 14:34 ` Shenhar, Talel
2023-01-02 13:43 ` Borislav Petkov [this message]
2023-01-02 16:14 ` Shenhar, Talel
2023-01-02 16:23 ` Borislav Petkov
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=Y7LfhB5IrLcFzPOi@zn.tnic \
--to=bp@alien8.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shellykz@amazon.com \
--cc=talel@amazon.com \
--cc=talelshenhar@gmail.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