All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon South <simon@simonsouth.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/1] rk3328: clk: Configure CPU clock during initialization
Date: Thu, 10 Oct 2019 15:28:35 -0400	[thread overview]
Message-ID: <cover.1570734167.git.simon@simonsouth.net> (raw)

This patch changes the RK3328 CRU driver so it explicitly configures
the CPU clock during initialization, through a call to
rk3328_configure_cpu().

Previously rk3328_configure_cpu() was implemented but not called from
anywhere, which I'm assuming was unintentional.

This change matches the RK3399's CRU driver
(drivers/clk/rockchip/clk_rk3399.c) by

- Invoking the function at the start of rkclk_init() and
- Setting the CPU clock to the lowest defined frequency, 600 MHz.

It yields no real functional change (the CPU clock is already set to
600 MHz at power-on) but it does make it straightforward to set a
higher clock rate at compile time for systems like the ROCK64 that run
reliably at higher frequencies.

Tested on my ROCK64.

Simon South (1):
  clk: rockchip: rk3328: Configure CPU clock

 arch/arm/include/asm/arch-rockchip/cru_rk3328.h | 3 +++
 drivers/clk/rockchip/clk_rk3328.c               | 2 ++
 2 files changed, 5 insertions(+)

-- 
2.23.0

             reply	other threads:[~2019-10-10 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 19:28 Simon South [this message]
2019-10-10 19:28 ` [U-Boot] [PATCH 1/1] clk: rockchip: rk3328: Configure CPU clock Simon South
2019-10-14  9:06   ` Kever Yang
2019-10-14  9:54     ` [U-Boot] [PATCH 1/1] clk: rockchip: rk3328: Configure CPU clock【请注意,邮件由u-boot-bounces@lists.denx.de代发】 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=cover.1570734167.git.simon@simonsouth.net \
    --to=simon@simonsouth.net \
    --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.