From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/8] arm: socfpga: fix device trees to work with DM serial
Date: Mon, 13 Aug 2018 09:28:28 -0400 [thread overview]
Message-ID: <20180813132828.GR29229@bill-the-cat> (raw)
In-Reply-To: <CAAh8qswLrRxxtFP0K-qm7mcSa7tr4MaAe75K5rf-zpFYRQWKiA@mail.gmail.com>
On Mon, Aug 13, 2018 at 03:25:19PM +0200, Simon Goldschmidt wrote:
> On Mon, Aug 13, 2018 at 3:17 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Mon, Aug 13, 2018 at 09:33:45AM +0200, Simon Goldschmidt wrote:
> >
> > > Device trees need to have the serial console device available
> > > before relocation and require a stdout-path in chosen at least
> > > for SPL to have a console.
> > >
> > > Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
> > > ---
> > >
> > > Changes in v3:
> > > - moved uart0's "u-boot,dm-pre-reloc;" from socfpga.dtsi to board
> > > specific dts files since this can change per board
> >
> > Why are these not in socfpga-u-boot.dtsi ? We have the mechanism to
> > grab CONFIG_SYS_CPU/CONFIG_SYS_SOC/CONFIG_SYS_VENDOR-u-boot.dtsi
> > automatically so that we don't have to modify the files we sync in from
> > upstream.
>
> Ehrm, I don't know, really. The DTS files for socfpga already have
> many U-Boot specifics and are quite different to Linux. It might make
> sense to sync them, but do we really have to do this for 2018.09?
>
> Keep in mind that this series exists to fix that 2018.07 broke on these boards.
Well, I think given that you're adding these changes right now, they
should be added to the correct file so that they aren't lost on re-sync
later. It would be adding:
&uart0 {
u-boot,dm-pre-reloc;
};
once to arch/arm/dts/socfpga-u-boot.dtsi rather than for every board.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180813/6f8bde14/attachment.sig>
next prev parent reply other threads:[~2018-08-13 13:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 7:33 [U-Boot] [PATCH v3 0/8] Get socfpga gen5 SPL working again Simon Goldschmidt
2018-08-13 7:33 ` [U-Boot] [PATCH v3 1/8] arm: socfpga: fix SPL on gen5 after moving to DM serial Simon Goldschmidt
2018-08-13 7:33 ` [U-Boot] [PATCH v3 2/8] arm: socfpga: fix device trees to work with " Simon Goldschmidt
2018-08-13 13:16 ` Tom Rini
2018-08-13 13:25 ` Simon Goldschmidt
2018-08-13 13:28 ` Tom Rini [this message]
2018-08-13 13:29 ` Marek Vasut
2018-08-13 13:33 ` Tom Rini
2018-08-13 13:36 ` Simon Goldschmidt
2018-08-13 13:41 ` Tom Rini
2018-08-13 13:48 ` Marek Vasut
2018-08-13 13:48 ` Simon Goldschmidt
2018-08-13 7:33 ` [U-Boot] [PATCH v3 3/8] arm: socfpga: spl_gen5: clean up malloc_base assignment Simon Goldschmidt
2018-08-13 7:33 ` [U-Boot] [PATCH v3 4/8] arm: socfpga: cyclone5: handle debug uart Simon Goldschmidt
2018-08-13 7:33 ` [U-Boot] [PATCH v3 5/8] arm: socfpga: fix U-Boot running from fpga OnChip RAM Simon Goldschmidt
2018-08-13 13:23 ` Marek Vasut
2018-08-13 13:33 ` Simon Goldschmidt
2018-08-13 13:49 ` Marek Vasut
2018-08-13 7:33 ` [U-Boot] [PATCH v3 6/8] arm: socfpga: gen5: combine some init code for SPL and U-Boot Simon Goldschmidt
2018-08-13 13:25 ` Marek Vasut
2018-08-13 7:33 ` [U-Boot] [PATCH v3 7/8] arm: socfpga: fix SPL booting from fpga OnChip RAM Simon Goldschmidt
2018-08-13 13:26 ` Marek Vasut
2018-08-13 13:32 ` Simon Goldschmidt
2018-08-13 13:51 ` Marek Vasut
2018-08-13 7:33 ` [U-Boot] [PATCH v3 8/8] malloc_simple: calloc: don't call memset if malloc failed Simon Goldschmidt
2018-08-13 13:28 ` [U-Boot] [PATCH v3 0/8] Get socfpga gen5 SPL working again Marek Vasut
2018-08-13 13:34 ` Simon Goldschmidt
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=20180813132828.GR29229@bill-the-cat \
--to=trini@konsulko.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