public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 00/10] spi: dw: Add support for DUAL/QUAD/OCTAL modes
Date: Fri, 2 Apr 2021 19:07:14 -0400	[thread overview]
Message-ID: <360ad365-d9d9-6ec2-5165-5e24cdb71f60@gmail.com> (raw)
In-Reply-To: <20210402230515.177825-1-seanga2@gmail.com>

On 4/2/21 7:05 PM, Sean Anderson wrote:
> This series adds support for enhanced SPI modes. It was tested on a K210 (DWC
> SSI with QSPI flash).
> 
> If anyone has a designware device with QSPI flash attached (especially a DW SSI
> APB device), I'd greatly appreciate them testing out this patch series. Given
> that there has been no testing of v2 over the past month, I don't think lack of
> testing should hold up this series.
> 
> Changes in v3:
> - Dropped merged patches
> - Rebased on u-boot/master
> 
> Changes in v2:
> - Add more information to exec_op debug message
> - Actually mask interrupts
> - Merge CAP_{DUAL,QUAD,OCTAL} into CAP_ENHANCED
> - Fix some inconsistencies in register naming and usage
> - Moved some hunks between commits so things make more sense
> 
> Sean Anderson (10):
>    mtd: spi-mem: Export spi_mem_default_supports_op
>    spi: spi-mem: Add debug message for spi-mem ops
>    spi: dw: Log status register on timeout
>    spi: dw: Actually mask interrupts
>    spi: dw: Switch to capabilities
>    spi: dw: Rewrite poll_transfer logic
>    spi: dw: Add ENHANCED cap
>    spi: dw: Define registers for enhanced mode
>    spi: dw: Support enhanced SPI
>    spi: dw: Support clock stretching
> 
>   drivers/spi/designware_spi.c | 647 ++++++++++++++++++++++++-----------
>   drivers/spi/spi-mem.c        |   7 +
>   include/spi-mem.h            |   3 +
>   3 files changed, 451 insertions(+), 206 deletions(-)
> 

Looks like I forgot to bump the version. This should be v3. I can resend if necessary.

--Sean

  parent reply	other threads:[~2021-04-02 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 23:05 [PATCH v2 00/10] spi: dw: Add support for DUAL/QUAD/OCTAL modes Sean Anderson
2021-04-02 23:05 ` [PATCH v2 01/10] mtd: spi-mem: Export spi_mem_default_supports_op Sean Anderson
2021-04-02 23:05 ` [PATCH v2 02/10] spi: spi-mem: Add debug message for spi-mem ops Sean Anderson
2021-04-02 23:05 ` [PATCH v2 03/10] spi: dw: Log status register on timeout Sean Anderson
2021-04-02 23:05 ` [PATCH v2 04/10] spi: dw: Actually mask interrupts Sean Anderson
2021-04-02 23:05 ` [PATCH v2 05/10] spi: dw: Switch to capabilities Sean Anderson
2021-04-02 23:05 ` [PATCH v2 06/10] spi: dw: Rewrite poll_transfer logic Sean Anderson
2021-04-05  0:47   ` Damien Le Moal
2021-04-05  1:11     ` Sean Anderson
2021-04-02 23:05 ` [PATCH v2 07/10] spi: dw: Add ENHANCED cap Sean Anderson
2021-04-02 23:05 ` [PATCH v2 08/10] spi: dw: Define registers for enhanced mode Sean Anderson
2021-04-02 23:05 ` [PATCH v2 09/10] spi: dw: Support enhanced SPI Sean Anderson
2021-04-02 23:05 ` [PATCH v2 10/10] spi: dw: Support clock stretching Sean Anderson
2021-04-02 23:07 ` Sean Anderson [this message]
2021-04-19  7:06   ` [PATCH v2 00/10] spi: dw: Add support for DUAL/QUAD/OCTAL modes Jagan Teki
2021-04-19 13:19     ` Sean Anderson
2021-04-19 13:45       ` Jagan Teki

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=360ad365-d9d9-6ec2-5165-5e24cdb71f60@gmail.com \
    --to=seanga2@gmail.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