linux-kernel - Re: [PATCHv1 00/14] omapdrm: DSI command mode panel support

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: <b66ec006-e998-b8c6-8ef1-5bf19208c100@ti.com>
Date:   Thu, 12 Oct 2017 11:45:19 +0300
From:   Tomi Valkeinen <tomi.valkeinen@...com>
To:     Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        <dri-devel@...ts.freedesktop.org>
CC:     <linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCHv1 00/14] omapdrm: DSI command mode panel support

Hi Sebastian,

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

On 29/09/17 16:26, Sebastian Reichel wrote:
> Hi Tomi & Laurent,
> 
> ping?

I've been having quick glances at this every now and then, but I'm not
sure what to do with the series.

We have one work item that more or less overrides everything but
critical fixes: moving to common DRM encoder/panel drivers. Anything
that makes that work more difficult should be postponed.

Especially patch 6 in this series most likely falls into that category,
and might require a very different implementation with common DRM
drivers. Also everything in panel-dsi-cm needs to be ported to a common
DRM panel driver when can use them.

So my gut feeling is that it's best to keep this out for now, and rework
it after Laurent gets the common DRM drivers working with omapdrm.

 Tomi