From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
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>, <sre@kernel.org>,
<nekit1000@gmail.com>, <mpartap@gmx.net>, <merlijn@wizzup.org>
Subject: Re: omap4: support for manually updated display
Date: Tue, 11 Sep 2018 09:48:27 +0300 [thread overview]
Message-ID: <42986939-9670-df31-8f30-b0bfbf559d90@ti.com> (raw)
In-Reply-To: <20180910174453.GV5662@atomide.com>
On 10/09/18 20:44, Tony Lindgren wrote:
>> I want to make it clear that I don't want to claim any privilege in getting
>> patches merged first. I am however worried that, without an easy way to test
>> DSI support, and without enough time to focus on it, I would break whatever
>> would be merged now in future reworks. I would thus like to find out how to
>> collaborate on this task, hopefully to move towards usage of drm_bridge and
>> drm_panel for DSI-based pipelines.
>
> Real users with mainline kernel with a real product should
> always have priority over any ongoing clean-up.
If this were cleanup, it would of course be a low priority work. But
this is changing omapdrm to support DRM panels and bridges, which is
needed to support many real products in the mainline kernel.
Droid/N9 are no exceptions here, I have been keeping support for
multiple boards out of mainline for this same reason: I don't want to
add omapdrm specific code that will need to be rewritten and would
complicate this big change. Well, Droid/N9 are different in the sense
that they are much more complex cases than the boards I've been keeping out.
In any case, Laurent was ok with merging the patches, so let's merge
them after rebasing.
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-09-11 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:04 Pavel Machek
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 17:44 ` Tony Lindgren
2018-09-11 6:48 ` Tomi Valkeinen [this message]
2018-10-18 22:15 ` Pavel Machek
2018-10-19 16:44 ` Tony Lindgren
2018-10-19 22:58 ` Sebastian Reichel
2018-10-20 0:38 ` Tony Lindgren
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-31 13:10 ` Laurent Pinchart
2018-09-10 21:28 ` Sebastian Reichel
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=42986939-9670-df31-8f30-b0bfbf559d90@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®