public inbox for linux-kernel@vger.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.14
Date: Thu, 16 Jan 2025 14:42:30 +0200	[thread overview]
Message-ID: <20250116124230.635223-1-djakov@kernel.org> (raw)

Hello Greg,

This is the pull request with interconnect changes for the v6.14-rc1 merge
window. It contains a new driver and tiny DT binding updates. As always,
the summary is in the signed tag.

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

Thanks,
Georgi


The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 4cc004716977beab6242bca385326c84db127256:

  Merge branch 'icc-sm8750' into icc-next (2025-01-14 00:13:23 +0200)

----------------------------------------------------------------
interconnect changes for 6.14

This pull request contains the interconnect changes for the 6.14-rc1 merge
window. It contains one new driver and DT documentation updates for L3
and bandwidth monitors.

Driver changes:
- New driver for the SM8750 platform
- Add DT compatibles for QCS615 BWMON and SM8650 OSM

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

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

Krzysztof Kozlowski (1):
      interconnect: sm8750: Add missing const to static qcom_icc_desc

Lijuan Gao (1):
      dt-bindings: interconnect: qcom-bwmon: Document QCS615 bwmon compatibles

Neil Armstrong (1):
      dt-bindings: interconnect: OSM L3: Document sm8650 OSM L3 compatible

Raviteja Laggyshetty (2):
      dt-bindings: interconnect: add interconnect bindings for SM8750
      interconnect: qcom: Add interconnect provider driver for SM8750

Shivnandan Kumar (1):
      dt-bindings: interconnect: qcom,msm8998-bwmon: Add SM8750 CPU BWMONs

 .../devicetree/bindings/interconnect/qcom,msm8998-bwmon.yaml   |    3 +
 .../devicetree/bindings/interconnect/qcom,osm-l3.yaml          |    1 +
 .../devicetree/bindings/interconnect/qcom,sm8750-rpmh.yaml     |  136 +
 drivers/interconnect/qcom/Kconfig                              |    9 +
 drivers/interconnect/qcom/Makefile                             |    2 +
 drivers/interconnect/qcom/sm8750.c                             | 1705 ++++++++
 include/dt-bindings/interconnect/qcom,sm8750-rpmh.h            |  143 +
 7 files changed, 1999 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,sm8750-rpmh.yaml
 create mode 100644 drivers/interconnect/qcom/sm8750.c
 create mode 100644 include/dt-bindings/interconnect/qcom,sm8750-rpmh.h

             reply	other threads:[~2025-01-16 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 12:42 Georgi Djakov [this message]
2025-01-16 13:03 ` [GIT PULL] interconnect changes for 6.14 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=20250116124230.635223-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