From: Tony Lindgren <tony@atomide.com>
To: Pekon Gupta <pekon@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] ARM: OMAP2+: gpmc: enable BCH_HW ecc-scheme for AM43xx platforms
Date: Tue, 27 May 2014 14:22:58 -0700 [thread overview]
Message-ID: <20140527212257.GH32336@atomide.com> (raw)
In-Reply-To: <1400498556-24005-1-git-send-email-pekon@ti.com>
* Pekon Gupta <pekon@ti.com> [140519 04:23]:
> Fixes: commit 0611c41934ab35ce84dea34ab291897ad3cbc7be
> ARM: OMAP2+: gpmc: update gpmc_hwecc_bch_capable() for new platforms and ECC schemes
>
> Though the commit log of above commit mentions AM43xx platforms, but code change
> missed AM43xx. This patch adds AM43xx to list of those SoC which have built-in
> ELM hardware engine, so that BCH ecc-schemes with hardware error-correction can
> be enabled on AM43xx devices.
>
> Reported-by: Roger Quadros <rogerq@ti.com>
> Signed-off-by: Pekon Gupta <pekon@ti.com>
Applying into omap-for-v3.16/dt-v2 thanks.
Tony
> ---
> arch/arm/mach-omap2/gpmc-nand.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
> index 4349e82..17cd393 100644
> --- a/arch/arm/mach-omap2/gpmc-nand.c
> +++ b/arch/arm/mach-omap2/gpmc-nand.c
> @@ -46,7 +46,7 @@ static struct platform_device gpmc_nand_device = {
> static bool gpmc_hwecc_bch_capable(enum omap_ecc ecc_opt)
> {
> /* platforms which support all ECC schemes */
> - if (soc_is_am33xx() || cpu_is_omap44xx() ||
> + if (soc_is_am33xx() || soc_is_am43xx() || cpu_is_omap44xx() ||
> soc_is_omap54xx() || soc_is_dra7xx())
> return 1;
>
> --
> 1.8.5.1.163.gd7aced9
>
prev parent reply other threads:[~2014-05-27 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 11:22 [PATCH] ARM: OMAP2+: gpmc: enable BCH_HW ecc-scheme for AM43xx platforms Pekon Gupta
2014-05-27 21:22 ` Tony Lindgren [this message]
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=20140527212257.GH32336@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.com \
--cc=rogerq@ti.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 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.