Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1506609

Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories

From Marek Vasut <marex@denx.de>
Newsgroups linux.kernel
Subject Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories
Date 2016-10-23 00:40 +0200
Message-ID <svd7j-WP-1@gated-at.bofh.it> (permalink)
References <soT1D-tV-5@gated-at.bofh.it> <sv2lz-2ER-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 10/22/2016 01:00 PM, Jagan Teki wrote:
> On Wed, Oct 5, 2016 at 5:30 PM, Cyrille Pitchen
> <cyrille.pitchen@atmel.com> wrote:
>> Hi all,
>>
>> This series extends support of SPI protocols to new protocols such as
>> SPI x-2-2 and SPI x-4-4. Also spi_nor_scan() tries now to select the right
>> op codes, timing parameters (number of mode and dummy cycles) and erase
>> sector size by parsing the Serial Flash Discoverable Parameter (SFDP)
>> tables, when available, as defined in the JEDEC JESD216 specifications.
>>
>> When SFDP tables are not available, legacy settings are still used for
>> backward compatibility (SPI and earlier QSPI memories).
>>
>> Support of SPI memories >128Mbits is also improved by using the 4byte
>> address instruction set, when available. Using those dedicated op codes
>> is stateless as opposed to enter the 4byte address mode, hence a better
>> compatibility with some boot loaders which expect to use 3byte address
>> op codes.
> 
> The memories which are > 128Mbits should have 4-bytes addressing
> support based on my experience, do you think BAR is also required
> atleast from spi-nor side?

Yes, I believe BAR is still required for broken/dumb flash chips.
Not all chips > 16 MiB support dedicated 4-byte addressing opcodes :-(

-- 
Best regards,
Marek Vasut

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories Jagan Teki <jagan@openedev.com> - 2016-10-22 13:10 +0200
  Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI  memories Marek Vasut <marex@denx.de> - 2016-10-23 00:40 +0200
    Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories Jagan Teki <jagan@openedev.com> - 2016-10-24 09:50 +0200
      Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI  memories Marek Vasut <marex@denx.de> - 2016-10-24 13:50 +0200
      Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI  memories Cyrille Pitchen <cyrille.pitchen@atmel.com> - 2016-10-24 14:10 +0200
        Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI  memories Cyrille Pitchen <cyrille.pitchen@atmel.com> - 2016-10-24 16:10 +0200
          Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories Jagan Teki <jagan@openedev.com> - 2016-10-25 11:10 +0200
            Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories Jagan Teki <jagan@openedev.com> - 2016-10-25 22:10 +0200

csiph-web