From: Sourav Poddar <sourav.poddar@ti.com>
To: <spi-devel-general@lists.sourceforge.net>
Cc: Matt Porter <mporter@ti.com>, Felipe Balbi <balbi@ti.com>,
grant.likely@secretlab.ca, broonie@kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Pekon Gupta <pekon@ti.com>,
linux-mtd@lists.infradead.org
Subject: Re: Qspi flash device driver - framework to use?
Date: Tue, 14 May 2013 17:43:14 +0530 [thread overview]
Message-ID: <51922A5A.9040501@ti.com> (raw)
In-Reply-To: <518CD57E.2020705@ti.com>
+ 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
WARNING: multiple messages have this Message-ID (diff)
From: Sourav Poddar <sourav.poddar-l0cyMroinI0@public.gmane.org>
To: <spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Matt Porter <mporter-l0cyMroinI0@public.gmane.org>,
Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Santosh Shilimkar
<santosh.shilimkar-l0cyMroinI0@public.gmane.org>,
Pekon Gupta <pekon-l0cyMroinI0@public.gmane.org>,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Qspi flash device driver - framework to use?
Date: Tue, 14 May 2013 17:43:14 +0530 [thread overview]
Message-ID: <51922A5A.9040501@ti.com> (raw)
In-Reply-To: <518CD57E.2020705-l0cyMroinI0@public.gmane.org>
+ 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
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
next prev parent reply other threads:[~2013-05-14 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 11:09 Qspi flash device driver - framework to use? Sourav Poddar
[not found] ` <20130510111757.GS3200@sirena.org.uk>
[not found] ` <20130510111757.GS3200-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-05-10 18:55 ` Santosh Shilimkar
2013-05-14 12:13 ` Sourav Poddar [this message]
2013-05-14 12:13 ` Sourav Poddar
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=51922A5A.9040501@ti.com \
--to=sourav.poddar@ti.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=mporter@ti.com \
--cc=pekon@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.