[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19101003.9xjQ92OS5C@phil>
Date: Wed, 15 Mar 2017 18:00:04 +0100
From: Heiko Stuebner <heiko@...ech.de>
To: Jeffy Chen <jeffy.chen@...k-chips.com>
Cc: Mark Yao <mark.yao@...k-chips.com>,
Andrzej Hajda <a.hajda@...sung.com>,
Guenter Roeck <groeck@...omium.org>,
Brian Norris <briannorris@...omium.org>,
Tomasz Figa <tfiga@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Sean Paul <seanpaul@...omium.org>,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-rockchip@...ts.infradead.org,
David Airlie <airlied@...ux.ie>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3] drm/rockchip: Refactor the component match logic.
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@...k-chips.com>
> Reviewed-by: Andrzej Hajda <a.hajda@...sung.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
View attachment "firefly-drm.log" of type "text/x-log" (36974 bytes)
Powered by blists - more mailing lists