Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tero Kristo <t-kristo@ti.com>
Cc: mchehab@kernel.org, tony@atomide.com, ssantosh@kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-edac@vger.kernel.org
Subject: Re: [PATCHv3 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC
Date: Mon, 27 Nov 2017 14:12:22 +0100	[thread overview]
Message-ID: <20171127131222.gr6pofces6fts3iv@pd.tnic> (raw)
In-Reply-To: <1510578490-14510-1-git-send-email-t-kristo@ti.com>

On Mon, Nov 13, 2017 at 03:08:10PM +0200, Tero Kristo wrote:
> TI Keystone and DRA7xx SoCs have support for EDAC on DDR3 memory that can
> correct one bit errors and detect two bit errors. Add EDAC driver for this
> feature which plugs into the generic kernel EDAC framework.
> 
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> v3:
>  * dropped the atomic edac_id counter
>  * added _emif_get_id which calculates the emif ID based on the sorted
>    address order of all emif instances
>  * changed the order of irq allocation and edac_mc_add_mc() within probe
> 
> v2:
>  * fixed checkpatch errors
>  * improved error cleanup for failed probe
>  * converted to use edac_printk
>  * added MAINTAINERS entry
>  * dropped mutex and used atomic counter for ID
>  * ... and some minor cosmetic changes
>  
>  MAINTAINERS            |   6 +
>  drivers/edac/Kconfig   |   7 +
>  drivers/edac/Makefile  |   1 +
>  drivers/edac/ti_edac.c | 340 +++++++++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 354 insertions(+)
>  create mode 100644 drivers/edac/ti_edac.c

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  parent reply	other threads:[~2017-11-27 13:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 20:38 [PATCH 0/3] EDAC: TI: add support for DRA7 and keystone EDAC Tero Kristo
2017-11-07 20:38 ` [PATCH 1/3] Documentation: dt: memory: ti-emif: add edac support under emif Tero Kristo
2017-11-10  8:25   ` [PATCHv2 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC Tero Kristo
2017-11-11 10:46     ` Borislav Petkov
2017-11-13  9:03       ` Tero Kristo
     [not found]   ` <1510087139-21885-2-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2017-12-07  9:03     ` [PATCH 1/3] Documentation: dt: memory: ti-emif: add edac support under emif Tero Kristo
2017-11-07 20:38 ` [PATCH 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC Tero Kristo
2017-11-09 10:14   ` Borislav Petkov
2017-11-09 10:38     ` Tero Kristo
2017-11-09 12:12       ` Borislav Petkov
2017-11-09 11:50   ` Jan Lübbe
2017-11-09 12:40     ` Tero Kristo
2017-11-13 13:08   ` [PATCHv3 " Tero Kristo
2017-11-13 17:10     ` Santosh Shilimkar
2017-11-13 17:58       ` Borislav Petkov
2017-11-13 18:04         ` Santosh Shilimkar
2017-11-13 18:08           ` Borislav Petkov
2017-11-13 18:49             ` Tero Kristo
2017-11-13 19:17               ` Santosh Shilimkar
2017-11-27 13:12     ` Borislav Petkov [this message]
2017-11-07 20:38 ` [PATCH 3/3] ARM: dts: Keystone: add ECC error handler support Tero Kristo

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=20171127131222.gr6pofces6fts3iv@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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