mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
	a.hajda@samsung.com, Laurent.pinchart@ideasonboard.com,
	airlied@linux.ie, daniel.vetter@intel.com,
	jani.nikula@linux.intel.com, seanpaul@chromium.org,
	yannick.fertre@st.com, philippe.cornu@st.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Simplify panel bridge cleanup
Date: Tue, 10 Oct 2017 09:06:53 +0530	[thread overview]
Message-ID: <d1b932cc-429c-91af-40e2-613f40c78b11@codeaurora.org> (raw)
In-Reply-To: <1506936755-23625-1-git-send-email-benjamin.gaignard@linaro.org>



On 10/02/2017 03:02 PM, Benjamin Gaignard wrote:
> The goal of this series is to simplify driver code when they need to clean up
> a previously allocated panel bridge.
> Few drivers have "is_panel_bridge" flag to be able to distinguish a
> drm_panel_bridge from "simple" drm_bridge.
> To remove this flag I propose to
> - let drm_panel_bridge_remove() check if the bridge provided in parameter is
>    really a drm_panel_bridge.
> - add drm_of_panel_bridge_remove() to remove a bridge given DT port and
>    endpoint
> Finally that allow to remove drm_bridge structure and "is_panel_bridge" flag
> from stm driver internal structure.
> 
> version 2:
> - does the same for vc4 and dw-mipi-dsi
For the series:

Reviewed-by: Archit Taneja <architt@codeaurora.org>

Feel free to queue to drm-misc-next.

Thanks,
Archit

> 
> Benjamin Gaignard (5):
>    drm/bridge: make drm_panel_bridge_remove more robust
>    drm/drm_of: add drm_of_panel_bridge_remove function
>    drm/stm: ltdc: remove bridge from driver internal structure
>    drm/vc4: remove bridge from driver internal structure
>    drm/bridge/synopsys: dsi :remove is_panel_bridge
> 
>   drivers/gpu/drm/bridge/panel.c                | 10 +++++++-
>   drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c |  5 +---
>   drivers/gpu/drm/drm_of.c                      | 33 +++++++++++++++++++++++++++
>   drivers/gpu/drm/stm/ltdc.c                    | 16 ++++---------
>   drivers/gpu/drm/stm/ltdc.h                    |  2 --
>   drivers/gpu/drm/vc4/vc4_dpi.c                 | 17 +++++---------
>   include/drm/drm_of.h                          |  8 +++++++
>   7 files changed, 62 insertions(+), 29 deletions(-)
> 

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2017-10-10  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02  9:32 Benjamin Gaignard
2017-10-02  9:32 ` [PATCH v2 1/5] drm/bridge: make drm_panel_bridge_remove more robust Benjamin Gaignard
2017-10-03  8:06 ` [PATCH v2 0/5] Simplify panel bridge cleanup Daniel Vetter
2017-10-10  3:36 ` Archit Taneja [this message]
2017-10-10 10:03   ` Benjamin Gaignard

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=d1b932cc-429c-91af-40e2-613f40c78b11@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=benjamin.gaignard@linaro.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.cornu@st.com \
    --cc=seanpaul@chromium.org \
    --cc=yannick.fertre@st.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

Powered by JetHome