* Felipe Balbi <balbi@xxxxxx> [131011 09:03]: > On Fri, Oct 11, 2013 at 07:06:39PM +0530, Pekon Gupta wrote: > > OMAP NAND driver support multiple ECC scheme, which can used in following > > different flavours, depending on in-build Hardware engines supported by SoC. > > > > +---------------------------------------+---------------+---------------+ > > | ECC scheme |ECC calculation|Error detection| > > +---------------------------------------+---------------+---------------+ > > |OMAP_ECC_HAM1_CODE_HW |H/W (GPMC) |S/W | > > +---------------------------------------+---------------+---------------+ > > |OMAP_ECC_BCH8_CODE_HW_DETECTION_SW |H/W (GPMC) |S/W | > > |(requires CONFIG_MTD_NAND_ECC_BCH) | | | > > +---------------------------------------+---------------+---------------+ > > |OMAP_ECC_BCH8_CODE_HW |H/W (GPMC) |H/W (ELM) | > > |(requires CONFIG_MTD_NAND_OMAP_BCH && | | | > > | ti,elm-id in DT) | | | > > +---------------------------------------+---------------+---------------+ > > To optimize footprint of omap2-nand driver, selection of some ECC schemes > > also require enabling following Kconfigs, in addition to setting appropriate > > DT bindings > > - Kconfig:CONFIG_MTD_NAND_ECC_BCH error detection done in software > > - Kconfig:CONFIG_MTD_NAND_OMAP_BCH error detection done by h/w engine > > > > DT binding updates in this patch are: > > - ti,elm-id: replaces elm_id > > - ti,nand-ecc-opts: supported values ham1, bch4, and bch8 > > selection of h/w or s/w implementation depends on ti,elm-id > > > > Signed-off-by: Pekon Gupta <pekon@xxxxxx> > > since this maintains backwards compatibility, I think it should be > alright to apply > > Reviewed-by: Felipe Balbi <balbi@xxxxxx> This patch looks safe to queue via the MTD tree for the arch/arm/*omap* parts in this patch: Acked-by: Tony Lindgren <tony@xxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
