From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v2 2/2] rockchip: gru: Allow setting up clocks in U-Boot proper
Date: Tue, 3 Nov 2020 08:11:42 -0700 [thread overview]
Message-ID: <CAPnjgZ1w+3tyByVAJ6DSAc2HWeSbDkBoaD+bon7k4rGpmY6MAA@mail.gmail.com> (raw)
In-Reply-To: <20201027211511.14544-2-alpernebiyasak@gmail.com>
On Tue, 27 Oct 2020 at 15:15, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>
> Commit fe974716326c ("rockchip: rk3288: Allow setting up clocks in
> U-Boot proper") fixes some clock issues when chainloading U-Boot on
> rk3288 chromebooks. Part of that change is still available in veyron's
> board_early_init_r() function. Since chain-loading U-Boot proper from
> vendor firmware is possible on gru boards as well, do the same thing for
> them too.
>
> On rk3399, this needs to detect whether SPL was run via handoff, so
> enable that and bloblist kconfigs it needs for chromebook_bob.
>
> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
> ---
>
> Changes in v2:
> - Enable kconfigs needed for using SPL handoff
>
> v1: https://patchwork.ozlabs.org/project/uboot/patch/20201022203740.24528-2-alpernebiyasak at gmail.com/
>
> board/google/gru/gru.c | 23 +++++++++++++++++++++++
> configs/chromebook_bob_defconfig | 5 +++++
> 2 files changed, 28 insertions(+)
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2020-11-03 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 21:15 [PATCH v2 1/2] rockchip: rk3399: Init clocks in U-Boot proper if SPL was not run Alper Nebi Yasak
2020-10-27 21:15 ` [PATCH v2 2/2] rockchip: gru: Allow setting up clocks in U-Boot proper Alper Nebi Yasak
2020-11-03 15:11 ` Simon Glass [this message]
2020-11-13 10:13 ` Kever Yang
2020-11-03 15:11 ` [PATCH v2 1/2] rockchip: rk3399: Init clocks in U-Boot proper if SPL was not run Simon Glass
2020-11-13 10:12 ` Kever Yang
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=CAPnjgZ1w+3tyByVAJ6DSAc2HWeSbDkBoaD+bon7k4rGpmY6MAA@mail.gmail.com \
--to=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.