public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards
Date: Tue, 18 Jun 2019 11:03:52 +0200	[thread overview]
Message-ID: <196aa8982a2d9bc2fec5408fe4d84615bbfb2c2b.camel@bootlin.com> (raw)
In-Reply-To: <CAMty3ZA-wf7tRE=+38SujjXXNGC-pb-m9RzgxFBops6w5n9qzQ@mail.gmail.com>

Hi,

On Tue, 2019-06-18 at 14:27 +0530, Jagan Teki wrote:
> On Tue, Jun 18, 2019 at 1:55 PM Paul Kocialkowski
> <paul.kocialkowski@bootlin.com> wrote:
> > Hi,
> > 
> > On Mon, 2019-06-17 at 15:24 +0800, xieqinick at gmail.com wrote:
> > > From: Nick Xie <nick@khadas.com>
> > 
> > Was this tested with SPL support? I don't see DRAM configuration here
> > so it seems that it relies on the non-free rockchip loader.
> > 
> > If that is the case, could you please indicate that in the commit
> > message?
> > 
> > To maintainers: please do not merge this series before DRAM init and
> > SPL support is available for these boards.
> > 
> > It seems that other RK3399 boards were merged without SPL support and
> > sofar, I have the feeling that nobody cared to explain how we got into
> > this broken situation. Please don't merge any more such board.
> 
> fyi: no rk3399 boards were merged w/o SPL. lpddr4 boards were merged
> with TPL-enabled (which was discussed on the threads, if you remember)
> with below boot chain.
> 
> rkbin (TPL) -> SPL -> U-Boot proper
> 
> Same case for this board as well.

Here is a quote from Philipp Tomsich on the thread we discussed this:

" On some boards, there will be no TPL and only a SPL stage that will
initialise DRAM (as the move to having TPL on the RK3399 is optional).

I agree with Paul that the DRAM init should be part of U-Boot whenever
we add new boards and make an open DRAM init a prerequisite. "

So even if I frequently confuse SPL and TPL, it doesn't change the fact
that no board should be merged without proper DRAM init.

Please stop pushing for merging these boards. I'm not sure what we
should do about the boards that were merged already without DRAM init,
but maybe they should be reverted.

Cheers,

Paul

-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

  reply	other threads:[~2019-06-18  9:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 11:19 [U-Boot] [PATCH] rockchip: rk3399: Add Khadas Edge board support xieqinick at gmail.com
2019-05-24 18:23 ` Jagan Teki
2019-05-25  3:44   ` Nick Xie
2019-05-25  5:57     ` Jagan Teki
2019-07-26  8:00       ` Kever Yang
2019-07-26  9:55         ` Nick
2019-07-26 13:52           ` Chris Webb
2019-07-27  1:09             ` Nick Xie
2019-07-27  9:25               ` Chris Webb
2019-06-17  7:24 ` [U-Boot] [PATCH v2] arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards xieqinick at gmail.com
2019-06-18  7:21   ` Kever Yang
2019-06-18  8:25   ` Paul Kocialkowski
2019-06-18  8:57     ` Jagan Teki
2019-06-18  9:03       ` Paul Kocialkowski [this message]
2019-06-18 10:08         ` Kever Yang
2019-06-18 12:47           ` Paul Kocialkowski
2019-06-18 16:12             ` Mark Kettenis
2019-06-19  1:42               ` Kever Yang
2019-06-19 16:54                 ` Paul Kocialkowski
2019-06-20  3:24                   ` Kever Yang
2019-06-21 11:34                     ` Heiko Stuebner
2019-06-21 11:58                       ` Paul Kocialkowski
2019-06-21 12:52                       ` Mark Kettenis
2019-06-21 13:05                         ` Paul Kocialkowski
2019-06-21 13:08                         ` Heiko Stuebner
2019-06-17  8:56 ` xieqinick at gmail.com
2019-06-18  7:21   ` Jagan Teki

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=196aa8982a2d9bc2fec5408fe4d84615bbfb2c2b.camel@bootlin.com \
    --to=paul.kocialkowski@bootlin.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