From: "Sripada, Radhakrishna" <radhakrishna.sripada@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [RFC 2/2] drm/i915: Allow force_bpc property to limit pipe_bpp
Date: Wed, 18 Oct 2017 15:29:49 -0700 [thread overview]
Message-ID: <20171018222949.11140-2-radhakrishna.sripada@intel.com> (raw)
In-Reply-To: <20171018222949.11140-1-radhakrishna.sripada@intel.com>
Use the newly added force_bpc connector property to limit pipe bpp.
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>
Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
---
drivers/gpu/drm/i915/intel_display.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index e691c07afd9a..ed8e3f06e605 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -10587,6 +10587,29 @@ connected_sink_compute_bpp(struct intel_connector *connector,
}
}
+static void
+connected_sink_force_bpp(struct intel_digital_connector_state *intel_conn_state,
+ struct intel_crtc_state *pipe_config)
+{
+ enum connector_force_bpc force_bpc = intel_conn_state->force_bpc;
+
+ switch (force_bpc) {
+ case INTEL_FORCE_BPC_AUTO:
+ break;
+ case INTEL_FORCE_BPC_8:
+ pipe_config->pipe_bpp = 8*3;
+ break;
+ case INTEL_FORCE_BPC_10:
+ pipe_config->pipe_bpp = 10*3;
+ break;
+ case INTEL_FORCE_BPC_12:
+ pipe_config->pipe_bpp = 12*3;
+ break;
+ default:
+ break;
+ }
+}
+
static int
compute_baseline_pipe_bpp(struct intel_crtc *crtc,
struct intel_crtc_state *pipe_config)
@@ -10615,6 +10638,8 @@ compute_baseline_pipe_bpp(struct intel_crtc *crtc,
if (connector_state->crtc != &crtc->base)
continue;
+ connected_sink_force_bpp(to_intel_digital_connector_state(connector_state),
+ pipe_config);
connected_sink_compute_bpp(to_intel_connector(connector),
pipe_config);
}
--
2.9.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-18 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 22:29 [RFC 1/2] drm/i915: Add connector property to force bpc Sripada, Radhakrishna
2017-10-18 22:29 ` Sripada, Radhakrishna [this message]
2017-10-18 22:48 ` ✗ Fi.CI.BAT: warning for series starting with [RFC,1/2] " Patchwork
2017-10-19 7:13 ` [RFC 1/2] " Daniel Vetter
2017-10-19 12:56 ` Jani Nikula
2017-10-19 14:08 ` Ville Syrjälä
2017-10-20 23:54 ` Sripada, Radhakrishna
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=20171018222949.11140-2-radhakrishna.sripada@intel.com \
--to=radhakrishna.sripada@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.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