All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Villeneuve <hugo@hugovil.com>
To: linux-mtd@lists.infradead.org
Cc: b32955@freescale.com
Subject: imx6 NAND chip selects
Date: Wed, 07 May 2014 12:31:42 -0400	[thread overview]
Message-ID: <536A5FEE.9090705@hugovil.com> (raw)

Hi,
I am trying to connect a NAND flash device (Micron MT29F8G08) to a 
Wandboard Dual.

Here is the pin mapping:

i.MX6             NAND flash
----------------------------
NANDF_CS0    -->  CE#
NANDF_RB0    -->  R/B#
NANDF_WP_B   -->  WP#
NANDF_CLE    -->  CLE
NANDF_ALE    -->  ALE
NANDF_WE     -->  WE#
NANDF_RE     -->  RE#
NANDF_D[0-7] -->  I/O[0-7]

This NAND flash has a single chip-select.

I'm testing it using Linux kernel 3.15.0-rc3.

In the wandboard device tree file, I have added all the above gpmi pins 
as GPMI pins.

I am still booting from the SD card, so at this point I am only trying 
to detect the NAND device. Unfortunately, when the kernel boots, the 
GPMI driver fails to register (error -19).

If I monitor the NANDF_CS0 line, I can see that it is pulsed low, but I 
am not seing any activity on the NANDF_WE line.

However, If I monitor the NANDF_CS1 line, I can see that it is pulsed 
low, and during the time it is low the NANDF_WE line is also going low.

I then made sure to reconfigure the unused pins NANDF_CS[1-3] as GPIOs 
(ALT5 function) in my device tree file. I have confirmed with kernel 
debug traces that the iomux register for NANDF_CS1 have the value 0x05, 
which means ALT5 function (GPIO). But I am still seeing the same 
behavior as before on the oscilloscope.

So how can I configure the GPMI driver to only use NANDF_CS0 and not 
NANDF_CS1?

And is it normal that NANDF_CS1 is still used by the GPMI driver when 
configured as GPIO?

Hugo.

             reply	other threads:[~2014-05-07 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 16:31 Hugo Villeneuve [this message]
2014-05-08 15:37 ` imx6 NAND chip selects Huang Shijie
2014-05-12 14:14   ` Hugo Villeneuve
2014-05-12 20:32   ` Hugo Villeneuve

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=536A5FEE.9090705@hugovil.com \
    --to=hugo@hugovil.com \
    --cc=b32955@freescale.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.