All of lore.kernel.org
 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 6.18
Date: Sun, 21 Sep 2025 10:56:03 +0300	[thread overview]
Message-ID: <20250921075603.14452-1-djakov@kernel.org> (raw)

Hello Greg,

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

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

Thanks,
Georgi


The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

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

for you to fetch changes up to bcdf7a064c3c73cd97870a3ef5e4dd6214b28b79:

  Merge branch 'icc-glymur' into icc-next (2025-09-12 13:54:17 +0300)

----------------------------------------------------------------
interconnect changes for 6.18

This pull request contains the interconnect changes for the 6.18-rc1
merge window. It contains new driver and a minor core cleanup.

Core change:
- Use device_match_of_node() instead of open coding it

Driver changes:
- Add new driver for the Qualcomm Glymur SoC
- Enable OSM L3 support for the QCS615 SoC

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

----------------------------------------------------------------
Georgi Djakov (1):
      Merge branch 'icc-glymur' into icc-next

Raviteja Laggyshetty (4):
      dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in Glymur SoC
      interconnect: qcom: icc-rpmh: increase MAX_PORTS to support four QoS ports
      interconnect: qcom: add glymur interconnect provider driver
      dt-bindings: interconnect: Add OSM L3 compatible for QCS615 SoC

Zhang Enpei (1):
      interconnect: core: Use device_match_of_node()

 .../devicetree/bindings/interconnect/qcom,glymur-rpmh.yaml     |  172 +
 .../devicetree/bindings/interconnect/qcom,osm-l3.yaml          |    5 +
 drivers/interconnect/core.c                                    |    2 +-
 drivers/interconnect/qcom/Kconfig                              |    9 +
 drivers/interconnect/qcom/Makefile                             |    2 +
 drivers/interconnect/qcom/glymur.c                             | 2543 ++++++++
 drivers/interconnect/qcom/icc-rpmh.h                           |    2 +-
 include/dt-bindings/interconnect/qcom,glymur-rpmh.h            |  205 +
 8 files changed, 2938 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,glymur-rpmh.yaml
 create mode 100644 drivers/interconnect/qcom/glymur.c
 create mode 100644 include/dt-bindings/interconnect/qcom,glymur-rpmh.h

             reply	other threads:[~2025-09-21  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21  7:56 Georgi Djakov [this message]
2025-09-23 12:12 ` [GIT PULL] interconnect changes for 6.18 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=20250921075603.14452-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.