From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Mahesh Kumar <mahesh1.kumar@intel.com>, intel-gfx@lists.freedesktop.org
Cc: maarten.lankhorst@intel.com
Subject: Re: [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC
Date: Wed, 07 Dec 2016 17:35:09 -0200 [thread overview]
Message-ID: <1481139309.2375.18.camel@intel.com> (raw)
In-Reply-To: <20161201154940.24446-1-mahesh1.kumar@intel.com>
Em Qui, 2016-12-01 às 21:19 +0530, Mahesh Kumar escreveu:
> This series implements following set of functionality
> Implement IPC WA's for Broxton/KBL
> Enable IPC in supported platforms
> Convert WM calculation to fixed point calculation
> Calculation of System memory Bandwidth for SKL/KBL/BXT
> Implementation of Arbitrated memory Bandwidth related WM WA's
Pushed patches 1, 2, 3, 5 and 6, with small bikesheds applied. Thanks
for the patches!
(actually I had a little problem with dim, so right now only dinq has
the patches, drm-tip doesn't, soon they will appear)
Let's resume the discussion on the remaining patches. For a possible
next series, make sure to rebase and send only what's not applied.
>
>
> Mahesh Kumar (8):
> drm/i915/skl: Add variables to check x_tile and y_tile
> drm/i915/bxt: IPC WA for Broxton
> drm/i915/kbl: IPC workaround for kabylake
> drm/i915/bxt: Enable IPC support
> drm/i915/skl+: change WM calc to fixed point 16.16
> drm/i915: Add intel_atomic_get_existing_crtc_state function
> drm/i915: Decode system memory bandwidth
> drm/i915/gen9: WM memory bandwidth related workaround
>
> drivers/gpu/drm/i915/i915_drv.c | 175 ++++++++++++++++++++++
> drivers/gpu/drm/i915/i915_drv.h | 109 ++++++++++++++
> drivers/gpu/drm/i915/i915_reg.h | 38 +++++
> drivers/gpu/drm/i915/intel_display.c | 24 ++++
> drivers/gpu/drm/i915/intel_drv.h | 15 ++
> drivers/gpu/drm/i915/intel_pm.c | 272
> +++++++++++++++++++++++++++++------
> 6 files changed, 586 insertions(+), 47 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-07 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 15:49 [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 1/8] drm/i915/skl: Add variables to check x_tile and y_tile Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 2/8] drm/i915/bxt: IPC WA for Broxton Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 3/8] drm/i915/kbl: IPC workaround for kabylake Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 4/8] drm/i915/bxt: Enable IPC support Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 5/8] drm/i915/skl+: change WM calc to fixed point 16.16 Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 6/8] drm/i915: Add intel_atomic_get_existing_crtc_state function Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 7/8] drm/i915: Decode system memory bandwidth Mahesh Kumar
2016-12-08 23:55 ` Paulo Zanoni
2017-02-15 15:00 ` Mahesh Kumar
2016-12-01 15:49 ` [PATCH v7 8/8] drm/i915/gen9: WM memory bandwidth related workaround Mahesh Kumar
2016-12-15 17:07 ` Paulo Zanoni
2017-02-15 15:00 ` Mahesh Kumar
2016-12-01 16:15 ` ✓ Fi.CI.BAT: success for GEN-9 Arbitrated Bandwidth WM WA's & IPC (rev3) Patchwork
2016-12-07 19:35 ` Paulo Zanoni [this message]
2016-12-08 16:00 ` [PATCH v7 0/8] GEN-9 Arbitrated Bandwidth WM WA's & IPC Daniel Vetter
2016-12-08 16:12 ` Zanoni, Paulo R
2016-12-08 16:18 ` 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=1481139309.2375.18.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=mahesh1.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