From: Sourav Poddar <sourav.poddar@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 00/12] sf: Add Extended read and quad read/write commands support
Date: Mon, 6 Jan 2014 12:52:15 +0530 [thread overview]
Message-ID: <52CA59A7.9080405@ti.com> (raw)
In-Reply-To: <e4c2739b-f8e6-4267-9066-f6dbf47999df@TX2EHSMHS001.ehs.local>
On Saturday 04 January 2014 08:34 PM, Jagannadha Sutradharudu Teki wrote:
> This a suffix series for
> http://u-boot.10912.n7.nabble.com/PATCH-v4-00-36-sf-Add-common-probe-and-extended-quad-read-write-cmds-support-td163949.html
> for adding extended read and quad read/write commands support.
>
> Concept:
> "Implementation will discover the fastest command by taking the supported
> commands from flash and a controller. Controller supported commands will always been a priority."
>
> The above concept is changed in this series as couple of reviews from earlier ones.
> - Implementation concept will apply on read commands.
> - As we have two write commands as of now ? so this series is not trying to
> discover the fastest write command
> - The respective command modes are given to the controller driver side as a form of
> SPI RX/RX operation modes - so sf definitions will not be part of SPI driver side.
>
> Testing branch:
> $ git clone git://git.denx.de/u-boot-spi.git
> $ cd u-boot-spi
> $ git checkout -b master-quad origin/master-quad
>
> REQUEST FOR ALL SPI CODE CONTRIBUTORS/USERS, PLEASE TEST THESE CHANGES
> W.R.T YOUR HW IF POSSIBLE.
>
> Please let me know for any issues/concerns/questions.
>
> --
> Thanks,
> Jagan.
>
> Changes for v6:
> - Divided flash reg ops code
> - sf_ops.c clean
> Changes for v5:
> - Re-implemented write command log - not trying to discover the fastest write
> - Added SPI RX/TX operation modes
> - SPI flash parts are moved into sf_params.c file
> - Added QUAD_IO_FAST read support
> - Discovred the read dummy_cycles based on configured read cmd
> - Added set QEB support for macronix flash
> - Enabled quad read/write cmd support for macronix flash
> Changes for v4:
> Changes for v3:
> Changes for v2:
> - none
>
> Jagannadha Sutradharudu Teki (12):
> sf: Add extended read commands support
> sf: Add quad read/write commands support
> sf: ops: Add configuration register writing support
> sf: Set quad enable bit support
> sf: probe: Enable RD_FULL and WR_QPP
> sf: Separate the flash params table
> sf: Add QUAD_IO_FAST read support
> sf: Discover read dummy_cycles
> sf: Add macronix set QEB support
> sf: probe: Enable macronix quad read/write cmds support
> sf: Divide flash register ops from QEB code
> sf: Code cleanups
>
> drivers/mtd/spi/Makefile | 4 +-
> drivers/mtd/spi/sf_internal.h | 31 +++++-
> drivers/mtd/spi/sf_ops.c | 71 ++++++++++--
> drivers/mtd/spi/sf_params.c | 130 ++++++++++++++++++++++
> drivers/mtd/spi/sf_probe.c | 246 +++++++++++++++++++-----------------------
> include/spi.h | 17 +++
> include/spi_flash.h | 43 ++++++++
> 7 files changed, 393 insertions(+), 149 deletions(-)
> create mode 100644 drivers/mtd/spi/sf_params.c
>
Apart from the couple of comments given, this series looks good to me.
prev parent reply other threads:[~2014-01-06 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 15:04 [U-Boot] [PATCH v6 00/12] sf: Add Extended read and quad read/write commands support Jagannadha Sutradharudu Teki
2014-01-06 7:22 ` Sourav Poddar [this message]
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=52CA59A7.9080405@ti.com \
--to=sourav.poddar@ti.com \
--cc=u-boot@lists.denx.de \
/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