[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ebd84ad-3428-c2f5-da8b-e5b1c54ea5e2@ti.com>
Date: Mon, 22 Oct 2018 11:14:07 +0300
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: Tony Lindgren <tony@...mide.com>,
Sebastian Reichel <sre@...nel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
CC: Pavel Machek <pavel@....cz>, <dri-devel@...ts.freedesktop.org>,
<linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
<linux-omap@...r.kernel.org>, <nekit1000@...il.com>,
<mpartap@....net>, <merlijn@...zup.org>
Subject: Re: omap4: support for manually updated display
On 20/10/18 03:38, Tony Lindgren wrote:
> * Sebastian Reichel <sre@...nel.org> [181019 15:58]:
>> I uploaded my current status here. It's not based on the newest
>> -next, but contains the interesting patches from Laurent. Also
>> the last few patches are not yet cleaned up, sorry for the mess.
>
> Way to go, thanks :) Here's a quick fix for issues with loading
> and unloading modules, seems like this should be fixed somewhere
> else though?
I didn't get that far on drm-next with pandaboard. When loading modules, dsi_probe crashes. It is missing runtime_get(). But after adding runtime_get call, it fails and I see:
[ 44.671081] omap_hwmod: dss_dsi2: _wait_target_ready failed: -16
[ 44.677459] omapdss_dsi 58005000.encoder: use pm_runtime_put_sync_suspend() in driver?
Why is dsi2 busy (and what does it even mean)...
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
Powered by blists - more mailing lists