From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/5] package/freescale-imx: Add option for DDR FW need
Date: Tue, 26 May 2020 14:43:56 +0200 [thread overview]
Message-ID: <20200526124356.GA438358@p1g2> (raw)
In-Reply-To: <1590422530-4788-2-git-send-email-stephane.viau@oss.nxp.com>
Hi Stephane,
On Mon, May 25, 2020 at 06:02:06PM +0200, Stephane Viau wrote:
> Only some i.MX8 needs a DDR training firmware (8M, 8MM, 8MN). Some other
> i.MX8 (QuadMax, QuadXPlus) rely on system controller for that task.
>
> Suggested-by: Julien Olivain <julien.olivain@oss.nxp.com>
> Signed-off-by: Stephane Viau <stephane.viau@oss.nxp.com>
> ---
> v3:
> - let the others 'select' this newly introduced option instead of
> 'default y' it. I believe this option is still required since we
> only want to choose a DDR binary for the i.MX 8M platforms. (Gary)
I've tested this patch and confirm it is working properly.
Note that using 'select' instead of 'default y if...' was suggested by
Yann on IRC.
Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com>
Regards,
Gary
next prev parent reply other threads:[~2020-05-26 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 16:02 [Buildroot] [PATCH v2 0/5] imx: add i.MX8M Nano EVK board support Stephane Viau
2020-05-25 16:02 ` [Buildroot] [PATCH v3 1/5] package/freescale-imx: Add option for DDR FW need Stephane Viau
2020-05-26 12:43 ` Gary Bisson [this message]
2020-05-25 16:02 ` [Buildroot] [PATCH v3 2/5] package/freescale-imx/firmware-imx: add choice for DDR training binaries Stephane Viau
2020-05-26 12:48 ` Gary Bisson
2020-05-25 16:02 ` [Buildroot] [PATCH v3 3/5] board/freescale/common/imx: use generic ddr_fw.bin name Stephane Viau
2020-05-26 12:48 ` Gary Bisson
2020-05-25 16:02 ` [Buildroot] [PATCH v3 4/5] board/freescale/common/imx: add support for i.MX8M Nano Stephane Viau
2020-05-25 16:02 ` [Buildroot] [PATCH v3 5/5] configs/freescale_imx8mnevk: new defconfig Stephane Viau
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=20200526124356.GA438358@p1g2 \
--to=gary.bisson@boundarydevices.com \
--cc=buildroot@busybox.net \
/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