From: Mark yao <mark.yao@rock-chips.com>
To: ayaka <ayaka@soulik.info>
Cc: randy.li@rock-chips.com, airlied@linux.ie, heiko@sntech.de,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: rockchip: drm: analogix_dp-rockchip would stock the kernel
Date: Mon, 17 Oct 2016 08:57:09 +0800 [thread overview]
Message-ID: <580421E5.9030609@rock-chips.com> (raw)
In-Reply-To: <1a7ebbe4-a9d8-610d-7cd5-41f5fe8355a5@soulik.info>
On 2016年10月16日 02:03, ayaka wrote:
> Hello:
> I meet a problem with eDP in rk3288 with the linux next 20161006,
> it is just like the early stage of 4.4
> kernel. I have added a eDP panel entry in the firefly reload board,
> once the kernel loaded analogix_dp-rockchip.ko, after printed the
> following two lines, the kernel stop working.
> rockchip-drm display-subsystem: bound ff940000.vop (ops
> vop_component_ops [rockchipdrm])
> rockchip-drm display-subsystem: bound ff930000.vop (ops
> vop_component_ops [rockchipdrm])
Hi ayaka
This log seems no problem.
How about tested it with build-in? we had test it with build-in.
Maybe this patch can help you, you can have a try.
https://patchwork.kernel.org/patch/9374135
Thanks.
> In the early June of the 4.4 kernel, I meet the same problem with
> rk3288 evb board with different error message, I have to disable the
> display system that time.
> In the today test, I meet the same problem with rk3399 evb board in
> 4.4.
> I have no idea what caused that, and it is a little hard to debug as
> kernel still would never kill that task.
> Randy Li
>
>
>
--
Mark Yao
next prev parent reply other threads:[~2016-10-17 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 18:03 rockchip: drm: analogix_dp-rockchip would stock the kernel ayaka
2016-10-17 0:57 ` Mark yao [this message]
2016-10-17 1:12 ` Randy Li
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=580421E5.9030609@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=ayaka@soulik.info \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=randy.li@rock-chips.com \
/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