From: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
To: Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>
Subject: [PATCH 0/2] Add interconnect support for Qualcomm Shikra SoC
Date: Wed, 29 Apr 2026 14:03:47 +0000 [thread overview]
Message-ID: <20260429-shikra_icc-v1-0-e3439903edf1@oss.qualcomm.com> (raw)
Add interconnect dt-bindings and RPM-based interconnect driver support
for Qualcomm Shikra SoC.
Device tree changes aren't part of this series and will be posted
separately.
Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
---
Raviteja Laggyshetty (2):
dt-bindings: interconnect: document the RPM Network-On-Chip interconnect in Shikra SoC
interconnect: qcom: add Shikra interconnect provider driver
.../bindings/interconnect/qcom,shikra.yaml | 135 ++
drivers/interconnect/qcom/Kconfig | 9 +
drivers/interconnect/qcom/Makefile | 2 +
drivers/interconnect/qcom/shikra.c | 1837 ++++++++++++++++++++
include/dt-bindings/interconnect/qcom,shikra.h | 121 ++
5 files changed, 2104 insertions(+)
---
base-commit: 9974969c14031a097d6b45bcb7a06bb4aa525c40
change-id: 20260320-shikra_icc-b1fcef45122d
Best regards,
--
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
next reply other threads:[~2026-04-29 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 14:03 Raviteja Laggyshetty [this message]
2026-04-29 14:03 ` [PATCH 1/2] dt-bindings: interconnect: document the RPM Network-On-Chip interconnect in Shikra SoC Raviteja Laggyshetty
2026-05-03 16:17 ` Krzysztof Kozlowski
2026-05-04 7:17 ` Raviteja Laggyshetty
2026-04-29 14:03 ` [PATCH 2/2] interconnect: qcom: add Shikra interconnect provider driver Raviteja Laggyshetty
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=20260429-shikra_icc-v1-0-e3439903edf1@oss.qualcomm.com \
--to=raviteja.laggyshetty@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=odelu.kukatla@oss.qualcomm.com \
--cc=robh@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