public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Archit Taneja <architt@codeaurora.org>,
	Eric Anholt <eric@anholt.net>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.
Date: Tue, 6 Jun 2017 16:24:44 +0200	[thread overview]
Message-ID: <2cbcbf54-debf-10a1-390d-128171d81f91@linux.intel.com> (raw)
In-Reply-To: <2ab4e84f-9834-1dce-d16a-14f9cc4083e9@codeaurora.org>

Op 05-06-17 om 12:08 schreef Archit Taneja:
>
>
> On 06/03/2017 01:55 AM, Eric Anholt wrote:
>> Many DRM drivers have common code to make a stub connector
>> implementation that wraps a drm_panel.  By wrapping the panel in a DRM
>> bridge, all of the connector code (including calls during encoder
>> enable/disable) goes away.
>>
>> v2: Fix build with CONFIG_DRM=m, drop "dev" argument that should just
>>     be the panel's dev, move kerneldoc up a level and document
>>     _remove().
>> v3: Fix another breakage with CONFIG_DRM=m, fix breakage with
>>     CONFIG_OF=n, move protos under CONFIG_DRM_PANEL_BRIDGE, wrap a
>>     line.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
>> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> (v1)
>> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com> (v2)
>> Acked-by: Archit Taneja <architt@codeaurora.org> (v2)
>> ---
>>
>> New version of the first patch with build fixes.  I've re-pushed to
>> get another round of kbuild test, but if it comes back clean, I'd like
>> to merge this one, the vc4 patches (unchanged), and atmel-hlcdc (acked
>> by the maintainer).  I'd be dropping my STM patch (replaced by their
>> DSI series), and mediatek (I'd like an ack from the maintainer first).
>
> Thanks, I've locally picked up this patch and the following patches from
> the v2 series:
>
> [PATCH v2 2/7] drm/vc4: Switch DSI to the panel-bridge layer, and support bridges.
> [PATCH v2 3/7] drm/vc4: Switch DPI to using the panel-bridge helper.
> [PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func.
> [PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge. 

This patch breaks support for building drm as module, because it imports some of the drm_kms_helper stuff.

  reply	other threads:[~2017-06-06 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 20:25 [PATCH v3] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Eric Anholt
2017-06-05 10:08 ` Archit Taneja
2017-06-06 14:24   ` Maarten Lankhorst [this message]
2017-06-06 14:31     ` [PATCH v3] drm/bridge: Build the panel wrapper in drm_kms_helper Maarten Lankhorst
2017-06-06 17:52       ` Eric Anholt
2017-06-07  8:19         ` Archit Taneja
2017-06-07  6:55       ` Lofstedt, Marta
2017-06-06 14:42 ` [PATCH v3] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Thierry Reding

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=2cbcbf54-debf-10a1-390d-128171d81f91@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=architt@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@gmail.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