public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: See, Chin Liang <chin.liang.see@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] spi: cadence_qspi_apb: Use 32 bit indirect write transaction when possible
Date: Wed, 7 Dec 2016 13:22:49 +0000	[thread overview]
Message-ID: <1481116966.1967.3.camel@intel.com> (raw)
In-Reply-To: <62f581df-d5c8-afe7-9bfe-d16ddb940b44@ti.com>

On Sel, 2016-12-06 at 10:54 +0530, Vignesh R wrote:
> 
> Hi,
> 
> On Thursday 01 December 2016 09:41 AM, Vignesh R wrote:
> [...]
> > 
> > 
> > > 
> > > 
> > > > 
> > > > 
> > > > Data slave port does accept byte, half-word and word access,
> > > > there
> > > > are
> > > > no data aborts. But indirect write controller seems to have
> > > > limitation(as documented in section 11.15.4.9.2) couping with
> > > > non 32-
> > > > bit
> > > > data writes on TI platform. For example with current driver if
> > > > I try:
> > > > 
> > > > fatload mmc 0 0x82000000 zImage
> > > > sf erase 0x0 0x500000
> > > > sf write 0x82000000 0x0 0x35
> > > > sf read 0xA0000000 0x0 0x35
> > > > 
> > > > 
> > > > md.b 0xA0000000
> > > > a0000000: 00 00 a0 00 00 00 a0 00 00 00 a0 00 00 00 a0 00
> > > > a0000010: 00 00 a0 00 00 00 a0 00 00 00 a0 00 00 00 a0 00
> > > > a0000020: 03 00 00 00 18 28 6f 00 00 00 00 00 d8 5b 35 00
> > > > a0000030: 01 02 03 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > md.b 0x82000000
> > > > 82000000: 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1
> > > > 82000010: 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1
> > > > 82000020: 03 00 00 ea 18 28 6f 01 00 00 00 00 d8 5b 35 00
> > > > 82000030: 01 02 03 04 00 90 0f e1 88 07 00 eb 01 70 a0 e1
> > > > 
> > > > 
> > > > As you can see, every fourth byte turn out to be 0x00.
> > > > Therefore this
> > > > patch is required.
> > > Thanks Vignesh
> > > 
> > > Interesting to know that the newer version of controller has this
> > > constrain. Let me pull out my board to ensure this patch doesn't
> > > break
> > > the SOCFPGA
> > > 
> Did you get a chance to test this patch? There is also a similar
> patch
> for indirect read as well[1], it would be great if you could give
> your
> Tested-by for both the patches. Thanks!
> 
> [1]https://patchwork.ozlabs.org/patch/700990/

Actually I was bumping into sf probe error. This is happen at mainline
even without your patch. Let me continue the troubelshooting at my side
and test out your patch asap.

Thanks
Chin Liang

  reply	other threads:[~2016-12-07 13:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  5:35 [U-Boot] [PATCH v2] spi: cadence_qspi_apb: Use 32 bit indirect write transaction when possible Vignesh R
2016-11-25 16:51 ` Marek Vasut
2016-11-28  9:37   ` Vignesh R
2016-11-28 12:41     ` Marek Vasut
2016-11-29  4:58       ` Vignesh R
2016-11-29 10:53         ` Marek Vasut
2016-11-29 12:08           ` Vignesh R
2016-11-29 12:59             ` Marek Vasut
2016-11-30  4:06               ` Vignesh R
2016-11-28 14:15   ` See, Chin Liang
2016-11-29  5:25     ` Vignesh R
2016-12-01  1:26       ` Chin Liang See
2016-12-01  4:11         ` Vignesh R
2016-12-06  5:24           ` Vignesh R
2016-12-07 13:22             ` See, Chin Liang [this message]
2016-12-08  5:08               ` Vignesh R
2016-11-25 17:42 ` Jagan Teki
2016-11-25 17:46   ` Marek Vasut
2016-11-25 17:48     ` Jagan Teki
2016-11-28  9:58       ` Vignesh R

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=1481116966.1967.3.camel@intel.com \
    --to=chin.liang.see@intel.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