linux-kernel - Re: omap4: support for manually updated display

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <42986939-9670-df31-8f30-b0bfbf559d90@ti.com>
Date:   Tue, 11 Sep 2018 09:48:27 +0300
From:   Tomi Valkeinen <tomi.valkeinen@...com>
To:     Tony Lindgren <tony@...mide.com>,
        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>, <sre@...nel.org>,
        <nekit1000@...il.com>, <mpartap@....net>, <merlijn@...zup.org>
Subject: Re: omap4: support for manually updated display

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