From: Jim Bride <jim.bride@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v8 09/12] Check pixel rate for DP to VGA dongle
Date: Wed, 7 Sep 2016 14:23:39 -0700 [thread overview]
Message-ID: <20160907212339.GD28453@shiv> (raw)
In-Reply-To: <1471430989-28161-10-git-send-email-mika.kahola@intel.com>
On Wed, Aug 17, 2016 at 01:49:45PM +0300, Mika Kahola wrote:
> Filter out a mode that exceeds the max pixel rate setting
> for DP to VGA dongle. This is defined in DPCD register 0x81
> if detailed cap info i.e. info field is 4 bytes long and
> it is available for DP downstream port.
>
> The register defines the pixel rate divided by 8 in MP/s.
>
> v2: DPCD read outs and computation moved to drm (Ville, Daniel)
> v3: Sink pixel rate computation moved to drm_dp_max_sink_dotclock()
> function (Daniel)
> v4: Use of drm_dp_helper.c routines to compute max pixel clock (Ville)
> v5: Use of intel_dp->downstream_ports to read out port capabilities.
> Code restructuring (Ville)
> v6: Move DP branch device check to drm_dp_helper.c (Daniel)
> v7: Cleanup as suggested by Ville
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
Reviewed-by: Jim Bride <jim.bride@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 91ffb79..25f459e 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -190,6 +190,29 @@ intel_dp_max_data_rate(int max_link_clock, int max_lanes)
> return (max_link_clock * max_lanes * 8) / 10;
> }
>
> +static int
> +intel_dp_downstream_max_dotclock(struct intel_dp *intel_dp)
> +{
> + struct intel_digital_port *intel_dig_port = dp_to_dig_port(intel_dp);
> + struct intel_encoder *encoder = &intel_dig_port->base;
> + struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> + int max_dotclk = dev_priv->max_dotclk_freq;
> + int ds_max_dotclk;
> +
> + int type = intel_dp->downstream_ports[0] & DP_DS_PORT_TYPE_MASK;
> +
> + if (type != DP_DS_PORT_TYPE_VGA)
> + return max_dotclk;
> +
> + ds_max_dotclk = drm_dp_downstream_max_clock(intel_dp->dpcd,
> + intel_dp->downstream_ports);
> +
> + if (ds_max_dotclk != 0)
> + max_dotclk = min(max_dotclk, ds_max_dotclk);;
> +
> + return max_dotclk;
> +}
> +
> static enum drm_mode_status
> intel_dp_mode_valid(struct drm_connector *connector,
> struct drm_display_mode *mode)
> @@ -199,7 +222,9 @@ intel_dp_mode_valid(struct drm_connector *connector,
> struct drm_display_mode *fixed_mode = intel_connector->panel.fixed_mode;
> int target_clock = mode->clock;
> int max_rate, mode_rate, max_lanes, max_link_clock;
> - int max_dotclk = to_i915(connector->dev)->max_dotclk_freq;
> + int max_dotclk;
> +
> + max_dotclk = intel_dp_downstream_max_dotclock(intel_dp);
>
> if (is_edp(intel_dp) && fixed_mode) {
> if (mode->hdisplay > fixed_mode->hdisplay)
> --
> 1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-07 21:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 10:49 [PATCH v8 00/12] drm/i915: DP branch devices Mika Kahola
2016-08-17 10:49 ` [PATCH v8 01/12] drm: Add missing DP downstream port types Mika Kahola
2016-08-17 10:49 ` [PATCH v8 02/12] drm: Drop VGA from bpc definitions Mika Kahola
2016-08-17 10:49 ` [PATCH v8 03/12] drm: Helper to read max clock rate Mika Kahola
2016-09-08 13:01 ` Ville Syrjälä
2016-09-08 13:18 ` Kahola, Mika
2016-08-17 10:49 ` [PATCH v8 04/12] drm: Helper to read max bits per component Mika Kahola
2016-09-08 13:03 ` Ville Syrjälä
2016-08-17 10:49 ` [PATCH v8 05/12] drm: Read DP branch device id Mika Kahola
2016-08-17 10:49 ` [PATCH v8 06/12] drm/i915: Cleanup DisplayPort AUX channel initialization Mika Kahola
2016-09-07 21:13 ` Jim Bride
2016-08-17 10:49 ` [PATCH v8 07/12] drm/i915: Read DP branch device HW revision Mika Kahola
2016-09-07 21:16 ` Jim Bride
2016-08-17 10:49 ` [PATCH v8 08/12] drm/i915: Read DP branch device SW revision Mika Kahola
2016-09-07 21:20 ` Jim Bride
2016-09-08 11:51 ` Kahola, Mika
2016-08-17 10:49 ` [PATCH v8 09/12] Check pixel rate for DP to VGA dongle Mika Kahola
2016-09-07 21:23 ` Jim Bride [this message]
2016-08-17 10:49 ` [PATCH v8 09/12] drm/i915: " Mika Kahola
2016-08-17 10:49 ` [PATCH v8 10/12] drm/i915: Update bits per component for display info Mika Kahola
2016-09-07 21:27 ` Jim Bride
2016-09-08 12:30 ` Kahola, Mika
2016-08-17 10:49 ` [PATCH v8 11/12] drm: Add DP branch device info on debugfs Mika Kahola
2016-09-07 21:30 ` Jim Bride
2016-08-17 10:49 ` [PATCH v8 12/12] drm/i915: Check TMDS clock DP to HDMI dongle Mika Kahola
2016-09-07 21:31 ` Jim Bride
2016-09-08 12:48 ` Ville Syrjälä
2016-09-09 7:45 ` Mika Kahola
2016-09-09 9:09 ` Ville Syrjälä
2016-09-09 13:23 ` Mika Kahola
2016-08-17 11:59 ` ✗ Ro.CI.BAT: failure for drm/i915: DP branch devices (rev9) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-08-17 10:16 [PATCH v8 00/12] drm/i915: DP branch devices Mika Kahola
2016-08-17 10:16 ` [PATCH v8 09/12] Check pixel rate for DP to VGA dongle Mika Kahola
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=20160907212339.GD28453@shiv \
--to=jim.bride@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@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;
as well as URLs for NNTP newsgroup(s).