[U-Boot] [PATCH] Flex-OneNAND driver

[Rohit]

Hi,

Kyungmin Park wrote:
>> Why?  If it's dynamic changes to the boundary that concern you, you could
>> tear down the device(s) and re-initialize.
> 
> Okay consider that add reset or reprobe command to do this
> 
We can expose Flex-OneNAND as a SLC device and a MLC device by having
two mtd_info structures. The difference between the two devices is block size only.

 1. This makes user aware of SLC and MLC areas.
 2. We expose two devices where as there is a single physical device.
    Also, MTD provides erase regions capability for such devices ie which
    have many erase regions.

Exposing as two devices reduces code by removing code for erase regions, but only little.
Also other support for Flex-OneNAND is still needed ie
- all 4KB dataram is used during read/write.
- read/write oob-only commands are not present.
- LSB recovery for MLC area read failure
- 4 ecc registers

>> Of course, I may simply be missing something about how this hardware works.
>>
>>> Also, comments from MTD mailing list have been included.
>> If this is going to go into Linux, perhaps we should wait until it is merged
>> there and then import the result?
> 
> It's almost done and wait to merge into MTD tree.
> As I mentioned. First merge MTD tree and then U-Boot tree.
> 
>> At least, I'd like Kyungmin Park's ack for OneNAND stuff.
> 
> Basically I acked this patch.

I'll repost after MTD merge.

Thanks,
Rohit