linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org,
	Brian Norris <computersforpeace@gmail.com>,
	Russell King <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	Huang Shijie <b32955@freescale.com>,
	linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/5] spi: introduce flag for memory mapped read
Date: Mon, 3 Aug 2015 10:27:19 +0530	[thread overview]
Message-ID: <55BEF4AF.5090704@ti.com> (raw)
In-Reply-To: <20150731181745.GM20873@sirena.org.uk>

Hi,

On 7/31/2015 11:47 PM, Mark Brown wrote:
> On Tue, Jul 28, 2015 at 02:11:12PM +0530, Vignesh R wrote:
> 
>> Introduce use_mmap_read field in spi_message struct. This can be set by
>> mtd devices (m25p80) to indicate to spi-master (ti-qspi) to perform
>> memory mapped read. This helps to distinguish whether the spi-message is
>> from mtd layer(hence mmap read is possible) or by other spi devices.
> 
> Based on this description and...
> 
>> + * @use_mmap_mode: Indicate to spi master to perform memory mapped
>> + *	read if possible.
> 
> ...the internal documentation I unable to tell what is meant by "perform
> a memory mapped read", at least to the extent where it is visible
> outside of the driver.  This means we can't really use this as a generic
> API since other people won't be able to tell what it does.
> 


Will the following documentation provide better idea regarding the flag:

@use_mmap_mode: Some SPI controller chips are optimized for interacting
with serial flash memories. These chips have memory mapped interface,
through which entire serial flash memory slave can be read/written as if
though they are physical memories (like RAM). Using this interface,
flash can be accessed using memcpy() function and the spi controller
hardware will take care of communicating with serial flash over SPI.
Setting this flag will indicate the SPI controller driver that the
spi_message is from mtd layer to read from/write to flash. The SPI
master driver can then appropriately switch the controller to memory
mapped interface to read from/write to flash, based on this flag (See
drivers/spi/spi-ti-qspi.c for example).
NOTE: If the SPI controller chip lacks memory mapped interface, then the
driver will ignore this flag and use normal SPI protocol to read
from/write to flash. Communication with non-flash SPI devices is not
possible using the memory mapped interface.

I can update the patch commit message and documentation accordingly?

Regards
Vignesh

  reply	other threads:[~2015-08-03  4:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  8:41 [RFC PATCH 0/5] Add memory mapped read support for TI QSPI Vignesh R
2015-07-28  8:41 ` [RFC PATCH 1/5] spi: introduce flag for memory mapped read Vignesh R
2015-07-31 18:17   ` Mark Brown
2015-08-03  4:57     ` Vignesh R [this message]
2015-08-04 15:51       ` Mark Brown
     [not found]         ` <20150804155148.GR20873-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-08-04 17:59           ` R, Vignesh
     [not found]             ` <55C0FD98.1090107-l0cyMroinI0@public.gmane.org>
2015-08-05  5:21               ` Michal Suchanek
2015-08-05  5:35                 ` Vignesh R
     [not found]                   ` <55C1A095.8000509-l0cyMroinI0@public.gmane.org>
2015-08-05  5:57                     ` Michal Suchanek
2015-08-05 11:50             ` Mark Brown
     [not found]               ` <20150805115013.GJ20873-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-08-05 12:40                 ` Michal Suchanek
     [not found]                   ` <CAOMqctQXwcHyiWBwtugSDSE_k65qrNfrwnhjQMDJkLoJMmGzUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-05 12:44                     ` Mark Brown
2015-08-05 12:56                       ` Michal Suchanek
2015-08-06  9:02                         ` Mark Brown
2015-08-06 10:01                           ` Michal Suchanek
     [not found]                             ` <CAOMqctQZRZ4zG_yYy=CeX3DX4NVNWN1COP4Q-2YvMun9xYOA7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-06 10:22                               ` Russell King - ARM Linux
2015-08-06 11:00                                 ` Mark Brown
     [not found]                                 ` <20150806102225.GI7576-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-08-06 11:02                                   ` Michal Suchanek
2015-08-06 12:25                                   ` Vignesh R
2015-08-06 13:51                                     ` Russell King - ARM Linux
     [not found]                                       ` <20150806135129.GJ7576-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-08-06 16:14                                         ` Geert Uytterhoeven
     [not found]                                           ` <CAMuHMdWWDwZ=ziGQXFCnOX8pErXpsEi533J73_Hh=sEqq4hR6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-06 18:20                                             ` Michal Suchanek
2015-08-06 21:33                                             ` Russell King - ARM Linux
     [not found]                                               ` <20150806213340.GK7576-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-08-07  7:38                                                 ` Michal Suchanek
2015-08-07  8:35                                                   ` Vignesh R
2015-08-07  8:25                                                 ` Martin Sperl
2015-08-07 10:16                                                   ` Michal Suchanek
     [not found]                                                     ` <CAOMqctScUybdoZPgqH185qzDxB=TyutDMARextHx0XwC7L3Xmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-12  9:27                                                       ` Vignesh R
2015-08-06 16:46                                         ` Mark Brown
2015-08-06 18:20                                     ` Mark Brown
2015-08-06 11:23                               ` Mark Brown
2015-08-06 11:42                                 ` Michal Suchanek
2015-08-06 16:03                                   ` Mark Brown
2015-07-28  8:41 ` [RFC PATCH 2/5] spi: spi-ti-qspi: Add memory mapped read support Vignesh R
2015-07-28  8:41 ` [RFC PATCH 3/5] mtd: devices: m25p80: set flag to request memory mapped read Vignesh R
2015-07-28  8:41 ` [RFC PATCH 4/5] ARM: dts: DRA7: Add memory map region entries for qspi Vignesh R
2015-07-31 13:48   ` Sekhar Nori
     [not found]     ` <55BB7CA4.1020300-l0cyMroinI0@public.gmane.org>
2015-08-03  5:09       ` Vignesh R
2015-07-31 18:19   ` Mark Brown
     [not found]     ` <20150731181903.GN20873-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-08-03  5:02       ` Vignesh R
     [not found]         ` <55BEF5D1.1050608-l0cyMroinI0@public.gmane.org>
2015-08-04 15:52           ` Mark Brown
2015-07-31 21:28   ` Brian Norris
     [not found]     ` <20150731212847.GH10676-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2015-08-03  5:06       ` Vignesh R
2015-07-28  8:41 ` [RFC PATCH 5/5] ARM: dts: AM4372: " Vignesh R

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=55BEF4AF.5090704@ti.com \
    --to=vigneshr@ti.com \
    --cc=b32955@freescale.com \
    --cc=broonie@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).