public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 5/7] mips: ath79: add spi driver
Date: Tue, 2 Feb 2016 17:07:04 +0100	[thread overview]
Message-ID: <201602021707.04782.marex@denx.de> (raw)
In-Reply-To: <BLU436-SMTP181A897A1CCDAC7A4B0E778FFDF0@phx.gbl>

On Tuesday, February 02, 2016 at 04:38:34 PM, Wills Wang wrote:
> On Wednesday, January 27, 2016 09:33 AM, Marek Vasut wrote:
> > On Saturday, January 16, 2016 at 07:13:51 PM, Wills Wang wrote:
> >> Reviewed-by: Thomas Chou <thomas@wytron.com.tw>
> >> 
> >> Signed-off-by: Wills Wang <wills.wang@live.com>
> >> ---
> >> 
> >> Changes in v7:
> >> - Define spi_cs_activate/spi_cs_deactivate
> >> - Rename MHZ to ATH79_SPI_MHZ
> >> - Use clrsetbits_32
> > 
> > The driver gets stuck if I do:
> > 
> > => sf probe
> > => sf read 0x81000000 0 0x20000
> > 
> > If I transfer only 0x10000 , it doesn't get stuck.
> > 
> > Best regards,
> > Marek Vasut
> 
> ap121 # sf probe
> SF: Detected W25Q64CV with page size 256 Bytes, erase size 4 KiB, total
> 8 MiB, mapped at 9f000000
> ap121 # sf read 0x81000000 0 0x20000
> device 0 offset 0x0, size 0x20000
> SF: 131072 bytes @ 0x0 Read: OK
> ap121 # sf read 0x81000000 0 0x10000
> device 0 offset 0x0, size 0x10000
> SF: 65536 bytes @ 0x0 Read: OK
> ap121 # sf read 0x81000000 0 0x1000
> device 0 offset 0x0, size 0x1000
> SF: 4096 bytes @ 0x0 Read: OK
> ap121 # sf read 0x81000000 0 0x100
> device 0 offset 0x0, size 0x100
> SF: 256 bytes @ 0x0 Read: OK

It's nice that it works on your custom hardware.

Best regards,
Marek Vasut

  reply	other threads:[~2016-02-02 16:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1452968033-4460-1-git-send-email-wills.wang@live.com>
2016-01-16 18:13 ` [U-Boot] [PATCH v7 1/7] mips: add base support for QCA/Atheros ath79 SOCs Wills Wang
2016-01-16 19:19   ` Marek Vasut
2016-01-22  9:02     ` Wills Wang
2016-01-22 14:44       ` Marek Vasut
2016-01-23  1:31         ` Wills Wang
2016-01-23  3:06           ` Marek Vasut
2016-01-23  5:25             ` Wills Wang
2016-02-01 19:19   ` Marek Vasut
2016-01-16 18:13 ` [U-Boot] [PATCH v7 2/7] mips: ath79: add support for AR933x SOCs Wills Wang
2016-01-16 19:31   ` Marek Vasut
2016-01-22  9:10     ` Wills Wang
2016-01-22 14:46       ` Marek Vasut
2016-01-16 18:13 ` [U-Boot] [PATCH v7 3/7] mips: ath79: add support for QCA953x SOCs Wills Wang
2016-01-16 19:33   ` Marek Vasut
2016-01-22  9:17     ` Wills Wang
2016-01-22 14:49       ` Marek Vasut
2016-01-16 18:13 ` [U-Boot] [PATCH v7 4/7] mips: ath79: add serial driver for ar933x SOC Wills Wang
2016-01-16 19:17   ` Daniel Schwierzeck
2016-01-18  3:58   ` Simon Glass
2016-01-16 18:13 ` [U-Boot] [PATCH v7 5/7] mips: ath79: add spi driver Wills Wang
2016-01-16 19:37   ` Daniel Schwierzeck
2016-01-22  9:24     ` Wills Wang
2016-01-27  1:33   ` Marek Vasut
2016-02-02 15:38     ` Wills Wang
2016-02-02 16:07       ` Marek Vasut [this message]
2016-01-16 18:13 ` [U-Boot] [PATCH v7 6/7] mips: ath79: add AP121 reference board Wills Wang
2016-01-16 19:50   ` Daniel Schwierzeck
2016-01-22  9:36     ` Wills Wang
2016-01-16 18:13 ` [U-Boot] [PATCH v7 7/7] mips: ath79: add AP143 " Wills Wang
2016-01-16 19:53   ` Daniel Schwierzeck

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=201602021707.04782.marex@denx.de \
    --to=marex@denx.de \
    --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