From: Sibi Sankar <sibis@codeaurora.org>
To: robh+dt@kernel.org, georgi.djakov@linaro.org
Cc: bjorn.andersson@linaro.org, agross@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, mark.rutland@arm.com,
evgreen@chromium.org, daidavid1@codeaurora.org,
saravanak@google.com, Sibi Sankar <sibis@codeaurora.org>
Subject: [PATCH 0/2] Add OSM L3 Interconnect Provider
Date: Wed, 7 Aug 2019 16:54:30 +0530 [thread overview]
Message-ID: <20190807112432.26521-1-sibis@codeaurora.org> (raw)
This patch series aims to add Operating State Manager (OSM) L3
interconnect provider support on SDM845 SoCs to handle bandwidth
requests from CPU/GPU to scale L3 caches.
Sibi Sankar (2):
dt-bindings: interconnect: Add OSM L3 DT bindings
interconnect: qcom: Add OSM L3 interconnect provider support
.../bindings/interconnect/qcom,osm-l3.yaml | 55 ++++
drivers/interconnect/qcom/Kconfig | 7 +
drivers/interconnect/qcom/Makefile | 2 +
drivers/interconnect/qcom/osm-l3.c | 292 ++++++++++++++++++
.../dt-bindings/interconnect/qcom,osm-l3.h | 13 +
5 files changed, 369 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
create mode 100644 drivers/interconnect/qcom/osm-l3.c
create mode 100644 include/dt-bindings/interconnect/qcom,osm-l3.h
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2019-08-07 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 11:24 Sibi Sankar [this message]
2019-08-07 11:24 ` [PATCH 1/2] dt-bindings: interconnect: Add OSM L3 DT bindings Sibi Sankar
2019-08-14 11:34 ` Sibi Sankar
2019-08-07 11:24 ` [PATCH 2/2] interconnect: qcom: Add OSM L3 interconnect provider support Sibi Sankar
2019-08-07 21:21 ` Saravana Kannan
2019-08-08 17:36 ` Sibi Sankar
2019-08-14 0:43 ` Saravana Kannan
2019-08-14 11:30 ` Sibi Sankar
2019-08-14 15:21 ` Jordan Crouse
2019-08-13 20:32 ` Evan Green
2019-08-14 11:27 ` Sibi Sankar
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=20190807112432.26521-1-sibis@codeaurora.org \
--to=sibis@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
/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.