From: Sourav Poddar <sourav.poddar@ti.com>
To: Huang Shijie <b32955@freescale.com>
Cc: artem.bityutskiy@linux.intel.com, balbi@ti.com,
broonie@kernel.org, linux-mtd@lists.infradead.org,
computersforpeace@gmail.com,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCHv2] drivers: mtd: devices: Add quad read support.
Date: Fri, 27 Sep 2013 11:24:13 +0530 [thread overview]
Message-ID: <52451D85.90404@ti.com> (raw)
In-Reply-To: <5244F003.6040502@freescale.com>
On Friday 27 September 2013 08:10 AM, Huang Shijie wrote:
> 于 2013年09月26日 19:21, Sourav Poddar 写道:
>> If the pupose of LUT is to just set the dummy cycles, and vf610-twr
>> hardware state machine does not have have any other dependency
>> on LUT, this patch should work.
> Hi Sourav & David:
>
> The key issue about the vf610-twr is that:
> [0] Use the LUT makes the Quadspi driver more efficiency.
> [1] the vf610-twr needs to know the SPI NOR commands for Page Program.
> Why? because the driver can not change the size of write-buffer
> from 256bytes to the 64byte(TXFIFO SIZE).
Not clear about this. But, you will anyway know what you are using from
the m25p80 side rite?
> [2] the dummy and other things.
>
Dummy stuffs can be handled from m25p80 side rite? fast read dummy cycle
support is already there. While,
$subject patch adds it for quad read.
> Mark said the Quadspi is not a SPI controller, instead it is a SPI NOR
> controller, and Mark suggested me
> to rewrite the m25p80.c for the Quadspi.
>
> thanks
> Huang Shijie
>
>
next prev parent reply other threads:[~2013-09-27 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 10:32 [PATCHv2] drivers: mtd: devices: Add quad read support Sourav Poddar
2013-09-26 11:00 ` David Woodhouse
2013-09-26 11:21 ` Sourav Poddar
2013-09-26 11:31 ` David Woodhouse
2013-09-27 2:40 ` Huang Shijie
2013-09-27 5:54 ` Sourav Poddar [this message]
2013-09-27 6:16 ` Huang Shijie
2013-09-27 6:27 ` Sourav Poddar
2013-09-27 7:05 ` Huang Shijie
2013-09-26 11:59 ` Mark Brown
2013-10-07 12:11 ` 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=52451D85.90404@ti.com \
--to=sourav.poddar@ti.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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 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.