[PATCH v3] mtd: omap: nand: Remove 0xFF's that prefixed 16bit NAND addresses

Artem Bityutskiy dedekind1 at gmail.com
Thu Nov 15 06:02:09 EST 2012

On Mon, 2012-10-29 at 15:51 -0400, Christopher Harvey wrote:
> In 16bit NAND mode the GPMC would send the address 0xNN as 0xFFNN
> instead of 0x00NN on the bus. The 0xFFs were actually uninitialized
> bits that were left unset in the GPMC command output register. The
> reason they weren't initialized in 16bit mode is that if the same code
> that writes to this register was used in 8bit mode then 2 commands
> would be output in 8bit mode. One for the low byte, and an extra 0x0
> command for the high byte. This commit uses writew if we're using
> 16bit NAND. This commit also changes the high byte in the command
> output register, but they are ignored by NAND chips anyway.
> Most chips seem fine with the extra 0xFFs, but the ONFI spec says
> otherwise.
> Signed-off-by: Christopher Harvey <charvey at matrox.com>

Pushed to l2-mtd.git, thanks!

Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20121115/7baa4063/attachment.sig>

More information about the linux-mtd mailing list