From: Philippe Cornu <philippe.cornu@st.com>
To: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Gustavo Padovan <gustavo@padovan.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Yannick Fertre <yannick.fertre@st.com>,
Philippe Cornu <philippe.cornu@st.com>,
"Vincent Abriou" <vincent.abriou@st.com>
Subject: [PATCH] drm: clarify adjusted_mode for a bridge connected to a crtc
Date: Mon, 26 Feb 2018 13:16:04 +0100 [thread overview]
Message-ID: <20180226121605.12050-1-philippe.cornu@st.com> (raw)
This patch clarifies the adjusted_mode documentation
for a bridge directly connected to a crtc.
Signed-off-by: Philippe Cornu <philippe.cornu@st.com>
---
This patch is linked to the discussion https://lkml.org/lkml/2018/1/25/367
include/drm/drm_bridge.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h
index 3270fec46979..b5f3c070467c 100644
--- a/include/drm/drm_bridge.h
+++ b/include/drm/drm_bridge.h
@@ -177,7 +177,8 @@ struct drm_bridge_funcs {
* pipeline has been called already. If the bridge is the first element
* then this would be &drm_encoder_helper_funcs.mode_set. The display
* pipe (i.e. clocks and timing signals) is off when this function is
- * called.
+ * called. If the bridge is connected to the crtc, the adjusted_mode
+ * parameter is the one defined in &drm_crtc_state.adjusted_mode.
*/
void (*mode_set)(struct drm_bridge *bridge,
struct drm_display_mode *mode,
--
2.15.1
next reply other threads:[~2018-02-26 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 12:16 Philippe Cornu [this message]
2018-03-27 15:51 ` Daniel Vetter
2018-03-29 7:35 ` Philippe CORNU
2018-03-29 7:39 ` Daniel Vetter
2018-04-05 15:15 ` Philippe CORNU
2018-04-06 14:53 ` Laurent Pinchart
2018-04-06 15:28 ` Philippe CORNU
2018-04-09 7:56 ` 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=20180226121605.12050-1-philippe.cornu@st.com \
--to=philippe.cornu@st.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=vincent.abriou@st.com \
--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®