From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/18] sf: fix support of QSPI memories and controllers
Date: Tue, 15 Mar 2016 20:17:30 +0100 [thread overview]
Message-ID: <56E85FCA.40704@denx.de> (raw)
In-Reply-To: <56E852BF.1080000@openedev.com>
On 03/15/2016 07:21 PM, Jagan Teki wrote:
> On Tuesday 15 March 2016 11:42 PM, Cyrille Pitchen wrote:
>> Hi all,
>>
>> This series of patches fixes and extend the support of QSPI memories
>> in the SPI flash framework. The updates are split into many parts to
>> make it easier to understand and review but they should be considered
>> as a whole.
>>
>> This was tested on a Atmel sama5d2 xplained board with a Micron n25q128a
>> memory.
>>
>> Best regards,
>>
>> Cyrille
>>
>> Cyrille Pitchen (18):
>> Revert "sf: Fix quad bit set for micron devices"
>> sf: call spi_claim_bus() and spi_release_bus() only once per read,
>> write or erase
>> sf: replace spi_flash_read_common() calls by spi_flash_cmd_read()
>> sf: remove spi_flash_write_common()
>> sf: export spi_flash_wait_ready() function
>> sf: share erase generic algorithm
>> sf: share write generic algorithm
>> sf: share read generic algorithm
>> sf: add hooks to handle register read and write operations
>> sf: move support of SST flash into generic spi_flash_write_alg()
>> sf: fix selection of supported READ commands for QSPI memories
>> sf: fix detection of QSPI memories when they boot in Quad or Dual mode
>> sf: add helper function to set the number of dummy bytes
>> sf: add 4byte address opcodes
>> sf: prepare next fixes to support of QSPI memories by manufacturer
>> sf: fix support of Micron memories
>> ARM: at91: clock: add function to get QSPI clocks
>> sf: add driver for Atmel QSPI controller
>
> Appreciate for the work, we're working on spi-nor framework[1] planning
> to push in couple of weeks. Will let you know once it merged so that you
> can add your changes on top of that.
>
> [1]
> http://git.denx.de/?p=u-boot/u-boot-spi.git;a=shortlog;h=refs/heads/spi-nor-next
The patchset seems to be in a sensible shape to me, so maybe we should
do it the other way around -- get this in and have you rebase your V6(?)
patchset on top of it -- since clearly your patchset will take some more
time to ripe.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-03-15 19:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 18:12 [U-Boot] [PATCH 00/18] sf: fix support of QSPI memories and controllers Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 01/18] Revert "sf: Fix quad bit set for micron devices" Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 02/18] sf: call spi_claim_bus() and spi_release_bus() only once per read, write or erase Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 03/18] sf: replace spi_flash_read_common() calls by spi_flash_cmd_read() Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 04/18] sf: remove spi_flash_write_common() Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 05/18] sf: export spi_flash_wait_ready() function Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 06/18] sf: share erase generic algorithm Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 07/18] sf: share write " Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 08/18] sf: share read " Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 09/18] sf: add hooks to handle register read and write operations Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 10/18] sf: move support of SST flash into generic spi_flash_write_alg() Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 11/18] sf: fix selection of supported READ commands for QSPI memories Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 12/18] sf: fix detection of QSPI memories when they boot in Quad or Dual mode Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 13/18] sf: add helper function to set the number of dummy bytes Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 14/18] sf: add 4byte address opcodes Cyrille Pitchen
2016-03-21 8:58 ` [U-Boot] [PATCH 14/18 v2] " Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 15/18] sf: prepare next fixes to support of QSPI memories by manufacturer Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 16/18] sf: fix support of Micron memories Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 17/18] ARM: at91: clock: add function to get QSPI clocks Cyrille Pitchen
2016-03-15 18:12 ` [U-Boot] [PATCH 18/18] sf: add driver for Atmel QSPI controller Cyrille Pitchen
2016-03-15 18:21 ` [U-Boot] [PATCH 00/18] sf: fix support of QSPI memories and controllers Jagan Teki
2016-03-15 19:17 ` Marek Vasut [this message]
2016-03-16 13:30 ` Cyrille Pitchen
2016-03-16 14:14 ` Jagan Teki
2016-03-16 16:23 ` Albert ARIBAUD
2016-03-16 16:34 ` Jagan Teki
2016-03-17 7:30 ` Albert ARIBAUD
2016-03-16 16:30 ` Cyrille Pitchen
2016-03-16 16:41 ` [U-Boot] [PATCH 1/4] rework board config files Cyrille Pitchen
2016-03-16 16:41 ` [U-Boot] [PATCH 2/4] sama5d2_xplained: add support of QSPI controllers Cyrille Pitchen
2016-03-16 16:41 ` [U-Boot] [PATCH 3/4] dts: add dts file for Atmel sama5d2 xplained board Cyrille Pitchen
2016-03-16 16:41 ` [U-Boot] [PATCH 4/4] sf: fix sf probe Cyrille Pitchen
2016-03-18 13:48 ` [U-Boot] [PATCH 00/18] sf: fix support of QSPI memories and controllers Stefan Roese
2016-03-18 15:18 ` Cyrille Pitchen
2016-03-21 9:07 ` Jagan Teki
2016-03-21 13:13 ` Cyrille Pitchen
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=56E85FCA.40704@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