From: sbabic at denx.de <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] imx: define ARCH_MXC for i.MX8/8M/7ULP
Date: Tue, 11 Jun 2019 08:44:45 +0000 (UTC) [thread overview]
Message-ID: <20190611084504.4CF72C21E16@lists.denx.de> (raw)
> Without this definition, fsl_esdhc will access reserved registers
> on i.MX chips, so define ARCH_MXC to fix it.
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next reply other threads:[~2019-06-11 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 8:44 sbabic at denx.de [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-09 8:33 [U-Boot] [PATCH 1/2] imx: drop imx-regs.h Peng Fan
2019-05-09 8:33 ` [U-Boot] [PATCH 2/2] imx: define ARCH_MXC for i.MX8/8M/7ULP Peng Fan
2019-05-09 11:05 ` Fabio Estevam
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=20190611084504.4CF72C21E16@lists.denx.de \
--to=sbabic@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