From: "Purushothaman, Vijay A" <vijay.a.purushothaman@linux.intel.com>
To: "Daniel Vetter" <daniel@ffwll.ch>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics <intel-gfx@lists.freedesktop.org>
Subject: Re: [v2 2/5] drm/i915: Limit max VCO supported in CHV to 6.48GHz
Date: Tue, 03 Mar 2015 20:27:19 +0530 [thread overview]
Message-ID: <54F5CBCF.2030204@linux.intel.com> (raw)
In-Reply-To: <20150223161314.GE24485@phenom.ffwll.local>
On 2/23/2015 9:43 PM, Daniel Vetter wrote:
> On Mon, Feb 16, 2015 at 01:21:34PM +0200, Ville Syrjälä wrote:
>> On Mon, Feb 16, 2015 at 03:07:59PM +0530, Vijay Purushothaman wrote:
>>> As per the recommendation from PHY team, limit the max vco supported in CHV to 6.48 GHz
>>>
>>> Signed-off-by: Vijay Purushothaman <vijay.a.purushothaman@linux.intel.com>
>>> ---
>>> drivers/gpu/drm/i915/intel_display.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>>> index 3b0fe9f..4e710f6 100644
>>> --- a/drivers/gpu/drm/i915/intel_display.c
>>> +++ b/drivers/gpu/drm/i915/intel_display.c
>>> @@ -390,7 +390,7 @@ static const intel_limit_t intel_limits_chv = {
>>> * them would make no difference.
>>> */
>>> .dot = { .min = 25000 * 5, .max = 540000 * 5},
>>> - .vco = { .min = 4860000, .max = 6700000 },
>>> + .vco = { .min = 4860000, .max = 6480000 },
>> I have a patch here to reduce the minimum to 4.80 GHz, otherwise I can't
>> get my 2560x1440 HDMI display working (241.5 MHz clock). With that change
>> we still have a gap (233-240 MHz) in the frequencies we can produce.
>> Reducing the max to 6.48 GHz will increase that gap to 216-240 MHz, which
>> is a bit unfortunate. But if that's the recommendation we should follow
>> it I suppose, and hope no HDMI displays will want such frequencies.
>>
>> Is there an updated spreadsheet available with the new limits? Quite a
>> few of the frequencies in the original spreadsheet did have vco>6.48
>> GHz.
> Has the updated doc been dug up meanwhile? A big part of review is getting
> access to docs and making sure they're up-to-date too ...
> -Daniel
I sent the copy of excel sheet that i am using to both of you in another
mail. I still end up relying on windows driver folks since they seem to
be having latest information about PHY.
Thanks,
Vijay
>> I any case this seems OK, so
>> Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>>> .n = { .min = 1, .max = 1 },
>>> .m1 = { .min = 2, .max = 2 },
>>> .m2 = { .min = 24 << 22, .max = 175 << 22 },
>>> --
>>> 1.7.9.5
>>>
>>> _______________________________________________
>>> Intel-gfx mailing list
>>> Intel-gfx@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>> --
>> Ville Syrjälä
>> Intel OTC
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-03 14:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 18:31 [PATCH] drm/i915: More DPIO magic for CHV HDMI & DP Vijay Purushothaman
2015-01-30 11:09 ` Ville Syrjälä
2015-02-12 13:19 ` Purushothaman, Vijay A
2015-02-16 9:37 ` [v2 0/5] " Vijay Purushothaman
2015-02-16 9:37 ` [v2 1/5] drm/i915: Add new PHY reg definitions for lock threshold Vijay Purushothaman
2015-02-16 11:21 ` Ville Syrjälä
2015-02-16 9:37 ` [v2 2/5] drm/i915: Limit max VCO supported in CHV to 6.48GHz Vijay Purushothaman
2015-02-16 11:21 ` Ville Syrjälä
2015-02-23 16:13 ` Daniel Vetter
2015-03-03 14:57 ` Purushothaman, Vijay A [this message]
2015-03-05 15:52 ` Daniel Vetter
2015-03-05 15:59 ` Ville Syrjälä
2015-02-16 9:38 ` [v2 3/5] drm/i915: Disable M2 frac division for integer case Vijay Purushothaman
2015-02-16 11:23 ` Ville Syrjälä
2015-03-03 15:11 ` [PATCH 1/3] " Vijay Purushothaman
2015-03-03 15:36 ` Ville Syrjälä
2015-03-05 13:49 ` Purushothaman, Vijay A
2015-03-05 14:00 ` Vijay Purushothaman
2015-03-10 9:23 ` Daniel Vetter
2015-02-16 9:38 ` [v2 4/5] drm/i915: Initialize CHV digital lock detect threshold Vijay Purushothaman
2015-02-16 11:27 ` Ville Syrjälä
2015-03-03 15:13 ` [PATCH 2/3] " Vijay Purushothaman
2015-03-03 15:38 ` Ville Syrjälä
2015-03-05 13:50 ` Purushothaman, Vijay A
2015-03-05 14:02 ` Vijay Purushothaman
2015-02-16 9:38 ` [v2 5/5] drm/i915: Update prop, int co-eff and gain threshold for CHV Vijay Purushothaman
2015-02-16 11:32 ` Ville Syrjälä
2015-03-03 14:59 ` Purushothaman, Vijay A
2015-03-03 15:14 ` [PATCH 3/3] " Vijay Purushothaman
2015-03-03 15:45 ` Ville Syrjälä
2015-03-05 14:03 ` Vijay Purushothaman
2015-03-05 14:35 ` Ville Syrjälä
2015-02-23 16:13 ` [v2 0/5] More DPIO magic for CHV HDMI & DP Daniel Vetter
2015-02-10 12:43 ` [PATCH] drm/i915: " Jani Nikula
2015-02-12 13:20 ` Purushothaman, Vijay A
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=54F5CBCF.2030204@linux.intel.com \
--to=vijay.a.purushothaman@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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