linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shiraz HASHIM <shiraz.hashim@st.com>
To: linux-mtd@lists.infradead.org
Subject: [Query] Serial Memory Interface Controller interface
Date: Tue, 04 May 2010 11:06:31 +0530	[thread overview]
Message-ID: <4BDFB25F.8050305@st.com> (raw)

Hi,

I am working on ST's SMI controller for Serial NOR flashes. This controller is a
special controller build specifically for serial memories (spi based).
It has certain features directly catering to serial memories such as mapping of
memory directly on the bus so that it can be directly accessed/addressed.

Now the problem is that this controller cannot be exactly mapped in to SPI
framework due to its features. What should be the best approach

1. To write serial nor flash drivers accessing smi controller (instead of SPI
framework APIs)
2. To use some tricks and fit SMI controller into SPI framework itself.

thanks for help

regards
Shiraz

                 reply	other threads:[~2010-05-04  5:36 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=4BDFB25F.8050305@st.com \
    --to=shiraz.hashim@st.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).