From: Nishanth Menon <menon.nishanth@gmail.com>
To: Linux OMAP List <linux-omap-open-source@linux.omap.com>, rohitkc@ti.com
Subject: [RFC] onenand detect logic
Date: Fri, 24 Aug 2007 15:29:54 -0500 [thread overview]
Message-ID: <46CF3FC2.3010203@gmail.com> (raw)
Hi Folks,
as a disclaimer, the following discussion is entirely a thought
experiment ;)
While discussing with Rohit C on supporting a different onenand on git
kernel, he enlightened me that the GPMC tracking and detecting onenand
CS based address is flaky.
Current Logic (with a highly deserving HACK alert comment) does this:
for each CS(){
if (CONFIG_7 reg ==0x20000000)
then assume it is onenand.
}
Here is a alternative proposal (majority from Rohit):
for each CS(){
if (configured as a NOR type memory){
write 0x90 to CONFIG_7 0x0 offset /* 0x90 0r 0x98 CFI command will
ensure that the memory is in non-read state, but in onenand it is a
readonly location */
read manu id and device id from onenand regs offsets from CONFIG_7
if matched as that for onenand, select same
}
}
Caveat: does not detect 2 onenands..
Question: Any better way of doing this dynamically and a bit more elegantly?
Regards,
Nishanth Menon
next reply other threads:[~2007-08-24 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 20:29 Nishanth Menon [this message]
2007-08-27 7:30 ` [RFC] onenand detect logic Kyungmin Park
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=46CF3FC2.3010203@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=rohitkc@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox