[PATCH v2] MTD: modify mtd api to return bitflip info on read operations
Mike Dunn
mikedunn at newsguy.com
Mon Dec 5 11:58:40 EST 2011
On 12/04/2011 10:07 PM, Artem Bityutskiy wrote:
> On Sun, 2011-12-04 at 06:55 -0800, Mike Dunn wrote:
>> So you're thinking that the driver would supply both ecc_strength and
>> "scrublevel" (or maybe bb_threshold)? Would these go into struct mtd_info?
> Probably yes. After all, UBI has no idea about what kind of flash is
> that and what kind of ECC it uses and what bit-flip level needs
> scrubbing. So I think this kind of information should come from the
> driver or from the user via mtd sysfs files. What do you think?
I'm not a flash expert, but that sounds reasonable, especially if the scrublevel
parameter is optional, with UBI using ecc_strength as the default value. As for
how to pass the parameter, sysfs might be a good idea for scrublevel, allowing
it to be tunable without having to modify the driver if experience show that the
driver author's original assumptions about how a block degrades were incorrect.
Thanks,
Mike
More information about the linux-mtd
mailing list