From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] drm/rockchip: Refactor the component match logic.
Date: Wed, 15 Mar 2017 18:00:04 +0100 [thread overview]
Message-ID: <19101003.9xjQ92OS5C@phil> (raw)
In-Reply-To: <1489573247-9628-1-git-send-email-jeffy.chen@rock-chips.com>
Am Mittwoch, 15. M?rz 2017, 18:20:47 CET schrieb Jeffy Chen:
> Currently we are adding all components from the dts, if one of their
> drivers been disabled, we would not be able to bring up others.
>
> Refactor component match logic, follow exynos drm.
>
> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
This reliably produces null pointer dereference errors in
__platform_driver_register called from rockchip_drm_init
on at least rk3036 and rk3288 (probably more) when applied on top of
Linus' tree from today. Log attached and Rockchip drm compiled as module.
I'm currently dug into other areas, so hadn't have time to investigate further
yet.
Heiko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: firefly-drm.log
Type: text/x-log
Size: 36974 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170315/86183a40/attachment-0001.bin>
next prev parent reply other threads:[~2017-03-15 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 10:20 [PATCH v3] drm/rockchip: Refactor the component match logic Jeffy Chen
2017-03-15 13:52 ` Sean Paul
2017-03-15 17:00 ` Heiko Stuebner [this message]
2017-03-15 17:23 ` Heiko Stuebner
2017-03-16 2:07 ` jeffy
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=19101003.9xjQ92OS5C@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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