linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vigneshr@ti.com (Vignesh R)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/5] spi: introduce flag for memory mapped read
Date: Fri, 7 Aug 2015 14:05:10 +0530	[thread overview]
Message-ID: <55C46DBE.7060809@ti.com> (raw)
In-Reply-To: <CAOMqctRBW230fA4AEhK7MyqkZY==6ENNNHE-LVm7-mHKA_VzRw@mail.gmail.com>



On 08/07/2015 01:08 PM, Michal Suchanek wrote:

> Now since the description is clearer it's obvious that ti-qspi cannot
> work fully mmapped as fsl-qspi does because the setup has to be done
> over normal spi access and using non-m25p80 devices on the same bus is
> a requirement.
> 
> The place where it is known if a transfer can use the mmap access is m25p80.c
> 
> So my suggestion is
> 
>  - add a new method for spi master that gets the read opcode, dummy
> length, address, address length, buffer, buffer length and performs
> read from the flash memory in a hardware-specific way
> 
> - add a check in m25p80.c that the master supports this feature and if
> so use it (eg check that the method is non-null)
> 
> Presumably if some new SPI controllers with similar feature are
> supported in the future they can use the same inteface because you
> pass on everything the m25p80 read knows.
> 

Ok... Do you mean something like this?

I will take m25p80 as example but can be expanded for any flash.

In include/linux/mtd.h:
	struct spi_mtd_config_info {
		struct spi_device 	*spi;
	        u32                     page_size;
	        u8                      addr_width;
       		u8                      erase_opcode;
	        u8                      read_opcode;
        	u8                      read_dummy;
	        u8                      program_opcode;
        	enum read_mode          flash_read;

	} /* subset of struct spi_nor */


In m25p80.c:

	static int m25p80_read(struct spi_nor *nor, loff_t from,
				size_t len, size_t *retlen,
				u_char *buf)
	{
		struct spi_mtd_config_info info;
		struct spi_device *spi;
		
		if (spi->master->spi_mtd_mmap_read) {
		  /* Populate spi_mtd_config_info */
		  spi->master->spi_mtd_mmap_read(&info, from, len,
						 retlen, buf);
		}
		else {
		/* no mtd specific acceleration supported try normal
		 * SPI way of communicating with flash
		 * continue with current code
		 * set up spi_message and call spi_sync()
		 */
	}

      }

In spi-ti-qspi.c:
Implement spi_mtd_mmap_read while holding master->bus_lock mutex.


-- 
Regards
Vignesh

  reply	other threads:[~2015-08-07  8:35 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
2015-08-04 15:51       ` Mark Brown
2015-08-04 17:59         ` R, Vignesh
2015-08-05  5:21           ` Michal Suchanek
2015-08-05  5:35             ` Vignesh R
2015-08-05  5:57               ` Michal Suchanek
2015-08-05 11:50           ` Mark Brown
2015-08-05 12:40             ` Michal Suchanek
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
2015-08-06 10:22                       ` Russell King - ARM Linux
2015-08-06 11:00                         ` Mark Brown
2015-08-06 11:02                         ` Michal Suchanek
2015-08-06 12:25                         ` Vignesh R
2015-08-06 13:51                           ` Russell King - ARM Linux
2015-08-06 16:14                             ` Geert Uytterhoeven
2015-08-06 18:20                               ` Michal Suchanek
2015-08-06 21:33                               ` Russell King - ARM Linux
2015-08-07  7:38                                 ` Michal Suchanek
2015-08-07  8:35                                   ` Vignesh R [this message]
2015-08-07  8:25                                 ` Martin Sperl
2015-08-07 10:16                                   ` Michal Suchanek
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
2015-08-03  5:09     ` Vignesh R
2015-07-31 18:19   ` Mark Brown
2015-08-03  5:02     ` Vignesh R
2015-08-04 15:52       ` Mark Brown
2015-07-31 21:28   ` Brian Norris
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=55C46DBE.7060809@ti.com \
    --to=vigneshr@ti.com \
    --cc=linux-arm-kernel@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).