From: Brian Masney <masneyb@onstation.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: robdclark@gmail.com, sean@poorly.run,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, airlied@linux.ie,
daniel@ffwll.ch, linux-kernel@vger.kernel.org,
linus.walleij@linaro.org
Subject: Re: [PATCH RFC 4/6] ARM: dts: msm8974: add display support
Date: Wed, 8 May 2019 22:16:16 -0400 [thread overview]
Message-ID: <20190509021616.GA26228@basecamp> (raw)
In-Reply-To: <20190507063902.GA2085@tuxbook-pro>
On Mon, May 06, 2019 at 11:39:02PM -0700, Bjorn Andersson wrote:
> On Sun 05 May 06:04 PDT 2019, Brian Masney wrote:
> > diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi b/arch/arm/boot/dts/qcom-msm8974.dtsi
> [..]
> > + clocks = <&mmcc MDSS_MDP_CLK>,
> > + <&mmcc MDSS_AHB_CLK>,
> > + <&mmcc MDSS_AXI_CLK>,
> > + <&mmcc MDSS_BYTE0_CLK>,
> > + <&mmcc MDSS_PCLK0_CLK>,
> > + <&mmcc MDSS_ESC0_CLK>,
> > + <&mmcc MMSS_MISC_AHB_CLK>;
> > + clock-names = "mdp_core",
> > + "iface",
> > + "bus",
> > + "byte",
> > + "pixel",
> > + "core",
> > + "core_mmss";
>
> Unless I enable MMSS_MMSSNOC_AXI_CLK and MMSS_S0_AXI_CLK I get some
> underrun error from DSI. You don't see anything like this?
>
> (These clocks are controlled by msm_bus downstream and should be driven
> by interconnect upstream)
>
>
> Apart from this, I think this looks nice. Happy to see the progress.
No, I'm not seeing an underrun errors from the DSI. I think the clocks
are fine since I'm able to get this working with 4.17 using these same
clocks. I just sent out v2 and the cover letter has some details, along
with the full dmesg.
Brian
next prev parent reply other threads:[~2019-05-09 2:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 13:04 [PATCH RFC 0/6] ARM: qcom: initial Nexus 5 display support Brian Masney
2019-05-05 13:04 ` [PATCH RFC 1/6] drm/msm: fix null pointer dereference in msm_atomic_prepare_fb() Brian Masney
2019-05-05 13:04 ` [PATCH RFC 2/6] drm/msm: add dirty framebuffer helper Brian Masney
2019-05-05 13:04 ` [PATCH RFC 3/6] ARM: qcom_defconfig: add display-related options Brian Masney
2019-05-06 7:04 ` Linus Walleij
2019-05-05 13:04 ` [PATCH RFC 4/6] ARM: dts: msm8974: add display support Brian Masney
2019-05-06 7:07 ` Linus Walleij
2019-05-07 6:39 ` Bjorn Andersson
2019-05-09 2:16 ` Brian Masney [this message]
2019-05-09 2:25 ` Rob Clark
[not found] ` <CAF6AEGsM382jB=h7oM3frhZ5fAp+qYUdgiiKSKo1RtR8+ffjrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-09 3:00 ` Bjorn Andersson
2019-05-09 7:12 ` Brian Masney
2019-05-09 14:38 ` Rob Clark
2019-05-09 14:59 ` Bjorn Andersson
2019-05-05 13:04 ` [PATCH RFC 5/6] ARM: dts: qcom: msm8974-hammerhead: add support for backlight Brian Masney
2019-05-06 7:08 ` Linus Walleij
2019-05-05 13:04 ` [PATCH RFC 6/6] ARM: dts: qcom: msm8974-hammerhead: add support for display Brian Masney
2019-05-06 7:09 ` Linus Walleij
2019-05-06 6:42 ` [PATCH RFC 0/6] ARM: qcom: initial Nexus 5 display support Linus Walleij
[not found] ` <CACRpkda=JTfKC4z=1Gmt1BE5adwd8XGZ4ERTgapWX_BN9TFESw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-06 8:46 ` Brian Masney
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=20190509021616.GA26228@basecamp \
--to=masneyb@onstation.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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).