Micron NAND Rev D: initial reset

Micron NAND Rev D: initial reset

[Peter Ma]

Hi, there...

I am trying to add mtd/nand driver support for the Micron MT29F2G08AADWP
(Revision D) on 2.6.26.  

According to Micron, the difference (aside from ID code) between Rev D and
the popular Rev C, is that the Rev D requires a RESET command to be issued
after power-up and before any other command is issued.

I am just diving into the nand driver, but I thought I would ask if there is
a good place to issue that RESET after power-up.

I do not see a specific "nand_reset()" function in nand_base.c  I assume I
need to create this function, then have it called within the platform driver
probe, just before the first command (nand_scan_ident).

Or is there a more generic way to go about this?  And if so, I assume
inserting a RESET command like this would be transparent to other NAND
chips?

Thanks & Regards,
Pete

________________________________________________________________
Peter W.W. Ma                | email:  pma@mediamatech.com
Principal                    | tel:    +1 778 839-7865
Mediama Technologies         | fax:    +1 604 433-2465
 

Re: Micron NAND Rev D: initial reset

[Karl Beldan]

Peter Ma wrote:
> Hi, there...
> 
> I am trying to add mtd/nand driver support for the Micron MT29F2G08AADWP
> (Revision D) on 2.6.26.  
> 
> According to Micron, the difference (aside from ID code) between Rev D and
> the popular Rev C, is that the Rev D requires a RESET command to be issued
> after power-up and before any other command is issued.
> 
> I am just diving into the nand driver, but I thought I would ask if there is
> a good place to issue that RESET after power-up.
> 
> I do not see a specific "nand_reset()" function in nand_base.c  I assume I
> need to create this function, then have it called within the platform driver
> probe, just before the first command (nand_scan_ident).
> 
> Or is there a more generic way to go about this?  And if so, I assume
> inserting a RESET command like this would be transparent to other NAND
> chips?
> 
added in ef89a8801321e0d0665c327c9d77d602ef764c87.

-- 
Karl