From: Vikas MANOCHA <vikas.manocha@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: DT: STM32F746: add u-boot, dm-pre-reloc property to sub nodes
Date: Wed, 12 Apr 2017 21:32:23 +0000 [thread overview]
Message-ID: <03c68f1f10064eeea1649f4d0424c44b@SFHDAG7NODE3.st.com> (raw)
In-Reply-To: <20170412172703.GA30757@bill-the-cat>
Hi Tom,
> -----Original Message-----
> From: Tom Rini [mailto:trini at konsulko.com]
> Sent: Wednesday, April 12, 2017 10:27 AM
> To: Vikas MANOCHA <vikas.manocha@st.com>
> Cc: u-boot at lists.denx.de; Ian Campbell <ijc@hellion.org.uk>; Hans de Goede <hdegoede@redhat.com>
> Subject: Re: [U-Boot] ARM: DT: STM32F746: add u-boot, dm-pre-reloc property to sub nodes
>
> On Tue, Apr 04, 2017 at 04:59:06PM -0700, Vikas Manocha wrote:
>
> > This patch is required for correct SPL device tree creation by fdtgrep
> > as fdtgrep looks for u-boot,dm-pre-reloc property of the node to
> > include it in the spl device tree.
> >
> > Not adding it in these subnodes ignores the pin muxing of peripherals
> > which is almost always in the subnodes.
> >
> > Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
> > ---
> > arch/arm/dts/stm32f746-disco.dts | 8 +++++++-
>
> This should be done in arch/arm/dts/stm32f746-u-boot.dtsi or similar, see scripts/Makefile.lib for the logic on how we pick these files
> up, thanks!
Really cool! Thanks for this information. I will create stm32f7-u-boot.dtsi to add this info & send v2.
Cheers,
Vikas
>
> --
> Tom
prev parent reply other threads:[~2017-04-12 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 23:59 [U-Boot] [PATCH] ARM: DT: STM32F746: add u-boot, dm-pre-reloc property to sub nodes Vikas Manocha
2017-04-12 17:27 ` [U-Boot] " Tom Rini
2017-04-12 21:32 ` Vikas MANOCHA [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=03c68f1f10064eeea1649f4d0424c44b@SFHDAG7NODE3.st.com \
--to=vikas.manocha@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox