From: Lucas Stach <l.stach@pengutronix.de>
To: Christian Hemp <christian.hemp@posteo.de>, barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: phyCORE-i.MX8M SOM support
Date: Mon, 11 Feb 2019 12:00:58 +0100 [thread overview]
Message-ID: <1549882858.2546.3.camel@pengutronix.de> (raw)
In-Reply-To: <20190206184122.14423-1-christian.hemp@posteo.de>
Hi Christian,
Am Mittwoch, den 06.02.2019, 19:41 +0100 schrieb Christian Hemp:
> The phyCORE-i.MX8M aka PCL-066 is a SoM containing a i.MX8M SoC.
>
> phyCORE-i.MX8M:
> - 1GB LPDDR4 RAM
> - eMMC
> - microSD
> - Ethernet
>
> Signed-off-by: Christian Hemp <christian.hemp@posteo.de>
> ---
> arch/arm/boards/Makefile | 1 +
> arch/arm/boards/phytec-som-imx8m/.gitignore | 1 +
> arch/arm/boards/phytec-som-imx8m/Makefile | 2 +
> arch/arm/boards/phytec-som-imx8m/board.c | 55 +
> arch/arm/boards/phytec-som-imx8m/ddr.h | 28 +
> arch/arm/boards/phytec-som-imx8m/ddr_init.c | 225 +++++
> .../boards/phytec-som-imx8m/ddrphy_train.c | 947 ++++++++++++++++++
> .../flash-header-phycore-imx8mq.imxcfg | 5 +
> arch/arm/boards/phytec-som-imx8m/lowlevel.c | 127 +++
> arch/arm/configs/imx_v8_defconfig | 2 +
> arch/arm/dts/Makefile | 1 +
> arch/arm/dts/imx8mq-phytec-phycore-som.dts | 328 ++++++
> arch/arm/mach-imx/Kconfig | 7 +
> images/Makefile.imx | 5 +
> 14 files changed, 1734 insertions(+)
> create mode 100644 arch/arm/boards/phytec-som-imx8m/.gitignore
> create mode 100644 arch/arm/boards/phytec-som-imx8m/Makefile
> create mode 100644 arch/arm/boards/phytec-som-imx8m/board.c
> create mode 100644 arch/arm/boards/phytec-som-imx8m/ddr.h
> create mode 100644 arch/arm/boards/phytec-som-imx8m/ddr_init.c
> create mode 100644 arch/arm/boards/phytec-som-imx8m/ddrphy_train.c
> create mode 100644 arch/arm/boards/phytec-som-imx8m/flash-header-phycore-imx8mq.imxcfg
> create mode 100644 arch/arm/boards/phytec-som-imx8m/lowlevel.c
> create mode 100644 arch/arm/dts/imx8mq-phytec-phycore-som.dts
The other supported i.MX8M boards are using a "imx8mq" name tag. I
would really like to see some consistency here, as the i.MX8 naming in
general is already confusing in itself, so we shouldn't add to this
confusion by calling the same SoC both mx8m and mx8mq.
Regards,
Lucas
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-02-11 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 18:41 Christian Hemp
2019-02-07 1:20 ` Andrey Smirnov
2019-02-11 8:20 ` Sascha Hauer
2019-02-11 11:00 ` Lucas Stach [this message]
2019-02-13 6:14 ` Oleksij Rempel
2019-02-14 18:20 ` Christian
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=1549882858.2546.3.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=christian.hemp@posteo.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