From: Georgi Djakov <djakov@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
georgi.djakov@linaro.org, Georgi Djakov <djakov@kernel.org>
Subject: [GIT PULL] interconnect changes for 5.13
Date: Thu, 15 Apr 2021 11:09:48 +0300 [thread overview]
Message-ID: <20210415080948.17167-1-djakov@kernel.org> (raw)
Hello Greg,
This is the pull request with the interconnect changes for the 5.13-rc1
merge window. These include two new drivers.
Patches have been in linux-next without any reported issues. Please pull
into char-misc-next.
Thanks,
Georgi
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-5.13-rc1
for you to fetch changes up to c1de07884f2bafa11ad3780cf08b234c88c2cc9d:
Merge branch 'icc-sm8350' into icc-next (2021-04-02 13:12:37 +0300)
----------------------------------------------------------------
interconnect changes for 5.13
These are the interconnect changes for the 5.13-rc1 merge window
with the highlights being drivers for two new platforms.
Driver changes:
- New driver for SM8350 platforms.
- New driver for SDM660 platforms.
Signed-off-by: Georgi Djakov <djakov@kernel.org>
----------------------------------------------------------------
AngeloGioacchino Del Regno (2):
dt-bindings: interconnect: Add bindings for Qualcomm SDM660 NoC
interconnect: qcom: Add SDM660 interconnect provider driver
Benjamin Li (1):
interconnect: qcom: icc-rpm: record slave RPM id in error log
Georgi Djakov (5):
interconnect: qcom: sdm660: Fix kerneldoc warning
interconnect: qcom: sm8350: Use the correct ids
interconnect: qcom: sm8350: Add missing link between nodes
Merge branch 'icc-sdm660' into icc-next
Merge branch 'icc-sm8350' into icc-next
Vinod Koul (3):
dt-bindings: interconnect: Add Qualcomm SM8350 DT bindings
interconnect: qcom: Add SM8350 interconnect provider driver
MAINTAINERS: icc: add interconnect tree
Documentation/devicetree/bindings/interconnect/qcom,rpmh.yaml | 10 +
Documentation/devicetree/bindings/interconnect/qcom,sdm660.yaml | 147 ++
MAINTAINERS | 1 +
drivers/interconnect/qcom/Kconfig | 18 +
drivers/interconnect/qcom/Makefile | 4 +
drivers/interconnect/qcom/icc-rpm.c | 4 +-
drivers/interconnect/qcom/sdm660.c | 923 ++++++++
drivers/interconnect/qcom/sm8350.c | 633 +++++
drivers/interconnect/qcom/sm8350.h | 168 ++
include/dt-bindings/interconnect/qcom,sdm660.h | 116 +
include/dt-bindings/interconnect/qcom,sm8350.h | 172 ++
11 files changed, 2194 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sdm660.yaml
create mode 100644 drivers/interconnect/qcom/sdm660.c
create mode 100644 drivers/interconnect/qcom/sm8350.c
create mode 100644 drivers/interconnect/qcom/sm8350.h
create mode 100644 include/dt-bindings/interconnect/qcom,sdm660.h
create mode 100644 include/dt-bindings/interconnect/qcom,sm8350.h
next reply other threads:[~2021-04-15 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 8:09 Georgi Djakov [this message]
2021-04-15 9:07 ` [GIT PULL] interconnect changes for 5.13 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=20210415080948.17167-1-djakov@kernel.org \
--to=djakov@kernel.org \
--cc=georgi.djakov@linaro.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;
as well as URLs for NNTP newsgroup(s).