From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM:MX6SX Add QuadSPI support for mx6sxsabresd
Date: Wed, 10 Sep 2014 21:43:35 +0800 [thread overview]
Message-ID: <54105587.5090309@gmail.com> (raw)
In-Reply-To: <CAOMZO5BVePY0NtK=R5gGpfeoVD4g73SDW_PX8=3BXm9OJoENvw@mail.gmail.com>
On 09/10/2014 08:40 PM, Fabio Estevam wrote:
> On Wed, Sep 10, 2014 at 3:16 AM, Peng Fan <Peng.Fan@freescale.com> wrote:
>> From: Peng Fan <van.freenix@gmail.com>
>>
>> Add QuadSPI support for mx6sxsabresd board.
>>
>> There are two 16MB S25FL128S flashes on board. They are connected to
>> QSPI2 interface. i.MX6SX supports two QuadSPI interfaces, QSPI1/2.
>> The two flash devices are connected to A1/B1 of QSPI2.
>>
>> Signed-off-by: Peng Fan <van.freenix@gmail.com>
>> ---
>> arch/arm/cpu/armv7/mx6/clock.c | 50 +++++++++++++++++++++++++++++
>> arch/arm/include/asm/arch-mx6/clock.h | 3 ++
>> board/freescale/mx6sxsabresd/mx6sxsabresd.c | 40 +++++++++++++++++++++++
>> drivers/spi/fsl_qspi.c | 30 +++++++++++++++++
>> include/configs/mx6sxsabresd.h | 14 ++++++++
>
> I would split this in two patches: one that adds qspi support for the
> mx6solox SoC and another one that adds qspi support to the
> mx6sxsabresd board.
ok. I'll correct this. Thanks for reviewing.
Regards,
Peng.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2014-09-10 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 6:16 [U-Boot] [PATCH 0/3] Add QSPI support for mx6sxsabresd board Peng Fan
2014-09-10 6:16 ` [U-Boot] [PATCH 1/3] ARM:MX6SX Add QuadSPI support for mx6sxsabresd Peng Fan
2014-09-10 12:40 ` Fabio Estevam
2014-09-10 13:43 ` Peng Fan [this message]
2014-09-10 6:16 ` [U-Boot] [PATCH 2/3] QSPI: Enable write device registers Peng Fan
2014-09-10 6:16 ` [U-Boot] [PATCH 3/3] QSPI: Enable QSPI AHB read for MX6SX Peng Fan
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=54105587.5090309@gmail.com \
--to=van.freenix@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.