From: Shawn Guo <shawn.guo@linaro.org>
To: Georgi Djakov <djakov@kernel.org>
Cc: AngeloGioacchino Del Regno <kholk11@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: [PATCH 0/3] Add missing A2NoC QoS clocks for SDM660 interconnect driver
Date: Mon, 23 Aug 2021 17:56:00 +0800 [thread overview]
Message-ID: <20210823095603.5538-1-shawn.guo@linaro.org> (raw)
The series updates SDM660 interconnect bindings, driver and device tree
to add A2NoC clocks required for QoS registers programming per downstream
kernel[1]. Otherwise, qcom_icc_noc_set_qos_priority() call on mas_ufs or
mas_usb_hs node will simply result in a hardware hang on SDM660 SoC.
[1] https://source.codeaurora.org/quic/la/kernel/msm-4.4/tree/arch/arm/boot/dts/qcom/sdm660-bus.dtsi?h=LA.UM.8.2.r1-04800-sdm660.0#n43
Shawn Guo (3):
dt-bindings: interconnect: sdm660: Add missing a2noc qos clocks
interconnect: qcom: sdm660: Add missing a2noc qos clocks
arm64: dts: qcom: sdm630: Add missing a2noc qos clocks
.../bindings/interconnect/qcom,sdm660.yaml | 41 ++++++++++++++++++-
arch/arm64/boot/dts/qcom/sdm630.dtsi | 17 ++++++--
drivers/interconnect/qcom/sdm660.c | 14 +++++++
3 files changed, 67 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-23 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 9:56 Shawn Guo [this message]
2021-08-23 9:56 ` [PATCH 1/3] dt-bindings: interconnect: sdm660: Add missing a2noc qos clocks Shawn Guo
2021-08-23 13:30 ` Rob Herring
2021-08-23 9:56 ` [PATCH 2/3] interconnect: qcom: " Shawn Guo
2021-08-23 15:57 ` Bjorn Andersson
2021-08-23 9:56 ` [PATCH 3/3] arm64: dts: qcom: sdm630: " Shawn Guo
2021-08-23 16:51 ` Dmitry Baryshkov
2021-08-24 1:17 ` Shawn Guo
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=20210823095603.5538-1-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=kholk11@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@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.