From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] spi-nor: Choices of choosing bank or 4-byte addressing
Date: Mon, 17 Aug 2015 19:56:13 +0200 [thread overview]
Message-ID: <201508171956.13254.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RTmd4uZ-KknfE6MOtZ-CZT3fA+oX-fQEFwrtdmuU7pxiQ@mail.gmail.com>
On Monday, August 17, 2015 at 03:54:50 PM, Jagan Teki wrote:
> For accessing SPI-NOR flash's with > 16MiB we have two choices like
> Bank/Extended and 4-byte addressing register support.
>
> Status in u-boot:
> 1) BAR (Bank/Extended)
> - Added support in u-boot already, tested
>
> 2) 4-byte addressing
> - No support yet
> - Hou Zhiqiang sent patches, those are review.
Patchwork or gmane link would really help.
> Ideally we may support any one of them, but there is some situation
> where (q)spi controller can only support 3-byte addressing (not
> supporting 4-byte addressing) but the connected flash could be >
> 16MiB, example: Xilinx Zynq QSPI
>
> In this case as controller not supporting 4-byte commands we must use
> BAR for accessing > 16MiB flash's.
So the controller in QSPI controller in Zynq is explicitly broken ?
> Siva, suggested like from controller driver (spi_slave {} ) we need to
> inform the flash about addressing width, so-that flash can configure
> accordingly.
Absolutelly not, you're mixing together SPI driver and a SPI NOR driver.
> I indeed agree with this, and if we have both supported then the flash
> will configure accordingly with controller check.
>
> Pls- share for any other thoughts.
>
> thanks!
Best regards,
Marek Vasut
prev parent reply other threads:[~2015-08-17 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 13:54 [U-Boot] spi-nor: Choices of choosing bank or 4-byte addressing Jagan Teki
2015-08-17 17:56 ` Marek Vasut [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=201508171956.13254.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