From: Thierry Reding <thierry.reding@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [GIT PULL] clk: tegra: Changes for v5.19-rc1
Date: Fri, 6 May 2022 16:24:46 +0200 [thread overview]
Message-ID: <20220506142446.3916142-1-thierry.reding@gmail.com> (raw)
Hi Mike, Stephen,
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/for-5.19-clk
for you to fetch changes up to 6f6baf690c3b8c41083d7443ab6a5645b96ff91b:
clk: tegra: Update kerneldoc to match prototypes (2022-05-06 10:56:00 +0200)
Thanks,
Thierry
----------------------------------------------------------------
clk: tegra: Changes for v5.19-rc1
This contains a boot time optimization for Tegra chips with BPMP and a
switch from .round_rate() to .determine_rate() to take into account any
maximum rate that might have been set.
Other than that this contains a fix for a DFLL regression on Tegra210
and kerneldoc fixups to avoid build warnings.
----------------------------------------------------------------
Diogo Ivo (1):
clk: tegra: Add missing reset deassertion
Rajkumar Kasirajan (1):
clk: tegra: Replace .round_rate() with .determine_rate()
Thierry Reding (1):
clk: tegra: Update kerneldoc to match prototypes
Timo Alho (1):
clk: tegra: Register clocks from root to leaf
drivers/clk/tegra/clk-bpmp.c | 87 +++++++++++++++++++++++++++++++++-----------
drivers/clk/tegra/clk-dfll.c | 20 ++++++++--
2 files changed, 82 insertions(+), 25 deletions(-)
next reply other threads:[~2022-05-06 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 14:24 Thierry Reding [this message]
2022-05-17 6:55 ` [GIT PULL] clk: tegra: Changes for v5.19-rc1 Stephen Boyd
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=20220506142446.3916142-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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.