Hi,
Few comments below.
* Ivan Djelic <ivan.dje...@parrot.com> [120419 11:49]:
>
> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> index 00d5108..e3a91a1 100644
> --- a/arch/arm/mach-omap2/gpmc.c
> +++ b/arch/arm/mach-omap2/gpmc.c
> @@ -49,6 +49,7 @@
> #define GPMC_ECC_CONTROL 0x1f8
> #define GPMC_ECC_SIZE_CONFIG 0x1fc
> #define GPMC_ECC1_RESULT 0x200
> +#define GPMC_ECC_BCH_RESULT_0 0x240
Can you please add a comment here saying something like:
#define GPMC_ECC_BCH_RESULT_0 0x240 /* Not available on omap2 */
> @@ -920,3 +921,150 @@ int gpmc_calculate_ecc(int cs, const u_char *dat,
> u_char *ecc_code)
> return 0;
> }
> EXPORT_SYMBOL_GPL(gpmc_calculate_ecc);
> +
> +#ifdef CONFIG_ARCH_OMAP3
> +
> +/**
> + * gpmc_enable_hwecc_bch - enable hardware BCH ecc functionality
> + * @cs: chip select number
> + * @mode: read/write mode
> + * @dev_width: device bus width(1 for x16, 0 for x8)
> + * @nsectors: how many 512-byte sectors to process
> + * @nerrors: how many errors to correct per sector (4 or 8)
> + */
> +int gpmc_enable_hwecc_bch(int cs, int mode, int dev_width, int nsectors,
> + int nerrors)
> +{
> + unsigned int val;
> +
> + /* check if ecc module is in use */
> + if (gpmc_ecc_used != -EINVAL)
> + return -EINVAL;
> + /*
> + * FIXME: some OMAP3 revisions have a hardware bug which prevents
> + * the 4-bit BCH mode from working properly. Such revisions could be
> + * detected and rejected here.
> + */
This should then be disabled to avoid corruption. Maybe only allow it
initially on omaps that have been tested? And for omap2 it should return
error for sure.
Or do you know the broken omap3 versions?
Also, should you first request this feature in case multiple drivers
need to share it?
Other than that, looks good to me.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
