From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] clk: renesas: Updates for v6.5 (take two)
Date: Fri, 9 Jun 2023 12:06:58 +0200 [thread overview]
Message-ID: <cover.1686304777.git.geert+renesas@glider.be> (raw)
Hi Mike, Stephen,
The following changes since commit d1c20885d3b01e6a62e920af4b227abd294d22f3:
clk: renesas: rzg2l: Fix CPG_SIPLL5_CLK1 register write (2023-05-23 09:06:50 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-clk-for-v6.5-tag2
for you to fetch changes up to 7df8eea64a417f1db6777cddc1d7eda3634b7175:
clk: renesas: rzg2l: Convert to readl_poll_timeout_atomic() (2023-06-05 15:41:43 +0200)
----------------------------------------------------------------
clk: renesas: Updates for v6.5 (take two)
- Convert the Renesas clock drivers to readl_poll_timeout_atomic().
Note that the conversion to readl_poll_timeout_atomic() depends
on iopoll improvements, which are thus included through an immutable
branch in multiple pull requests:
"[GIT PULL 2/3] Renesas driver updates for v6.5 (take two)" (for soc),
"[GIT PULL] clk: renesas: Updates for v6.5 (take two)" (for clk).
Thanks for pulling!
----------------------------------------------------------------
Geert Uytterhoeven (6):
iopoll: Call cpu_relax() in busy loops
iopoll: Do not use timekeeping in read_poll_timeout_atomic()
Merge tag 'iopoll-busy-loop-timeout-tag' into renesas-clk-for-v6.5
clk: renesas: cpg-mssr: Convert to readl_poll_timeout_atomic()
clk: renesas: mstp: Convert to readl_poll_timeout_atomic()
clk: renesas: rzg2l: Convert to readl_poll_timeout_atomic()
drivers/clk/renesas/clk-mstp.c | 18 +++++++-----------
drivers/clk/renesas/renesas-cpg-mssr.c | 31 +++++++++++--------------------
drivers/clk/renesas/rzg2l-cpg.c | 16 +++++-----------
include/linux/iopoll.h | 24 +++++++++++++++++++-----
4 files changed, 42 insertions(+), 47 deletions(-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2023-06-09 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:06 Geert Uytterhoeven [this message]
2023-06-12 18:02 ` [GIT PULL] clk: renesas: Updates for v6.5 (take two) 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=cover.1686304777.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox