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 changes for 5.15
Date: Mon, 23 Aug 2021 18:32:22 +0300 [thread overview]
Message-ID: <20210823153222.9638-1-djakov@kernel.org> (raw)
Hello Greg,
This is the pull request with the interconnect changes for the 5.15-rc1
merge window containing framework and driver changes. Details are available
in the signed tag.
Patches have been in linux-next for two weeks and without any reported
issues. Please pull into char-misc-next.
Thanks,
Georgi
The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3:
Linux 5.14-rc1 (2021-07-11 15:07:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-5.15-rc1
for you to fetch changes up to 8bf5d31c4f06d806ae24a3ba998a2f4eaccfa7c1:
interconnect: qcom: osm-l3: Use driver-specific naming (2021-08-09 20:10:19 +0300)
----------------------------------------------------------------
interconnect changes for 5.15
Here are changes for the 5.15-rc1 merge window consisting of interconnect
core and driver updates.
Framework change:
- Add sanity check to detect if node is already added to provider.
Driver changes:
- RPMh drivers probe function consolidation
- Add driver for SC8180x platforms
- Add support for SC8180x OSM L3
- Use driver-specific naming in OSM L3
Signed-off-by: Georgi Djakov <djakov@kernel.org>
----------------------------------------------------------------
Bjorn Andersson (4):
interconnect: Sanity check that node isn't already on list
dt-bindings: interconnect: Add SC8180x to OSM L3 DT binding
interconnect: qcom: osm-l3: Add sc8180x support
interconnect: qcom: osm-l3: Use driver-specific naming
Georgi Djakov (2):
dt-bindings: interconnect: Add Qualcomm SC8180x DT bindings
interconnect: qcom: Add SC8180x providers
Mike Tipton (1):
interconnect: qcom: icc-rpmh: Consolidate probe functions
Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml | 1 +
Documentation/devicetree/bindings/interconnect/qcom,rpmh.yaml | 11 +
drivers/interconnect/core.c | 3 +
drivers/interconnect/qcom/Kconfig | 9 +
drivers/interconnect/qcom/Makefile | 2 +
drivers/interconnect/qcom/icc-rpmh.c | 93 ++
drivers/interconnect/qcom/icc-rpmh.h | 2 +
drivers/interconnect/qcom/osm-l3.c | 60 +-
drivers/interconnect/qcom/sc7180.c | 96 +-
drivers/interconnect/qcom/sc7280.c | 96 +-
drivers/interconnect/qcom/sc8180x.c | 626 ++++++++
drivers/interconnect/qcom/sc8180x.h | 174 ++
drivers/interconnect/qcom/sdm845.c | 99 +-
drivers/interconnect/qcom/sdx55.c | 96 +-
drivers/interconnect/qcom/sm8150.c | 96 +-
drivers/interconnect/qcom/sm8250.c | 96 +-
drivers/interconnect/qcom/sm8350.c | 97 +-
include/dt-bindings/interconnect/qcom,sc8180x.h | 185 +++
18 files changed, 1159 insertions(+), 683 deletions(-)
create mode 100644 drivers/interconnect/qcom/sc8180x.c
create mode 100644 drivers/interconnect/qcom/sc8180x.h
create mode 100644 include/dt-bindings/interconnect/qcom,sc8180x.h
next reply other threads:[~2021-08-23 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 15:32 Georgi Djakov [this message]
2021-08-24 13:34 ` [GIT PULL] interconnect changes for 5.15 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=20210823153222.9638-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.