From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sourav Poddar Subject: Re: [PATCH 1/3] spi/qspi: Add memory mapped read support. Date: Thu, 10 Oct 2013 16:38:19 +0530 Message-ID: <52568AA3.9080203@ti.com> References: <52566ACC.1080100@ti.com> <20131010101410.GG21581@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: Peter Korsgaard , Trent Piepho , balbi@ti.com, "linux-mtd@lists.infradead.org" , "spi-devel-general@lists.sourceforge.net" , computersforpeace@gmail.com, dwmw2@infradead.org To: Mark Brown Return-path: In-Reply-To: <20131010101410.GG21581@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-mtd" Errors-To: linux-mtd-bounces+gldm-linux-mtd-36=gmane.org@lists.infradead.org List-Id: linux-spi.vger.kernel.org Hi Mark, On Thursday 10 October 2013 03:44 PM, Mark Brown wrote: > On Thu, Oct 10, 2013 at 02:22:28PM +0530, Sourav Poddar wrote: > >> [Trent]: With mapping driver, I believe you are hinting at >> drivers/mtd/maps? I had >> a look at it and what I got is that it is used/suitable for parallel >> flashes and not the >> serial flashes. > Essentially what it looks like this hardware is trying to do is adapt a > serial flash so it looks more like a parallel flash. It's not clear > that this is a good idea if we are already able to understand serial > flash though. Do you have any idea of how to go about implementing it in a more cleaner way?(taking care of all what the spi controller hardware needs to do for the memory mapped mode.). I understand doing a memcpy in the caller itself, but how to tackle the spi controller configuration at that point of time. Memory mapped is a spi controller feature rather than a flash. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/