From: sonika <sonika.jindal@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/skl: Update edp 1.4 DDI translation table
Date: Tue, 24 Feb 2015 10:28:24 +0530 [thread overview]
Message-ID: <54EC04F0.2030704@intel.com> (raw)
In-Reply-To: <20150224001235.GK24485@phenom.ffwll.local>
On Tuesday 24 February 2015 05:42 AM, Daniel Vetter wrote:
> On Sat, Feb 21, 2015 at 11:10:51AM +0530, Sonika Jindal wrote:
>> Updating recommended DDI translation table for edp 1.4
>> as per bspec update
>>
>> Signed-off-by: Sonika Jindal <sonika.jindal@intel.com>
>> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_ddi.c | 18 +++++++++---------
>> 1 file changed, 9 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
>> index 114b729..f17cc48 100644
>> --- a/drivers/gpu/drm/i915/intel_ddi.c
>> +++ b/drivers/gpu/drm/i915/intel_ddi.c
>> @@ -141,16 +141,16 @@ static const struct ddi_buf_trans skl_ddi_translations_dp[] = {
>>
>> /* eDP 1.4 low vswing translation parameters */
>> static const struct ddi_buf_trans skl_ddi_translations_edp[] = {
> I don't have an edp translation table at all for skl. Does this really
> apply on -nightly? If not please make it clear in the cover letter what
> your depencies are or just send everything in one patch series.
>
> Thanks, Daniel
Hi Daniel,
Yes my bad in missing that info. This patch is dependent on
"drm/i915/skl: Add support for edp1.4 low vswing"
which is merged on -internal. Do I need to send out those rebased
patches for -nightly?
Regards,
Sonika
>> - { 0x00000018, 0x00000428 },
>> - { 0x00002016, 0x00000067 },
>> - { 0x00006012, 0x00000032 },
>> + { 0x00000018, 0x000000a8 },
>> + { 0x00002016, 0x000000ab },
>> + { 0x00006012, 0x000000a2 },
>> { 0x00008010, 0x00000088 },
>> - { 0x00000018, 0x00000067 },
>> - { 0x00004014, 0x00000032 },
>> - { 0x00006012, 0x00000098 },
>> - { 0x00000018, 0x00000032 },
>> - { 0x00005013, 0x00000098 },
>> - { 0x00006012, 0x0000001e },
>> + { 0x00000018, 0x000000ab },
>> + { 0x00004014, 0x000000a2 },
>> + { 0x00006012, 0x000000a6 },
>> + { 0x00000018, 0x000000a2 },
>> + { 0x00005013, 0x0000009c },
>> + { 0x00000018, 0x00000088 },
>> };
>>
>>
>> --
>> 1.7.10.4
>>
>> _______________________________________________
>> 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-02-24 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 5:40 [PATCH] drm/i915/skl: Update edp 1.4 DDI translation table Sonika Jindal
2015-02-24 0:12 ` Daniel Vetter
2015-02-24 4:58 ` sonika [this message]
2015-02-24 10:44 ` 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=54EC04F0.2030704@intel.com \
--to=sonika.jindal@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.