From: Scott Wood <scottwood@freescale.com>
To: nanda <nanda74pg@rediffmail.com>
Cc: linuxppc-dev@ozlabs.org, avorontsov@ru.mvista.com
Subject: Re: fsl upm NAND Flash issue without GPIO chip handler
Date: Tue, 19 Jan 2010 11:13:16 -0600 [thread overview]
Message-ID: <4B55E82C.3060406@freescale.com> (raw)
In-Reply-To: <20100119124014.22519.qmail@f5mail-237-237.rediffmail.com>
nanda wrote:
>
> We had merged the 2.6.24
That's pretty old...
> with the FSL based NAND driver,
Which one? Which chip are you using, and how is NAND attached to it?
> we observed that gpio library is mandatory to be included. We have not included the
> gpios configured in the dts file as the we don’t have the separate GPIO
> chip(arch/powepc/boot/dts/board.dts).
What separate GPIO chip? Which "board.dts" are you looking at?
> After executing the image in the board, we observed the below
> 1) The device ID and manufacture Id was printed as "c0" and "c0" and the
> error message "No NAND device found!!!". Does it mean it is not
> accessing the NAND flash and the values read are junk one?
> 2) Processor of the board doesn’t connect the Ready/Busy of the NAND
> flash through the separate GPIO chip. I mean it is directly connected
> from GPIO Port C of PIN 15 to the Ready/Busy PIN of the NAND flash.
> Hence is it necessary to port the gpio specific functions like
> gpio_request/gpio_free(specified in fsl_upm.c file), instead should we
> need to configure the PIN par_io_config_pin() for configuration of the
> PORT C with 15th PIN and set the data value using par_io_data_set()
> (specified arch/powerpc/sysdev/qe_lib/qe_io.c)
Have you tried pointing the "gpios" property at pin 15 of port C? The
whole point of this abstraction is that these connections are described
in the data, not in the code.
-Scott
next prev parent reply other threads:[~2010-01-19 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 12:40 fsl upm NAND Flash issue without GPIO chip handler nanda
2010-01-19 17:13 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-20 18:11 nanda
2010-01-20 18:39 ` Scott Wood
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=4B55E82C.3060406@freescale.com \
--to=scottwood@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nanda74pg@rediffmail.com \
/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.