From: Bjorn Andersson <andersson@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>, linux-clk@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Adam Skladowski <a39.skl@gmail.com>,
Johan Hovold <johan+linaro@kernel.org>
Subject: [GIT PULL] Qualcomm clock fixes for v6.9
Date: Sat, 20 Apr 2024 11:28:00 -0500 [thread overview]
Message-ID: <20240420162801.1132878-1-andersson@kernel.org> (raw)
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-clk-fixes-for-6.9
for you to fetch changes up to 0d4ce2458cd7d1d66a5ee2f3c036592fb663d5bc:
clk: qcom: smd-rpm: Restore msm8976 num_clk (2024-04-02 22:49:07 -0500)
----------------------------------------------------------------
Qualcomm clock fixes for v6.9
The introduction of support for the external VDD_GFX supply in SA8295P
ADP unearthed a lockdep problem in the GDSC code w.r.t regulator
supplies. Make the regulator optional, to avoid creating a dummy
regulator, on those boards that doesn't use this. While not solving the
root cause of the problem, it reduces the impact of the lockdep warning
- and it avoids wasting resources.
Refactoring of the RPM clock driver accidentally removed num_clks from
msm8976. Reintroduce this to get the clocks back.
----------------------------------------------------------------
Adam Skladowski (1):
clk: qcom: smd-rpm: Restore msm8976 num_clk
Johan Hovold (1):
clk: qcom: gdsc: treat optional supplies as optional
drivers/clk/qcom/clk-smd-rpm.c | 1 +
drivers/clk/qcom/gdsc.c | 11 ++++++++---
2 files changed, 9 insertions(+), 3 deletions(-)
next reply other threads:[~2024-04-20 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 16:28 Bjorn Andersson [this message]
2024-04-22 18:59 ` [GIT PULL] Qualcomm clock fixes for v6.9 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=20240420162801.1132878-1-andersson@kernel.org \
--to=andersson@kernel.org \
--cc=a39.skl@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).