From: Chuck Peplinski <chuck@mds.com>
To: linux-mtd@lists.infradead.org
Subject: Support for Micron N25Q512
Date: Tue, 31 Dec 2013 11:52:25 -0600 [thread overview]
Message-ID: <52C30459.7040404@mds.com> (raw)
Hello-
We have a board that contains a TI ARM and the Micron N25Q512 and I've
been working to support it using the mtd driver in a recent Linux
distribution. I'd like to bring my code more into alignment with your
code. I see a number of things that confuse me. I understand that this
is the place to discuss.
I'm working with TI Linux code based on Linux 2.6.
When I refer to "your codebase", I mean
git://git.infradead.org/linux-mtd.git, SHA1 ID 15b540c.
I have diff'ed this code against what is provided to me in the older 2.6
version and I understand the differences. They don't seem to make the
code work on my board.
Searching the archives, I see that there has recently been activity to
support a device with this name. I also see an interesting thread about
a new framework for SPI-NOR. And I see reference to a file
drivers/mtd/devices/st_spi_fsm.c
But I don't see this file in the head of the code base.
- The JEDEC ID that I read is 0x20ba20, while the version in your
codebase names it 0x20bb20.
- To make the device work, I've had to add code to read the "flag status
register" and wait for transactions to complete. This is as illustrated
in the micron example code available from their web site. As I hacked
this into m25p80.c, it is quite specific to my device and not generic.
So that can't be the right way to do it.
I'm familiar with the differences between kernel versions. I realize my
code is not the latest, but I am ready to handle things like this. How
can I get connected to the latest work in the mtd driver and synchronize
my work with it?
Chuck
--
Chuck Peplinski
Momentum Data Systems
reply other threads:[~2013-12-31 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52C30459.7040404@mds.com \
--to=chuck@mds.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).