* Re: Qspi flash device driver - framework to use?
[not found] <518CD57E.2020705@ti.com>
@ 2013-05-14 12:13 ` Sourav Poddar
0 siblings, 0 replies; only message in thread
From: Sourav Poddar @ 2013-05-14 12:13 UTC (permalink / raw)
To: spi-devel-general
Cc: Matt Porter, Felipe Balbi, grant.likely, broonie,
Santosh Shilimkar, Pekon Gupta, linux-mtd
+ linux-mtd list
On Friday 10 May 2013 04:39 PM, Sourav Poddar wrote:
> Hi,
>
> I am trying to work out a way to write a QSPI serial flash interface
> driver
> for my IP. The idea is to have an execute in place usecase.
>
> We have a configuration port from which the spi core can be configured
> and a
> memory mapped port from which the data can be read/write from/to serial
> flash device.
>
> As far as I can understand, I dont think it will be correct/possible
> to write this
> driver making use of the generice spi framework(drivers/spi/spi.c) as
> that
> framework is more suited for generic spi use case, where in you can load
> your Image from external SPI devices into DDR and then execute. ?
>
> But for cases, where qspi is connected to serial flash device (XIP is
> needed) what
> we might need is some framework which just passes the buffers and its
> length to
> our driver which in turn will configure the qspi to initiate the
> transfer.
>
> What can be the best framework to use for the above use case?
>
> I saw a device(m25p80) using mtd framework for some similar usecase.
> Is it the mtd which should be used? OR will it be a
> good idea to go for a generic qspi framework(drivers/qspi) which can be
> used by qspi flash devices having a memory mapped interface. ?
>
> Thanks,
> Sourav
^ permalink raw reply [flat|nested] only message in thread