mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 7.2
Date: Mon,  8 Jun 2026 14:25:37 +0300	[thread overview]
Message-ID: <20260608112537.2701425-1-djakov@kernel.org> (raw)

Hello Greg,

This is the pull request with interconnect changes for the v7.2-rc1
merge window. As always, the short summary is in the signed tag.

All patches have been in linux-next for two full weeks. There are
currently no reported issues. Please pull into char-misc-next when
possible.

Thanks,
Georgi


The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-7.2-rc1

for you to fetch changes up to 94fe92d2f662b990da2ef9788bbe3bdcfe086731:

  Merge branch 'icc-misc' into icc-next (2026-05-22 10:41:01 +0300)

----------------------------------------------------------------
This pull request contains the following interconnect updates for
the 7.2-rc1 merge window:

- New driver for Shikra SoC
- New driver for Nord SoC
- New driver for Hawi SoC including CPU/LLCC bwmon support
- Add missing SDCC nodes for Eliza SoC
- Misc cleanups and fixes.

Signed-off-by: Georgi Djakov <djakov@kernel.org>

----------------------------------------------------------------
Abel Vesa (2):
      dt-bindings: interconnect: qcom,eliza-rpmh: Add SDCC1 slave
      interconnect: qcom: eliza: Add SDCC1 slave node

Georgi Djakov (5):
      Merge branch 'icc-shikra' into icc-next
      Merge branch 'icc-nord' into icc-next
      Merge branch 'icc-eliza' into icc-next
      Merge branch 'icc-hawi' into icc-next
      Merge branch 'icc-misc' into icc-next

Krzysztof Kozlowski (7):
      interconnect: Do not create empty devres on missing interconnects
      interconnect: Move MODULE_DEVICE_TABLE next to the table itself
      dt-bindings: interconnect: qcom,sdm660: Disallow clocks when appropriate
      dt-bindings: interconnect: qcom,sm6115: Drop incorrect children if:then: block
      dt-bindings: interconnect: qcom,sm6115: Restrict children and clocks
      interconnect: qcom: Fix indentation
      interconnect: qcom: Restrict drivers per ARM/ARM64

Mukesh Ojha (2):
      dt-bindings: interconnect: qcom-bwmon: Add Hawi cpu-bwmon compatible
      dt-bindings: interconnect: qcom-bwmon: Add Hawi llcc-bwmon compatible

Odelu Kukatla (2):
      dt-bindings: interconnect: Document RPMh Network-On-Chip for Qualcomm Nord SoC
      interconnect: qcom: Add interconnect provider driver for Nord SoC

Raviteja Laggyshetty (2):
      dt-bindings: interconnect: document the RPM Network-On-Chip interconnect in Shikra SoC
      interconnect: qcom: add Shikra interconnect provider driver

Vivek Aknurwar (2):
      dt-bindings: interconnect: qcom: document the RPMh NoC for Hawi SoC
      interconnect: qcom: add Hawi interconnect provider driver

 .../devicetree/bindings/interconnect/qcom,hawi-rpmh.yaml       |  131 +
 .../devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml   |    2 +
 .../devicetree/bindings/interconnect/qcom,nord-rpmh.yaml       |  131 +
 .../devicetree/bindings/interconnect/qcom,sdm660.yaml          |   13 +
 .../devicetree/bindings/interconnect/qcom,shikra.yaml          |  134 +
 .../devicetree/bindings/interconnect/qcom,sm6115.yaml          |   33 +-
 drivers/interconnect/core.c                                    |    2 +-
 drivers/interconnect/qcom/Kconfig                              |   95 +-
 drivers/interconnect/qcom/Makefile                             |    6 +
 drivers/interconnect/qcom/eliza.c                              |   15 +-
 drivers/interconnect/qcom/hawi.c                               | 2028 ++++++
 drivers/interconnect/qcom/msm8953.c                            |    2 +-
 drivers/interconnect/qcom/nord.c                               | 2682 ++++++++
 drivers/interconnect/qcom/shikra.c                             | 1837 +++++
 include/dt-bindings/interconnect/qcom,eliza-rpmh.h             |    1 +
 include/dt-bindings/interconnect/qcom,hawi-rpmh.h              |  165 +
 include/dt-bindings/interconnect/qcom,nord-rpmh.h              |  217 +
 include/dt-bindings/interconnect/qcom,shikra.h                 |  121 +
 18 files changed, 7577 insertions(+), 38 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,hawi-rpmh.yaml
 create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,nord-rpmh.yaml
 create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,shikra.yaml
 create mode 100644 drivers/interconnect/qcom/hawi.c
 create mode 100644 drivers/interconnect/qcom/nord.c
 create mode 100644 drivers/interconnect/qcom/shikra.c
 create mode 100644 include/dt-bindings/interconnect/qcom,hawi-rpmh.h
 create mode 100644 include/dt-bindings/interconnect/qcom,nord-rpmh.h
 create mode 100644 include/dt-bindings/interconnect/qcom,shikra.h

             reply	other threads:[~2026-06-08 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 11:25 Georgi Djakov [this message]
2026-06-08 19:35 ` 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=20260608112537.2701425-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

all inboxes | Powered by JetHome®