From: Peng Fan <B51431@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/5] qspi: qspi support for mx6sxsabresd
Date: Wed, 31 Dec 2014 17:58:15 +0800 [thread overview]
Message-ID: <54A3C8B7.4030207@freescale.com> (raw)
In-Reply-To: <CAD6G_RRfKB4pEbgOUKCZj3FqsVBp+BD8A9OiwKRuC9-2JkRzrg@mail.gmail.com>
On 12/31/2014 5:35 PM, Jagan Teki wrote:
> On 31 December 2014 at 08:31, Peng Fan <Peng.Fan@freescale.com> wrote:
>> This patch set is to support qspi for mx6sxsabresd board.
>>
>> To mx6sxsabresd Revb board, 32M flash is used, but in header file,
>> CONFIG_SPI_FLASH_BAR is not defined, and we still use SZ_16M. The LUT
>> initialization qspi_set_lut function uses 32BIT addr, however
>> CONFIG_SPI_FLASH_BAR and 24BIT addr should be used to access
>> bigger than 16MB size flash, and BRRD/BRWR should also be supported.
>> Future patches will fix this.
>
> Please do remember your self, for next patches. of-course I have added this
> note on "[U-Boot,v4,5/5] imx:mx6sxsabresd add qspi support" commit body.
>
Thanks. Actually I am doing the work.
>>
>> Since flash opcodes are not recommended to use in driver level, use
>> QSPI_CMD_xx to replace OPCODE_xx. It is qspi controller's feature
>> to program LUT with QSPI_CMD_xx which same value with OPCODE_xx.
>>
>> Since Revb board's qspi flash support 4K erase, 4K erase is added in driver.
>>
>> Peng Fan (5):
>> QuadSPI: use QSPI_CMD_xx instead of flash opcodes
>> QuadSPI: use correct amba_base
>> arm:mx6sx add QSPI support
>> imx:qspi add 4K erase support
>> imx:mx6sxsabresd add qspi support
>>
>> arch/arm/cpu/armv7/mx6/clock.c | 50 ++++++++++
>> arch/arm/include/asm/arch-mx6/clock.h | 1 +
>> arch/arm/include/asm/arch-mx6/imx-regs.h | 12 +--
>> board/freescale/mx6sxsabresd/mx6sxsabresd.c | 40 ++++++++
>> drivers/spi/fsl_qspi.c | 137 +++++++++++++++++++---------
>> include/configs/mx6sxsabresd.h | 12 +++
>> 6 files changed, 205 insertions(+), 47 deletions(-)
>>
>> --
>> 1.8.4
>>
>>
>
> Applied to u-boot-spi/master
>
> thanks!
>
Regards,
Peng.
prev parent reply other threads:[~2014-12-31 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 3:01 [U-Boot] [PATCH v4 0/5] qspi: qspi support for mx6sxsabresd Peng Fan
2014-12-31 3:01 ` [U-Boot] [PATCH v4 1/5] QuadSPI: use QSPI_CMD_xx instead of flash opcodes Peng Fan
2014-12-31 3:01 ` [U-Boot] [PATCH v4 2/5] QuadSPI: use correct amba_base Peng Fan
2014-12-31 3:01 ` [U-Boot] [PATCH v4 3/5] arm:mx6sx add QSPI support Peng Fan
2014-12-31 3:01 ` [U-Boot] [PATCH v4 4/5] imx:qspi add 4K erase support Peng Fan
2014-12-31 3:01 ` [U-Boot] [PATCH v4 5/5] imx:mx6sxsabresd add qspi support Peng Fan
2014-12-31 9:35 ` [U-Boot] [PATCH v4 0/5] qspi: qspi support for mx6sxsabresd Jagan Teki
2014-12-31 9:58 ` Peng Fan [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=54A3C8B7.4030207@freescale.com \
--to=b51431@freescale.com \
--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