Hi Pekon,

On Tue, Oct 15, 2013 at 06:49:49AM +0100, Pekon Gupta wrote:
> OMAP NAND driver currently supports multiple flavours of 1-bit Hamming
> ecc-scheme, like:
> - OMAP_ECC_HAMMING_CODE_DEFAULT
>       1-bit hamming ecc code using software library
> - OMAP_ECC_HAMMING_CODE_HW
>       1-bit hamming ecc-code using GPMC h/w engine
> - OMAP_ECC_HAMMING_CODE_HW_ROMCODE
>       1-bit hamming ecc-code using GPMC h/w engin with ecc-layout compatible
>       to ROM code.
> 
> This patch combines above multiple ecc-schemes into single implementation:
> - OMAP_ECC_HAM1_CODE_HW
>       1-bit hamming ecc-code using GPMC h/w engine with ROM-code compatible
>       ecc-layout.
> 
> Signed-off-by: Pekon Gupta <[email protected]>
> Reviewed-by: Felipe Balbi <[email protected]>
> Acked-by: Tony Lindgren <[email protected]>
> ---
>  Documentation/devicetree/bindings/mtd/gpmc-nand.txt | 8 ++++----
>  arch/arm/mach-omap2/board-flash.c                   | 2 +-
>  arch/arm/mach-omap2/gpmc.c                          | 4 +---
>  drivers/mtd/nand/omap2.c                            | 9 +++------
>  include/linux/platform_data/mtd-nand-omap2.h        | 6 +-----
>  5 files changed, 10 insertions(+), 19 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt 
> b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> index df338cb..25ee232 100644
> --- a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> +++ b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> @@ -22,10 +22,10 @@ Optional properties:
>                               width of 8 is assumed.
>  
>   - ti,nand-ecc-opt:          A string setting the ECC layout to use. One of:
> -
> -             "sw"            Software method (default)
> -             "hw"            Hardware method
> -             "hw-romcode"    gpmc hamming mode method & romcode layout
> +             "sw"            <deprecated> use "ham1" instead
> +             "hw"            <deprecated> use "ham1" instead
> +             "hw-romcode"    <deprecated> use "ham1" instead
> +             "ham1"          1-bit Hamming ecc code
>               "bch4"          4-bit BCH ecc code
>               "bch8"          8-bit BCH ecc code

[...]

> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> index 579697a..c9fb353 100644
> --- a/arch/arm/mach-omap2/gpmc.c
> +++ b/arch/arm/mach-omap2/gpmc.c
> @@ -1342,9 +1342,7 @@ static void __maybe_unused gpmc_read_timings_dt(struct 
> device_node *np,
>  #ifdef CONFIG_MTD_NAND
>  
>  static const char * const nand_ecc_opts[] = {
> -     [OMAP_ECC_HAMMING_CODE_DEFAULT]         = "sw",
> -     [OMAP_ECC_HAMMING_CODE_HW]              = "hw",
> -     [OMAP_ECC_HAMMING_CODE_HW_ROMCODE]      = "hw-romcode",
> +     [OMAP_ECC_HAM1_CODE_HW]                 = "ham1",
>       [OMAP_ECC_BCH4_CODE_HW]                 = "bch4",
>       [OMAP_ECC_BCH8_CODE_HW]                 = "bch8",
>  };

As the parsing isn't updated until the next patch, doesn't this
temporarily break DTBs with the deprecated ti,nand-ecc-opt values?

Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to