From: JeffyChen <jeffy.chen@rock-chips.com>
To: Robin Murphy <robin.murphy@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Douglas Anderson <dianders@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v1] arch_topology: Adjust initial CPU capacities with current freq
Date: Mon, 13 Jan 2020 11:59:51 +0800 [thread overview]
Message-ID: <5E1BEB37.2010904@rock-chips.com> (raw)
In-Reply-To: <5fa797f8-3ba5-7e18-4eed-2d39904b2f72@arm.com>
Hi Robin,
On 01/11/2020 11:12 PM, Robin Murphy wrote:
>>
>
> Actually, last time I looked both the BSP U-Boot and mainline do contain
> equivalent code to initialise both PLLs to (IIRC) 600MHz and apparently
> adjust a couple of other things set by the maskrom. The trap is that
> mainline does it in the SPL - thus the unfortunately common combination
> of using the upstream main stage with the miniloader ends up missing out
> that step entirely. In comparison, I'm now using the full upstream
> TPL/SPL flow on my RK3399 board (NanoPC-T4) and even a full generic
> distro kernel is acceptably quick:
>
> [ 2.315378] Trying to unpack rootfs image as initramfs...
> [ 2.781747] Freeing initrd memory: 7316K
> ...
> [ 4.239990] Freeing unused kernel memory: 1984K
> [ 4.247829] Run /init as init process
Oops, sorry for the noise, i've checked in the wrong u-boot code base...
Will ask miniloader team to check that, thanks :)
>
> Robin.
next prev parent reply other threads:[~2020-01-13 4:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 7:52 [PATCH v1] arch_topology: Adjust initial CPU capacities with current freq Jeffy Chen
2020-01-10 11:37 ` Sudeep Holla
2020-01-10 11:54 ` Robin Murphy
2020-01-10 12:01 ` Dietmar Eggemann
2020-01-10 12:28 ` Robin Murphy
2020-01-11 2:51 ` JeffyChen
2020-01-11 15:12 ` Robin Murphy
2020-01-13 3:59 ` JeffyChen [this message]
2020-01-10 14:03 ` kbuild test robot
2020-01-10 14:03 ` kbuild test robot
2020-01-10 14:45 ` kbuild test robot
2020-01-10 14:45 ` kbuild test robot
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=5E1BEB37.2010904@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
/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.