From: Georgi Djakov <djakov@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
djakov@kernel.org
Subject: [GIT PULL] interconnect fixes for 5.18-rc
Date: Fri, 22 Apr 2022 10:32:21 +0300 [thread overview]
Message-ID: <20220422073221.30745-1-djakov@kernel.org> (raw)
Hello Greg,
This pull request contains interconnect driver fixes for an issue that
has been reported. Please pull into char-misc-linus when possible. The
patches have been in linux-next for a week.
Thanks,
Georgi
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/djakov/icc.git tags/icc-5.18-rc4
for you to fetch changes up to 2fb251c265608636fc961b7d38e1a03937e57371:
interconnect: qcom: sdx55: Drop IP0 interconnects (2022-04-14 09:47:16 +0300)
----------------------------------------------------------------
interconnect fixes for v5.18
This contains a fix for a reported issue on sc7180 platforms, where
one of the resources has been incorrectly modelled as both clock and
interconnect, which is causing a crash when both frameworks try to
manage it. Fix the same issue also on another platform that appears
to be affected by the same.
- interconnect: qcom: sc7180: Drop IP0 interconnects
- interconnect: qcom: sdx55: Drop IP0 interconnects
Signed-off-by: Georgi Djakov <djakov@kernel.org>
----------------------------------------------------------------
Stephen Boyd (2):
interconnect: qcom: sc7180: Drop IP0 interconnects
interconnect: qcom: sdx55: Drop IP0 interconnects
drivers/interconnect/qcom/sc7180.c | 21 --------
drivers/interconnect/qcom/sdx55.c | 21 --------
2 files changed, 42 deletions(-)
next reply other threads:[~2022-04-22 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 7:32 Georgi Djakov [this message]
2022-04-22 13:50 ` [GIT PULL] interconnect fixes for 5.18-rc Greg KH
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=20220422073221.30745-1-djakov@kernel.org \
--to=djakov@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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