linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sourav Poddar <sourav.poddar@ti.com>
To: Mark Brown <broonie@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Memory mapped support for SPI flash ?
Date: Mon, 7 Oct 2013 16:56:03 +0530	[thread overview]
Message-ID: <52529A4B.6040501@ti.com> (raw)

Hi,

I wanted to know whether there is any framework or support available
in mtd which helps in doing a memory mapped read for a serial NOR flash 
driver.

Requirement is something like this..

My controller supports memory mapped read, but needs to switch to
memory mapped port to read from it and once the
read is done switch back again to normal configuration mode.

So, my idea is that spi controller need to be communicated from  the mtd 
layer
that the current read is memory mapped read, so the controller does
whatever settings need to be done and then does the memory mapped read and
switch back to configuration mode.

I see some drivers under drivers/mtd/maps/* , point and unpoint 
functions, but are they
applicable for serial NOR flashes? Or there is any other stuff available 
which I can use
for my usecase?

I was thing of using it in a way that dual/quad support is used. I mean 
to add "memory map"
as a mode and pass it as a transfer parameter(from the mtd layer) to 
indicate that the current transfer
is a memory map read and then do a memcopy in the low level driver function.

Thanks in advance,
Sourav

                 reply	other threads:[~2013-10-07 11:26 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=52529A4B.6040501@ti.com \
    --to=sourav.poddar@ti.com \
    --cc=broonie@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --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).