From: Katherine Perez <kaperez@linux.microsoft.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 0/4] arm64: dts: qcom: sm8150: display support for Microsoft Surface Duo
Date: Fri, 12 Nov 2021 18:39:51 -0800 [thread overview]
Message-ID: <20211113023955.105989-1-kaperez@linux.microsoft.com> (raw)
Hi Bjorn and Vinod,
I'm trying to enable the display subsystem on SM8150 but am having
trouble enabling the DISP_CC_MDSS_AHB_CLK. Trace shows "disp_cc_mdss_ahb_clk
status stuck at off". Do you have any pointers on enabling this clock?
msm_dsi_phy ae94400.dsi-phy: [drm:dsi_phy_driver_probe [msm]] *ERROR* dsi_phy_driver_probe: Unable to get ahb clk
disp_cc-sm8250 af00000.clock-controller: supply mmcx not found, using dummy regulator
platform ae96000.dsi: Fixing up cyclic dependency with ae00000.mdss:mdp@ae010000
------------[ cut here ]------------
disp_cc_mdss_ahb_clk status stuck at 'off'
WARNING: CPU: 6 PID: 76 at drivers/clk/qcom/clk-branch.c:91 clk_branch_wait+0x14c/0x164
CPU: 6 PID: 76 Comm: kworker/u16:2 Not tainted 5.15.0 #17
Hardware name: Microsoft Surface Duo (DT)
Workqueue: events_unbound deferred_probe_work_func
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : clk_branch_wait+0x14c/0x164
lr : clk_branch_wait+0x14c/0x164
sp : ffff80001078ba40
x29: ffff80001078ba40 x28: 0000000000000000 x27: ffff65e6008e2100
x26: ffffb8630ec8e278 x25: ffff65e60005e005 x24: ffffb8630ebc0f98
x23: ffffb8630e234dd8 x22: 0000000000000001 x21: ffffb8630d5b8b60
x20: 0000000000000000 x19: ffffb8630eb5e7b8 x18: 0000000000000030
x17: 2e726f74616c7567 x16: ffffb8630d5a3800 x15: ffffffffffffffff
x14: 0000000000000000 x13: 6f27207461206b63 x12: 7574732073757461
x11: 77705f313439386d x10: 0000000000000027 x9 : ffffb8630cf974bc
x8 : 0000000000000027 x7 : 0000000000000002 x6 : 0000000000000027
x5 : ffff65e6f93cc9a8 x4 : ffff80001078b890 x3 : 0000000000000001
x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff65e600851d80
Call trace:
clk_branch_wait+0x14c/0x164
clk_branch2_enable+0x3c/0x60
clk_core_enable+0x78/0x220
clk_enable+0x38/0x60
dsi_phy_enable_resource+0x98/0xac [msm]
dsi_phy_driver_probe+0x29c/0x4f8 [msm]
platform_probe+0x74/0xe4
really_probe.part.0+0xa4/0x328
__driver_probe_device+0xa0/0x150
driver_probe_device+0x4c/0x164
__device_attach_driver+0xc0/0x128
bus_for_each_drv+0x84/0xe0
__device_attach+0xe0/0x188
device_initial_probe+0x20/0x2c
bus_probe_device+0xa8/0xbc
deferred_probe_work_func+0x90/0xc8
process_one_work+0x1f4/0x43c
worker_thread+0x78/0x4f0
kthread+0x154/0x160
ret_from_fork+0x10/0x20
---[ end trace 734ed75908fc6b0e ]---
Katherine Perez (4):
arm64: dts: qcom: sm8150: add dispcc node
arm64: dts: qcom: sm8150: add display nodes
arm64: dts: qcom: sm8150: add DSI display nodes
arm64: dts: qcom: sm8150: display support for Microsoft Surface Duo
.../dts/qcom/sm8150-microsoft-surface-duo.dts | 26 ++
arch/arm64/boot/dts/qcom/sm8150.dtsi | 292 ++++++++++++++++++
2 files changed, 318 insertions(+)
--
2.31.1
next reply other threads:[~2021-11-13 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 2:39 Katherine Perez [this message]
2021-11-13 2:39 ` [RFC PATCH v2 1/4] arm64: dts: qcom: sm8150: add dispcc node Katherine Perez
2021-11-13 2:39 ` [RFC PATCH v2 2/4] arm64: dts: qcom: sm8150: add display nodes Katherine Perez
2021-11-13 2:39 ` [RFC PATCH v2 3/4] arm64: dts: qcom: sm8150: add DSI " Katherine Perez
2021-11-13 18:37 ` Bjorn Andersson
2021-11-13 2:39 ` [RFC PATCH v2 4/4] arm64: dts: qcom: sm8150: display support for Microsoft Surface Duo Katherine Perez
-- strict thread matches above, loose matches on Subject: below --
2021-11-17 1:35 [RFC PATCH v2 0/4] " Katherine Perez
2021-11-17 6:20 ` Bjorn Andersson
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=20211113023955.105989-1-kaperez@linux.microsoft.com \
--to=kaperez@linux.microsoft.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).