public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6] sf: Turn SPI flash chip into 3-Byte address mode
Date: Thu, 13 Aug 2015 13:53:05 +0200	[thread overview]
Message-ID: <55CC8521.3070509@denx.de> (raw)
In-Reply-To: <CAD6G_RTqM+QXUUhfPe=g_HjGvEcWDrfdETOSULF+fcEoyUa+qQ@mail.gmail.com>

Jagan,

On 13.08.2015 13:45, Jagan Teki wrote:
>>> Please correct me if I'm wrong, but AFAIU this BAR thing
>>> (CONFIG_SPI_FLASH_BAR) doesn't support to address e.g. a 64MiB SPI flash
>>> contiguously. Only 16MiB areas. So for example its not possible to put
>>> UBI/UBIFS in such a big partition.
>
> Stefan,
>
> No, BAR is accessing flash > 16MiB in 3-byte addressing mode, for your
> example of
> 64MiB flash, it can grouped into 4 16MiB regions means 4 bank vales
> bank0 to bank3
>
> Based on the sf read/erase/write flash offsets, that particular bank
> will enable an do
> the relevant operations.
>
> In-spite of having 4 byte addressing operations BAR should do exactly
> same with existing
> 3-byte addressing.

Okay, thanks for the explanation. If this really is the case, and this 
BAR support will seamlessly enable the access to the complete flash 
area, then the 4-byte mode should really not be necessary.

I'm wondering though about 2 things:

a) Do all SPI NOR flash chips support this BAR mode?

b) If yes, why isn't BAR enabled per default?

c) Why doesn't the Linux kernel use this BAR mode?

Thanks,
Stefan

  reply	other threads:[~2015-08-13 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  6:18 [U-Boot] [PATCH V6] sf: Turn SPI flash chip into 3-Byte address mode Zhiqiang Hou
2015-08-13  9:17 ` Siva Durga Prasad Paladugu
2015-08-13 10:50   ` Hou Zhiqiang
2015-08-13 11:21     ` Stefan Roese
2015-08-13 11:27       ` Siva Durga Prasad Paladugu
2015-08-13 11:45         ` Jagan Teki
2015-08-13 11:53           ` Stefan Roese [this message]
2015-08-17  8:07             ` Jagan Teki
2015-08-13 12:48           ` Siva Durga Prasad Paladugu
2015-08-14  4:07             ` Hou Zhiqiang
2015-08-14  4:44               ` Siva Durga Prasad Paladugu
2015-08-17  8:13             ` Jagan Teki
2015-08-17  8:56               ` Siva Durga Prasad Paladugu
2015-08-17  9:12                 ` Jagan Teki
2015-08-17  9:14                   ` Siva Durga Prasad Paladugu
2015-08-17  9:21                     ` Jagan Teki
2015-08-14  4:55 ` Siva Durga Prasad Paladugu
2015-08-14 10:01   ` Hou Zhiqiang
2015-08-19 12:26   ` Hou Zhiqiang
2016-01-27  5:47     ` Zhiqiang Hou

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=55CC8521.3070509@denx.de \
    --to=sr@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