From: Stephen Boyd <sboyd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk fixes for v6.1-rc7
Date: Wed, 30 Nov 2022 14:57:20 -0800 [thread overview]
Message-ID: <20221130225720.1615026-1-sboyd@kernel.org> (raw)
The following changes since commit ffa20aa581cf5377fc397b0d0ff9d67ea823629b:
clk: qcom: Update the force mem core bit for GPU clocks (2022-10-27 17:23:29 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus
for you to fetch changes up to f6abcc21d94393801937aed808b8f055ffec8579:
clk: qcom: gcc-sc8280xp: add cxo as parent for three ufs ref clks (2022-11-22 18:27:07 -0800)
----------------------------------------------------------------
A set of clk driver fixes that resolve issues for various SoCs. Most of
these are incorrect clk data, like bad parent descriptions. When the clk
tree is improperly described things don't work, like USB and UFS
controllers, because clk frequencies are wonky. Here are the extra
details:
- Fix the parent of UFS reference clks on Qualcomm SC8280XP so that UFS
works properly.
- Fix the clk ID for USB on AT91 RM9200 so the USB driver continues to
probe.
- Stop using of_device_get_match_data() on the wrong device for a
Samsung Exynos driver so it gets the proper clk data.
- Fix ExynosAutov9 binding.
- Fix the parent of the div4 clk on Exynos7885.
- Stop calling runtime PM APIs from the Qualcomm GDSC driver directly
as it leads to a lockdep splat and is just plain wrong because it
violates runtime PM semantics by calling runtime PM APIs when the
device has been runtime PM disabled.
----------------------------------------------------------------
David Virag (1):
clk: samsung: exynos7885: Correct "div4" clock parents
Inbaraj E (1):
dt-bindings: clock: exynosautov9: fix reference to CMU_FSYS1
Marek Szyprowski (1):
clk: samsung: Revert "clk: samsung: exynos-clkout: Use of_device_get_match_data()"
Michael Grzeschik (1):
ARM: at91: rm9200: fix usb device clock id
Shazad Hussain (1):
clk: qcom: gcc-sc8280xp: add cxo as parent for three ufs ref clks
Stephen Boyd (3):
clk: qcom: gdsc: Remove direct runtime PM calls
Merge tag 'samsung-clk-6.2' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into clk-fixes
Merge tag 'clk-microchip-fixes-6.1' of https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux into clk-fixes
.../bindings/clock/samsung,exynosautov9-clock.yaml | 2 +-
arch/arm/boot/dts/at91rm9200.dtsi | 2 +-
drivers/clk/at91/at91rm9200.c | 2 +-
drivers/clk/qcom/gcc-sc8280xp.c | 6 +++
drivers/clk/qcom/gdsc.c | 61 +++-------------------
drivers/clk/qcom/gdsc.h | 2 -
drivers/clk/samsung/clk-exynos-clkout.c | 6 ++-
drivers/clk/samsung/clk-exynos7885.c | 4 +-
8 files changed, 21 insertions(+), 64 deletions(-)
--
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/
https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git
next reply other threads:[~2022-11-30 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 22:57 Stephen Boyd [this message]
2022-12-01 19:37 ` [GIT PULL] clk fixes for v6.1-rc7 pr-tracker-bot
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=20221130225720.1615026-1-sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=torvalds@linux-foundation.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