From: Sean Anderson <seanga2@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Lukasz Majewski <lukma@denx.de>
Subject: [PULL] clock changes for v2022.01-rc3
Date: Wed, 15 Dec 2021 14:41:19 -0500 [thread overview]
Message-ID: <54091fff-b3d6-321c-5da0-bffa19f12829@gmail.com> (raw)
Hi Tom,
The following changes since commit ade37460a944aed36ae6ee634c4d4a9a22690461:
Prepare v2022.01-rc3 (2021-11-29 11:16:03 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-clk.git tags/clk-2022.01-rc3
for you to fetch changes up to 560e1e005093b1d62c53391d68960237294e7f89:
clk: define LOG_CATEGORY for generic and ccf clocks (2021-12-15 12:16:16 -0500)
CI:
https://source.denx.de/u-boot/custodians/u-boot-clk/-/pipelines/10265
----------------------------------------------------------------
Clock patches for v2022.01-rc3
This adds better logging support for many CCF drivers, and clarifies some
documentation regarding clk_get_rate.
----------------------------------------------------------------
Giulio Benetti (1):
clk: fix clk_get_rate() documentation
Patrick Delaunay (2):
clk: cosmetic: reorder include files
clk: define LOG_CATEGORY for generic and ccf clocks
drivers/clk/clk-composite.c | 9 ++++++---
drivers/clk/clk-divider.c | 6 +++++-
drivers/clk/clk-fixed-factor.c | 13 +++++++++----
drivers/clk/clk-gate.c | 15 ++++++++++-----
drivers/clk/clk-mux.c | 13 +++++++++----
drivers/clk/clk-uclass.c | 2 +-
drivers/clk/clk.c | 20 +++++++++++---------
drivers/clk/clk_fixed_factor.c | 3 +++
drivers/clk/clk_fixed_rate.c | 3 +++
include/clk.h | 3 ++-
10 files changed, 59 insertions(+), 28 deletions(-)
next reply other threads:[~2021-12-15 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 19:41 Sean Anderson [this message]
2021-12-15 23:23 ` [PULL] clock changes for v2022.01-rc3 Tom Rini
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=54091fff-b3d6-321c-5da0-bffa19f12829@gmail.com \
--to=seanga2@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=lukma@denx.de \
--cc=patrick.delaunay@foss.st.com \
--cc=trini@konsulko.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;
as well as URLs for NNTP newsgroup(s).