From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Kumar, Mahesh" <mahesh1.kumar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH 0/3] Decode memdev info and bandwidth and implemnt latency WA
Date: Wed, 18 Jul 2018 15:03:58 +0300 [thread overview]
Message-ID: <20180718120358.GW5565@intel.com> (raw)
In-Reply-To: <eb1907cc-3b2f-9171-2f79-dee5dd64ffdf@intel.com>
On Sat, Jul 14, 2018 at 07:42:17PM +0530, Kumar, Mahesh wrote:
>
>
> On 7/13/2018 8:21 PM, Ville Syrjälä wrote:
> > On Fri, Jul 13, 2018 at 07:41:21PM +0530, Mahesh Kumar wrote:
> >> This series adds support to calculate system memdev parameters and calculate
> > What's "memdev"?
> memory device.
Still not sure what that means. Makes me think of something akin to chardev
or blockdev. I guess I'd just call it mem_info or something like that.
> -Mahesh
> >
> >> total system memory bandwidth. This parameters and BW will be used to enable
> >> WM level-0 latency workaround and display memory bandwidth related WA for gen9.
> >>
> >> Mahesh Kumar (3):
> >> drm/i915/bxt: Decode memory bandwidth and parameters
> >> drm/i915/skl+: Decode memory bandwidth and parameters
> >> drm/i915: Implement 16GB dimm wa for latency level-0
> >>
> >> drivers/gpu/drm/i915/i915_drv.c | 261 ++++++++++++++++++++++++++++++++++++++++
> >> drivers/gpu/drm/i915/i915_drv.h | 13 ++
> >> drivers/gpu/drm/i915/i915_reg.h | 51 ++++++++
> >> drivers/gpu/drm/i915/intel_pm.c | 13 ++
> >> 4 files changed, 338 insertions(+)
> >>
> >> --
> >> 2.16.2
> >>
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-18 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:11 [PATCH 0/3] Decode memdev info and bandwidth and implemnt latency WA Mahesh Kumar
2018-07-13 14:11 ` [PATCH 1/3] drm/i915/bxt: Decode memory bandwidth and parameters Mahesh Kumar
2018-07-13 14:11 ` [PATCH 2/3] drm/i915/skl+: " Mahesh Kumar
2018-07-13 14:11 ` [PATCH 3/3] drm/i915: Implement 16GB dimm wa for latency level-0 Mahesh Kumar
2018-07-13 14:57 ` Ville Syrjälä
2018-07-14 14:10 ` Kumar, Mahesh
2018-07-18 12:04 ` Ville Syrjälä
2018-07-18 12:34 ` Kumar, Mahesh
2018-07-13 14:32 ` ✗ Fi.CI.SPARSE: warning for Decode memdev info and bandwidth and implemnt latency WA Patchwork
2018-07-13 14:46 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-13 14:51 ` [PATCH 0/3] " Ville Syrjälä
2018-07-14 14:12 ` Kumar, Mahesh
2018-07-18 12:03 ` Ville Syrjälä [this message]
2018-07-18 12:23 ` Kumar, Mahesh
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=20180718120358.GW5565@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mahesh1.kumar@intel.com \
--cc=rodrigo.vivi@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