From: sbabic at denx.de <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] pinctrl: imx: Define imx6_pinctrl_soc_info in .data section
Date: Tue, 11 Jun 2019 08:44:42 +0000 (UTC) [thread overview]
Message-ID: <20190611084445.0C2BBC220C0@lists.denx.de> (raw)
In-Reply-To: <20190423144451.31949-1-lukma@denx.de>
> This commit is necessary to be able to re-use the pinctrl code in early
> SPL to properly configure pins.
> The problem is that those "static" structures (without explicit
> initialization) are placed in the SDRAM area, which corresponds to
> u-boot proper (not even SPL).
> Hence, when one wants to configure pins before relocation via DTS/DM,
> the board hangs (imx6q SoC powered one) as only OCRAM area is available
> (0x009xxxxx).
> This commit prevents from this issue by moving the imx6_pinctrl_soc_info
> structure to data section (from BSS).
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> Reviewed-by: Peng Fan <peng.fan@nxp.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
=====================================================================
prev parent reply other threads:[~2019-06-11 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 14:44 [U-Boot] [PATCH v2] pinctrl: imx: Define imx6_pinctrl_soc_info in .data section Lukasz Majewski
2019-04-24 1:39 ` Peng Fan
2019-06-11 8:44 ` sbabic at denx.de [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=20190611084445.0C2BBC220C0@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