From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
Sebastian Reichel <sre@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Pavel Machek <pavel@ucw.cz>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <nekit1000@gmail.com>,
<mpartap@gmx.net>, <merlijn@wizzup.org>
Subject: Re: omap4: support for manually updated display
Date: Mon, 22 Oct 2018 11:14:07 +0300 [thread overview]
Message-ID: <6ebd84ad-3428-c2f5-da8b-e5b1c54ea5e2@ti.com> (raw)
In-Reply-To: <20181020003812.GE43338@atomide.com>
On 20/10/18 03:38, Tony Lindgren wrote:
> * Sebastian Reichel <sre@kernel.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
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
Sebastian Reichel <sre@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: mpartap@gmx.net, merlijn@wizzup.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
nekit1000@gmail.com, Pavel Machek <pavel@ucw.cz>,
linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: omap4: support for manually updated display
Date: Mon, 22 Oct 2018 11:14:07 +0300 [thread overview]
Message-ID: <6ebd84ad-3428-c2f5-da8b-e5b1c54ea5e2@ti.com> (raw)
In-Reply-To: <20181020003812.GE43338@atomide.com>
On 20/10/18 03:38, Tony Lindgren wrote:
> * Sebastian Reichel <sre@kernel.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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: omap4: support for manually updated display
Date: Mon, 22 Oct 2018 11:14:07 +0300 [thread overview]
Message-ID: <6ebd84ad-3428-c2f5-da8b-e5b1c54ea5e2@ti.com> (raw)
In-Reply-To: <20181020003812.GE43338@atomide.com>
On 20/10/18 03:38, Tony Lindgren wrote:
> * Sebastian Reichel <sre@kernel.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
next prev parent reply other threads:[~2018-10-22 8:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:04 omap4: support for manually updated display Pavel Machek
2018-08-30 9:04 ` Pavel Machek
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 17:44 ` Tony Lindgren
2018-09-10 17:44 ` Tony Lindgren
2018-09-11 6:48 ` Tomi Valkeinen
2018-09-11 6:48 ` Tomi Valkeinen
2018-09-11 6:48 ` Tomi Valkeinen
2018-10-18 22:15 ` Pavel Machek
2018-10-18 22:15 ` Pavel Machek
2018-10-19 16:44 ` Tony Lindgren
2018-10-19 16:44 ` Tony Lindgren
2018-10-19 22:58 ` Sebastian Reichel
2018-10-19 22:58 ` Sebastian Reichel
2018-10-19 22:58 ` Sebastian Reichel
2018-10-20 0:38 ` Tony Lindgren
2018-10-20 0:38 ` Tony Lindgren
2018-10-22 8:14 ` Tomi Valkeinen [this message]
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-31 13:10 ` Laurent Pinchart
2018-10-31 13:10 ` Laurent Pinchart
2018-10-31 13:10 ` Laurent Pinchart
2018-09-10 21:28 ` Sebastian Reichel
2018-09-10 21:28 ` Sebastian Reichel
2018-09-11 12:54 ` Pavel Machek
2018-09-11 12:54 ` Pavel Machek
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=6ebd84ad-3428-c2f5-da8b-e5b1c54ea5e2@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.