From: "Kumar, Shobhit" <shobhit.kumar@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
Shobhit Kumar <shobhit.kumar@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] Misc WM fixes and Arbitrated Display Bandwidth WA for SKL
Date: Fri, 15 Jan 2016 10:32:19 +0530 [thread overview]
Message-ID: <56987D5B.3010808@linux.intel.com> (raw)
In-Reply-To: <20160115014835.GG13799@intel.com>
On 01/15/2016 07:18 AM, Matt Roper wrote:
> On Thu, Jan 14, 2016 at 05:32:41PM +0530, Shobhit Kumar wrote:
>> Hi,
>> This series add a set of updates to the WM calculation and also enables
>> arbitrated display bandwidth based WA. Some of these patches do overlap
>> with Matts work but we wanted to send them out as we have them in our
>> internal testing for early review. Most likley some of them can be
>> superceded by patches from Matt, or can be re-used if deemed necessary.
>
> I've left some feedback on your patches, but it was all pretty minor;
> they look pretty good overall. So I think we should polish up this set
> and merge it; I've got more SKL WM work coming (more atomic-y watermark
> calculation and programming) but I'll hold off on that until your series
> lands so that I don't cause too much thrash.
Thanks Matt for the quick review. I will get the comments addressed and
final patches uploaded quickly.
Regards
Shobhit
>
> Thanks.
>
>
> Matt
>
>>
>> Especially "drm/i915/skl+: Use fb size for relative data rate calculation"
>> this already addresses some of Ville's comment on similar patch from Matt.
>>
>> Regards
>> Shobhit
>>
>> Kumar, Mahesh (6):
>> drm/i915/skl+: Use proper bytes_per_pixel during WM calculation
>> drm/i915/skl+: Use fb size for relative data rate calculation
>> drm/i915/skl+: calculate ddb minimum allocation
>> drm/i915/skl+: calculate plane pixel rate.
>> drm/i915/skl+: Use scaling amount for plane data rate calculation
>> drm/i915/skl: WA for watermark calculation based on Arbitrated Display
>> BW
>>
>> Shobhit Kumar (1):
>> drm/i915: Add support to parse DMI table and get platform memory info
>>
>> drivers/gpu/drm/i915/i915_dma.c | 19 +++
>> drivers/gpu/drm/i915/i915_drv.h | 15 ++
>> drivers/gpu/drm/i915/intel_drv.h | 2 +
>> drivers/gpu/drm/i915/intel_pm.c | 294 +++++++++++++++++++++++++++++++++++++--
>> 4 files changed, 316 insertions(+), 14 deletions(-)
>>
>> --
>> 2.4.3
>>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-15 5:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 12:02 [PATCH 0/7] Misc WM fixes and Arbitrated Display Bandwidth WA for SKL Shobhit Kumar
2016-01-14 12:02 ` [PATCH 1/7] drm/i915/skl+: Use proper bytes_per_pixel during WM calculation Shobhit Kumar
2016-01-14 19:07 ` Matt Roper
2016-01-19 9:56 ` Kumar, Shobhit
2016-01-14 12:02 ` [PATCH 2/7] drm/i915/skl+: Use fb size for relative data rate calculation Shobhit Kumar
2016-01-15 0:16 ` Matt Roper
2016-01-14 12:02 ` [PATCH 3/7] drm/i915/skl+: calculate ddb minimum allocation Shobhit Kumar
2016-01-15 0:39 ` Matt Roper
2016-01-14 12:02 ` [PATCH 4/7] drm/i915/skl+: calculate plane pixel rate Shobhit Kumar
2016-01-15 0:57 ` Matt Roper
2016-01-14 12:02 ` [PATCH 5/7] drm/i915/skl+: Use scaling amount for plane data rate calculation Shobhit Kumar
2016-01-15 1:15 ` Matt Roper
2016-01-14 12:02 ` [PATCH 6/7] drm/i915: Add support to parse DMI table and get platform memory info Shobhit Kumar
2016-01-15 1:44 ` Matt Roper
2016-01-27 16:04 ` Kumar, Shobhit
2016-01-14 12:02 ` [PATCH 7/7] drm/i915/skl: WA for watermark calculation based on Arbitrated Display BW Shobhit Kumar
2016-01-14 15:30 ` kbuild test robot
2016-01-14 17:35 ` Damien Lespiau
2016-01-14 17:25 ` kbuild test robot
2016-01-14 13:20 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-15 1:48 ` [PATCH 0/7] Misc WM fixes and Arbitrated Display Bandwidth WA for SKL Matt Roper
2016-01-15 5:02 ` Kumar, Shobhit [this message]
2016-01-25 4:48 ` Shobhit Kumar
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=56987D5B.3010808@linux.intel.com \
--to=shobhit.kumar@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=shobhit.kumar@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).