Re: [PATCH v3 15/22] mtd: rawnand: fsmc: Stop implementing ->select_chip()

[Boris Brezillon <bbrezillon@xxxxxxxxxx>]

On Wed, 9 Jan 2019 22:30:18 +0100
Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:

> On Wed, Jan 9, 2019 at 9:54 PM Boris Brezillon <bbrezillon@xxxxxxxxxx> wrote:
> > [Me]  
> > > I guess that is normal for FSMC: only one CS. It seems a bit
> > > aggressive to toggle CS on/off between every command like this,
> > > I suspect the FSMC isn't really built for that but shakes apart
> > > or something.  
> >
> > Hm, that would be weird. There's indeed timing constraints on the NAND
> > chip side, but none infringing those constraints should not trigger an
> > external abort exception.  
> 
> The manual contains this (the same bit, just another name than
> in the driver):
> 
> PBKEN PC-card/NAND-Flash chip-select enable.
> Enables the corresponding chip-select.
> If a disabled chip-select is accessed, an HRESP = ERROR is generated
> on the AHB bus.
> 0: disabled (default after reset)
> 1: enabled

It's still not clear what this bit does. Do you have access to the CS
pin on the board?

> 
> > Can you check which phys range is remapped at
> > 0xcc960000?  
> 
> No idea how to do that but I'll see if I can figure it out...

print the __iomem values returned by devm_ioremap_resource() and find
the one that matches this address.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/