From: Vignesh R <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses
Date: Tue, 9 Jan 2018 18:49:17 +0530 [thread overview]
Message-ID: <20180109131920.23057-1-vigneshr@ti.com> (raw)
This series reverts use of bounce_buf.c for non-DMA related alignment
restriction and replaces it with local bounce buffer to handle problems
with non 32 bit aligned writes on TI platforms.
Based on top of Jason's series:
https://patchwork.ozlabs.org/cover/856431/
Tested on K2G EVM.
Goldschmidt Simon (1):
Revert "spi: cadence_qspi_apb: Use 32 bit indirect read transaction
when possible"
Vignesh R (2):
Revert "spi: cadence_qspi_apb: Use 32 bit indirect write transaction
when possible"
spi: cadence_qspi_apb: Make flash writes 32 bit aligned
drivers/spi/cadence_qspi_apb.c | 49 ++++++++++++++++++----------------------
include/configs/k2g_evm.h | 1 -
include/configs/socfpga_common.h | 1 -
include/configs/stv0991.h | 1 -
4 files changed, 22 insertions(+), 30 deletions(-)
--
2.15.1
next reply other threads:[~2018-01-09 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 13:19 Vignesh R [this message]
2018-01-09 13:19 ` [U-Boot] [PATCH v2 1/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect read transaction when possible" Vignesh R
2018-01-09 13:19 ` [U-Boot] [PATCH v2 2/3] Revert "spi: cadence_qspi_apb: Use 32 bit indirect write " Vignesh R
2018-01-09 13:19 ` [U-Boot] [PATCH v2 3/3] spi: cadence_qspi_apb: Make flash writes 32 bit aligned Vignesh R
2018-01-15 11:36 ` [U-Boot] [PATCH v2 0/3] cadence-quadspi: Fix issues with non 32bit aligned accesses Vignesh R
2018-01-15 11:45 ` Marek Vasut
2018-01-15 12:01 ` Simon Goldschmidt
2018-01-15 13:47 ` Jason Rush
2018-01-23 8:12 ` Simon Goldschmidt
2018-01-23 8:45 ` Jagan Teki
2018-01-23 9:02 ` Vignesh R
2018-01-23 9:07 ` Jagan Teki
2018-01-23 9:16 ` Vignesh R
2018-01-23 9:24 ` Jagan Teki
2018-01-23 9:26 ` Simon Goldschmidt
2018-01-23 9:31 ` Jagan Teki
2018-01-23 10:05 ` Vignesh R
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 15:33 Goldschmidt Simon
2018-01-10 15:39 ` Marek Vasut
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=20180109131920.23057-1-vigneshr@ti.com \
--to=vigneshr@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