public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: sonika <sonika.jindal@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 03/13] drm/i915: Don't copy the DP source rates arrays
Date: Mon, 16 Mar 2015 13:55:11 +0200	[thread overview]
Message-ID: <20150316115511.GI17419@intel.com> (raw)
In-Reply-To: <5506BF88.3000804@intel.com>

On Mon, Mar 16, 2015 at 05:03:28PM +0530, sonika wrote:
> 
> On Monday 16 March 2015 04:25 PM, Ville Syrjälä wrote:
> > On Mon, Mar 16, 2015 at 03:07:05PM +0530, Jindal, Sonika wrote:
> >>
> >> On 3/16/2015 3:04 PM, Ville Syrjälä wrote:
> >>> On Mon, Mar 16, 2015 at 02:43:19PM +0530, Jindal, Sonika wrote:
> >>>>
> >>>> On 3/12/2015 8:40 PM, ville.syrjala@linux.intel.com wrote:
> >>>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>>>>
> >>>>> The source rates don't change, so we can just point the caller at the
> >>>>> const arrays.
> >>>>>
> >>>>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>>>> ---
> >>>>>     drivers/gpu/drm/i915/intel_dp.c | 24 ++++++++++--------------
> >>>>>     1 file changed, 10 insertions(+), 14 deletions(-)
> >>>>>
> >>>>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> >>>>> index d638f5e..537f1d0 100644
> >>>>> --- a/drivers/gpu/drm/i915/intel_dp.c
> >>>>> +++ b/drivers/gpu/drm/i915/intel_dp.c
> >>>>> @@ -1157,22 +1157,18 @@ intel_read_sink_rates(struct intel_dp *intel_dp, int *sink_rates)
> >>>>>     }
> >>>>>
> >>>>>     static int
> >>>>> -intel_read_source_rates(struct intel_dp *intel_dp, int *source_rates)
> >>>>> +intel_dp_source_rates(struct intel_dp *intel_dp, const int **source_rates)
> >>>>>     {
> >>>>>     	struct drm_device *dev = intel_dp_to_dev(intel_dp);
> >>>>> -	int i;
> >>>>> -	int max_default_rate;
> >>>>>
> >>>>> -	if (INTEL_INFO(dev)->gen >= 9 && intel_dp->supported_rates[0]) {
> >>>>> -		for (i = 0; i < ARRAY_SIZE(gen9_rates); ++i)
> >>>>> -			source_rates[i] = gen9_rates[i];
> >>>>> -	} else {
> >>>>> -		/* Index of the max_link_bw supported + 1 */
> >>>>> -		max_default_rate = (intel_dp_max_link_bw(intel_dp) >> 3) + 1;
> >>>>> -		for (i = 0; i < max_default_rate; ++i)
> >>>>> -			source_rates[i] = default_rates[i];
> >>>>> +	if (INTEL_INFO(dev)->gen >= 9) {
> >>>>> +		*source_rates = gen9_rates;
> >>>>> +		return ARRAY_SIZE(gen9_rates);
> >>>>>     	}
> >>>>> -	return i;
> >>>>> +
> >>>>> +	*source_rates = default_rates;
> >>>>> +
> >>>>> +	return (intel_dp_max_link_bw(intel_dp) >> 3) + 1;
> >>>> Now when intel_dp_max_link_bw doesn't do much, can this be simply
> >>>> ARRAY_SIZE(default_rates)? and we can get away with this function.
> >>> If you'll look at patch 6 you'll see me moving the source limitations
> >>> from intel_dp_max_link_bw() to intel_dp_source_rates().
> >>>
> >> Yes, thats why I think we can remove the intel_dp_max_link_bw function
> >> altogether.
> > We still need it to limit the sink rates appropriately when
> > SUPPORTED_LINK_RATES is not present.
> But with this series, haven't we already removed that? We are not using 
> it anymore.

SUPPORTED_LINK_RATES may not be there. We obviously still need to
find out what's the maximum link rate supported by the sink when it's
not available. Hence we still need intel_dp_max_link_bw() to decode
the MAX_LINK_RATE (actually the only thing it does after my
patches is filter out invalid values of MAX_LINK_RATE and issue a
warning).

> >>>>>     }
> >>>>>
> >>>>>     static void
> >>>>> @@ -1269,12 +1265,12 @@ intel_dp_compute_config(struct intel_encoder *encoder,
> >>>>>     	int link_avail, link_clock;
> >>>>>     	int sink_rates[8];
> >>>>>     	int supported_rates[8] = {0};
> >>>>> -	int source_rates[8];
> >>>>> +	const int *source_rates;
> >>>>>     	int source_len, sink_len, supported_len;
> >>>>>
> >>>>>     	sink_len = intel_read_sink_rates(intel_dp, sink_rates);
> >>>>>
> >>>>> -	source_len = intel_read_source_rates(intel_dp, source_rates);
> >>>>> +	source_len = intel_dp_source_rates(intel_dp, &source_rates);
> >>>>>
> >>>>>     	supported_len = intel_supported_rates(source_rates, source_len,
> >>>>>     				sink_rates, sink_len, supported_rates);
> >>>>>

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-16 11:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 15:10 [PATCH 00/13] drm/i915: Clean up the DP link rate code ville.syrjala
2015-03-12 15:10 ` [PATCH 01/13] drm/i915: Make the DP rates int instead of uint32_t ville.syrjala
2015-03-13 22:45   ` Todd Previte
2015-03-12 15:10 ` [PATCH 02/13] drm/i915: Store the converted link rates in intel_dp->supported_rates[] ville.syrjala
2015-03-13 22:58   ` Todd Previte
2015-03-12 15:10 ` [PATCH 03/13] drm/i915: Don't copy the DP source rates arrays ville.syrjala
2015-03-13 23:04   ` Todd Previte
2015-03-16  9:13   ` Jindal, Sonika
2015-03-16  9:34     ` Ville Syrjälä
2015-03-16  9:37       ` Jindal, Sonika
2015-03-16 10:55         ` Ville Syrjälä
2015-03-16 11:33           ` sonika
2015-03-16 11:55             ` Ville Syrjälä [this message]
2015-03-12 15:10 ` [PATCH 04/13] drm/i915: Don't copy sink rates either ville.syrjala
2015-03-12 15:10 ` [PATCH 05/13] drm/i915: Remove special case from intel_supported_rates() ville.syrjala
2015-03-12 15:10 ` [PATCH 06/13] drm/i915: Fully separate source vs. sink rates ville.syrjala
2015-03-17 10:06   ` Daniel Vetter
2015-03-12 15:10 ` [PATCH 07/13] drm/i915: Hide the source vs. sink rate handling from intel_dp_compute_config() ville.syrjala
2015-03-13 11:44   ` sonika
2015-03-13 12:02     ` Ville Syrjälä
2015-03-13 11:56       ` sonika
2015-03-12 15:10 ` [PATCH 08/13] drm/i915: Fix max link rate in intel_dp_mode_valid() ville.syrjala
2015-03-12 15:10 ` [PATCH 09/13] drm/i915: Use DP_LINK_RATE_SET whenever possible ville.syrjala
2015-03-12 15:10 ` [PATCH 10/13] drm/i915: Fix MST link rate handling ville.syrjala
2015-03-12 15:10 ` [PATCH 11/13] drm/i915: Avoid overflowing the DP link rate arrays ville.syrjala
2015-03-12 15:10 ` [PATCH 12/13] drm/i915: Add eDP intermediate frequencies for CHV ville.syrjala
2015-03-12 15:10 ` [PATCH 13/13] drm/i915: Include the sink/source/supported rates in debug output ville.syrjala
2015-03-12 19:42   ` shuang.he
2015-03-13 17:40 ` [PATCH 14/13] drm/i915: Unconfuse DP link rate array names ville.syrjala
2015-03-17  9:45   ` sonika
2015-03-17 10:13     ` 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=20150316115511.GI17419@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sonika.jindal@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