linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pekon Gupta <pekon@ti.com>
Cc: linux-omap@vger.kernel.org, afzal@ti.com
Subject: Re: [PATCH 1/1] arm: omap: gpmc: remove detection of ecc-capability based on SoC name
Date: Thu, 14 Nov 2013 10:31:48 -0800	[thread overview]
Message-ID: <20131114183148.GK10317@atomide.com> (raw)
In-Reply-To: <1381859559-15281-1-git-send-email-pekon@ti.com>

* Pekon Gupta <pekon@ti.com> [131015 11:29]:
> Legacy OMAP SoC like OMAP2xxx, OMAP3xxx do not have in-build ELM h/w engine,
> so they cannot support h/w based BCH ECC error-detection. Thus,
> gpmc_hwecc_bch_capable() check was added in following commit to find-out
> which SoC have in-built ELM h/w to support hardware based ecc-correction.
> 
> commit 3852ccd66a9bcb2aa6f46bce5442b6d8d08e5b5d
> Author:     Afzal Mohammed <afzal@ti.com>
> AuthorDate: 2012-10-01
> 
> But with DT based kernel, presence of ELM h/w engine on SoC is parsed from DT
> data part of .dtsi file, which is unique for each device. Hence hard-coded
> check for each device can be dropped.

I don't think we can queue this yet as omap3 is not yet DT only?

Regards,

Tony
 
> Signed-off-by: Pekon Gupta <pekon@ti.com>
> ---
>  arch/arm/mach-omap2/gpmc-nand.c | 25 -------------------------
>  1 file changed, 25 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
> index 662c7fd..2b03eba 100644
> --- a/arch/arm/mach-omap2/gpmc-nand.c
> +++ b/arch/arm/mach-omap2/gpmc-nand.c
> @@ -43,28 +43,6 @@ static struct platform_device gpmc_nand_device = {
>  	.resource	= gpmc_nand_resource,
>  };
>  
> -static bool gpmc_hwecc_bch_capable(enum omap_ecc ecc_opt)
> -{
> -	/* support only OMAP3 class */
> -	if (!cpu_is_omap34xx() && !soc_is_am33xx()) {
> -		pr_err("BCH ecc is not supported on this CPU\n");
> -		return 0;
> -	}
> -
> -	/*
> -	 * For now, assume 4-bit mode is only supported on OMAP3630 ES1.x, x>=1
> -	 * and AM33xx derivates. Other chips may be added if confirmed to work.
> -	 */
> -	if ((ecc_opt == OMAP_ECC_BCH4_CODE_HW) &&
> -	    (!cpu_is_omap3630() || (GET_OMAP_REVISION() == 0)) &&
> -	    (!soc_is_am33xx())) {
> -		pr_err("BCH 4-bit mode is not supported on this CPU\n");
> -		return 0;
> -	}
> -
> -	return 1;
> -}
> -
>  int gpmc_nand_init(struct omap_nand_platform_data *gpmc_nand_data,
>  		   struct gpmc_timings *gpmc_t)
>  {
> @@ -127,9 +105,6 @@ int gpmc_nand_init(struct omap_nand_platform_data *gpmc_nand_data,
>  
>  	gpmc_update_nand_reg(&gpmc_nand_data->reg, gpmc_nand_data->cs);
>  
> -	if (!gpmc_hwecc_bch_capable(gpmc_nand_data->ecc_opt))
> -		return -EINVAL;
> -
>  	err = platform_device_register(&gpmc_nand_device);
>  	if (err < 0) {
>  		dev_err(dev, "Unable to register NAND device\n");
> -- 
> 1.8.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-11-14 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 17:52 [PATCH 1/1] arm: omap: gpmc: remove detection of ecc-capability based on SoC name Pekon Gupta
2013-11-14 18:31 ` 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=20131114183148.GK10317@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pekon@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 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).