Hi Mark,
> From: Mark Rutland
> [...]
>
> > 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?
>
Ok then I'll swap the [Patch 1/9] and [Patch 2/9] so that DT parsing updates
(with backward compatibility) happen before the deprecation of DT values.
This way old DT binding would work all through.
And as DT parsing is kept backward compatible, so .dts changes would not
break the DTBs even if updated in separate patch.
with regards, pekon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
