From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Sandy Huang <hjc-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Subject: Re: Regression: HDMI stopped working on rk3399-sapphire in 4.17-rc1
Date: Fri, 20 Apr 2018 00:31:08 +0200 [thread overview]
Message-ID: <5183868.jTL5zlpghY@phil> (raw)
In-Reply-To: <CAAMcf8AEDE2p16WQHjwS85M=1aAfgW8cY+0E6GWKA5WSFGmejw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Vicente,
Am Dienstag, 17. April 2018, 19:23:29 CEST schrieb Vicente Bergas:
> On Mon, Apr 16, 2018 at 11:49 PM, Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On Mon, Apr 16, 2018 at 11:41 PM, Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> wrote:
> >> Hi Vicente,
> >>
> >> Am Montag, 16. April 2018, 23:18:27 CEST schrieb Vicente Bergas:
> >>> Hello,
> >>>
> >>> first of all, I am not sure if this goes to
> >>> linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> >>> or
> >>> dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> >>> Please, tell me if I have chosen the wrong list.
> >>
> >> Best would be having both in the Cc list :-)
> >>
> >>
> >>> In 4.16-rc7 the HDMI video works with minor issues, but it is perfectly
> >>> usable. In 4.17-rc1 the HDMI port is not detected at all.
> >>>
> >>> Here are the messages from dmesg that I think are relevant:
> >>>
> >>> Linux version 4.16.0-rc7+ (vj@alarm) (gcc version 7.3.0 (GCC)) #15 SMP
> >>> Mon Mar 26 19:03:44 CEST 2018
> >>> iommu: Adding device ff8f0000.vop to group 0
> >>> iommu: Adding device ff900000.vop to group 1
> >>> rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)
> >>> rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)
> >>> rockchip-drm display-subsystem: failed to bind ff940000.hdmi (ops
> >>> dw_hdmi_rockchip_ops): -EPROBE_DEFER
> >>> rockchip-drm display-subsystem: master bind failed: -EPROBE_DEFER
> >>> rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)
> >>> rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)
> >>> dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with
> >>> HDCP (DWC HDMI 2.0 TX PHY)
> >>> rockchip-drm display-subsystem: bound ff940000.hdmi (ops dw_hdmi_rockchip_ops)
> >>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> >>> [drm] No driver support for vblank timestamp query.
> >>> Console: switching to colour frame buffer device 240x67
> >>> rockchip-drm display-subsystem: fb0: frame buffer device
> >>> [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
> >>>
> >>> Linux version 4.17.0-rc1+ (vj@alarm) (gcc version 7.3.0 (GCC)) #1 SMP
> >>> Mon Apr 16 19:42:50 CEST 2018
> >>> rk_iommu ff8f3f00.iommu: Failed to get clk 'iface': -ENOENT
> >>> rk_iommu: probe of ff8f3f00.iommu failed with error -ENOENT
> >>> rk_iommu ff903f00.iommu: Failed to get clk 'iface': -ENOENT
> >>> rk_iommu: probe of ff903f00.iommu failed with error -ENOENT
> >>> rockchip-drm display-subsystem: Linked as a consumer to ff8f0000.vop
> >>> rockchip-drm display-subsystem: Linked as a consumer to ff900000.vop
> >>> rockchip-drm display-subsystem: Linked as a consumer to ff940000.hdmi
> >>> rockchip-drm display-subsystem: master bind failed: -12
> >>> rockchip-vop: probe of ff900000.vop failed with error -12
> >>>
> >>>
> >>> While fixing this issue, I can help debugging and testing.
> >>
> >> I do belive
> >> https://patchwork.codeaurora.org/patch/495129/
> >> should do the trick. Needs a respin to make it a bit more
> >> beatiful, but should restore your display output again nevertheless.
> >>
> >>
> >> Heiko
> >
> > Hi Heiko,
> > thanks for such a quick answer!
> > Tomorrow I'll give it a try.
> >
> > Regards,
> > Vicente.
>
> Hi Heiko,
> just tested your v2 patch:
> http://lists.infradead.org/pipermail/linux-rockchip/2018-April/020349.html
> and indeed the HDMI port was detected and was able to show me the console :)
>
> But, there have been several kernel stack traces, a lot of
> unresponsiveness and unable to start a framebuffer-based graphical
> mode.
> The first relevant error seems to be line 349 from dmesg:
> [CRTC:30:crtc-0] vblank wait timed out
> https://pastebin.com/YegEpAep
>
> Please, can somebody help?
does the problem go away when you apply
https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v4.18-armsoc/dts64&id=df3bcde704fb51645615635667944fc550c493e2
Thanks
Heiko
next prev parent reply other threads:[~2018-04-19 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 21:18 Regression: HDMI stopped working on rk3399-sapphire in 4.17-rc1 Vicente Bergas
[not found] ` <CAAMcf8DRkLJYCYtemri3L-SrPax4VJ4jvHG369MYcDAwWeOm8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-16 21:41 ` Heiko Stuebner
2018-04-16 21:49 ` Vicente Bergas
[not found] ` <CAAMcf8DKcxHuMn78dHe-4Qn7XHvnQBEx6jaMm3aukrmMsBFVWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-17 17:23 ` Vicente Bergas
[not found] ` <CAAMcf8AEDE2p16WQHjwS85M=1aAfgW8cY+0E6GWKA5WSFGmejw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-19 22:31 ` Heiko Stuebner [this message]
2018-04-19 22:53 ` Vicente Bergas
[not found] ` <CAAMcf8CuYmh1PSdB+7MXK8on6T-TomeuHRZjCi3gv+Dy+Cjb0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-30 18:08 ` Vicente Bergas
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=5183868.jTL5zlpghY@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=hjc-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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