Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Adam Skladowski <a39.skl@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Val Packett <val@packett.cool>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/6] clk: qcom: dispcc-sm6115: Add missing MDSS resets
Date: Mon, 16 Feb 2026 20:25:21 -0300	[thread overview]
Message-ID: <20260216233600.13098-5-val@packett.cool> (raw)
In-Reply-To: <20260216233600.13098-2-val@packett.cool>

The MDSS resets were left undescribed, fix that.

Fixes: 9b518788631c ("clk: qcom: Add display clock controller driver for SM6115")
Signed-off-by: Val Packett <val@packett.cool>
---
 drivers/clk/qcom/dispcc-sm6115.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/clk/qcom/dispcc-sm6115.c b/drivers/clk/qcom/dispcc-sm6115.c
index 8ae25d51db94..75bd57213079 100644
--- a/drivers/clk/qcom/dispcc-sm6115.c
+++ b/drivers/clk/qcom/dispcc-sm6115.c
@@ -22,6 +22,7 @@
 #include "clk-regmap-divider.h"
 #include "common.h"
 #include "gdsc.h"
+#include "reset.h"
 
 enum {
 	DT_BI_TCXO,
@@ -511,6 +512,10 @@ static struct clk_branch disp_cc_sleep_clk = {
 	},
 };
 
+static const struct qcom_reset_map disp_cc_sm6115_resets[] = {
+	[DISP_CC_MDSS_CORE_BCR] = { 0x2000 },
+};
+
 static struct gdsc mdss_gdsc = {
 	.gdscr = 0x3000,
 	.pd = {
@@ -561,6 +566,8 @@ static const struct qcom_cc_desc disp_cc_sm6115_desc = {
 	.config = &disp_cc_sm6115_regmap_config,
 	.clks = disp_cc_sm6115_clocks,
 	.num_clks = ARRAY_SIZE(disp_cc_sm6115_clocks),
+	.resets = disp_cc_sm6115_resets,
+	.num_resets = ARRAY_SIZE(disp_cc_sm6115_resets),
 	.gdscs = disp_cc_sm6115_gdscs,
 	.num_gdscs = ARRAY_SIZE(disp_cc_sm6115_gdscs),
 };
-- 
2.52.0


  parent reply	other threads:[~2026-02-16 23:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 23:25 [PATCH 0/6] SM6115/SM6125 MDSS core reset Val Packett
2026-02-16 23:25 ` [PATCH 1/6] dt-bindings: clock: qcom,sm6115-dispcc: Define MDSS resets Val Packett
2026-02-17  8:11   ` Krzysztof Kozlowski
2026-02-16 23:25 ` [PATCH 2/6] dt-bindings: clock: qcom,dispcc-sm6125: " Val Packett
2026-02-16 23:25 ` Val Packett [this message]
2026-02-17  7:36   ` [PATCH 3/6] clk: qcom: dispcc-sm6115: Add missing " Dmitry Baryshkov
2026-02-17  9:22   ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 4/6] clk: qcom: dispcc-sm6125: " Val Packett
2026-02-17  7:37   ` Dmitry Baryshkov
2026-02-17  8:12   ` Krzysztof Kozlowski
2026-02-17  9:22   ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 5/6] arm64: dts: qcom: sm6115: Add missing MDSS core reset Val Packett
2026-02-17  7:37   ` Dmitry Baryshkov
2026-02-17  9:22   ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 6/6] arm64: dts: qcom: sm6125: " Val Packett
2026-02-17  7:37   ` Dmitry Baryshkov
2026-02-17  9:23   ` Konrad Dybcio
2026-02-18 13:31   ` Yedaya Katsman

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=20260216233600.13098-5-val@packett.cool \
    --to=val@packett.cool \
    --cc=a39.skl@gmail.com \
    --cc=andersson@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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