From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: architt@codeaurora.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,
Benjamin Gaignard <benjamin.gaignard@linaro.org>
Subject: [PATCH 0/3] Simplify panel bridge cleanup
Date: Fri, 29 Sep 2017 14:59:16 +0200 [thread overview]
Message-ID: <1506689959-7858-1-git-send-email-benjamin.gaignard@linaro.org> (raw)
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.
Benjamin Gaignard (3):
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
drivers/gpu/drm/bridge/panel.c | 10 +++++++++-
drivers/gpu/drm/drm_of.c | 33 +++++++++++++++++++++++++++++++++
drivers/gpu/drm/stm/ltdc.c | 16 +++++-----------
drivers/gpu/drm/stm/ltdc.h | 2 --
include/drm/drm_of.h | 8 ++++++++
5 files changed, 55 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2017-09-29 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 12:59 Benjamin Gaignard [this message]
2017-09-29 12:59 ` [PATCH 1/3] drm/bridge: make drm_panel_bridge_remove more robust Benjamin Gaignard
2017-09-29 12:59 ` [PATCH 2/3] drm/drm_of: add drm_of_panel_bridge_remove function Benjamin Gaignard
2017-09-29 12:59 ` [PATCH 3/3] drm/stm: ltdc: remove bridge from driver internal structure Benjamin Gaignard
2017-09-29 15:03 ` [PATCH 0/3] Simplify panel bridge cleanup Philippe CORNU
2017-10-02 7:51 ` Daniel Vetter
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=1506689959-7858-1-git-send-email-benjamin.gaignard@linaro.org \
--to=benjamin.gaignard@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.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
all inboxes | Powered by JetHome®