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 2/3] drm/i915: Decode system memory bandwidth
Date: Wed, 15 Mar 2017 18:19:41 -0300 [thread overview]
Message-ID: <1489612781.2442.84.camel@intel.com> (raw)
In-Reply-To: <20170215144840.20461-3-mahesh1.kumar@intel.com>
Em Qua, 2017-02-15 às 20:18 +0530, Mahesh Kumar escreveu:
> This patch adds support to decode system memory bandwidth
> which will be used for arbitrated display memory percentage
> calculation in GEN9 based system.
>
> Changes from v1:
> - Address comments from Paulo
> - implement decode function for SKL/KBL also
> Changes from v2:
> - Rewrite the code as per HW team inputs
> - Addresses review comments
> Changes from v3:
> - Fix compilation warning
> Changes from v4:
> - Address review comments from Paulo
> - Round-off the frequency & bandwidth results (Paulo)
>
> Signed-off-by: Mahesh Kumar <mahesh1.kumar@intel.com>
> ---
>
<snip>
> +
> +static void
> +intel_get_memdev_info(struct drm_i915_private *dev_priv)
> +{
> + struct memdev_info *memdev_info = &dev_priv->memdev_info;
> + int ret;
> +
> + memdev_info->valid = false;
> + memdev_info->rank = I915_DRAM_RANK_INVALID;
> + memdev_info->num_channels = 0;
> +
> + if (!IS_GEN9(dev_priv))
> + return;
> +
> + if (IS_BROXTON(dev_priv))
> + ret = bxt_get_memdev_info(dev_priv);
> + else
> + ret = skl_get_memdev_info(dev_priv);
> + if (ret)
> + return;
Quick question: we now have GLK and it's going to call
skl_get_memdev_info(). Is this intentional?
> +
> + DRM_DEBUG_DRIVER("DRAM bandwidth: %u KBps, total-channels:
> %u\n",
> + memdev_info->bandwidth_kbps,
> + memdev_info->num_channels);
> + DRM_DEBUG_DRIVER("DRAM rank: %s rank\n",
> + (memdev_info->rank ==
> I915_DRAM_RANK_DUAL) ?
> + "dual" : "single");
> +}
> +
Besides, I see BAT pointed a bunch of WARNs for this series, so I'll
wait until BAT gives use the approval stamp before I continue this
review, since it's likely that I'll end up having to re-review once the
WARNs get fixed.
Thanks,
Paulo
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-15 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:48 [PATCH 0/3] Enable IPC & WM related WA's Mahesh Kumar
2017-02-15 14:48 ` [PATCH 1/3] drm/i915/bxt: Enable IPC support Mahesh Kumar
2017-02-15 14:48 ` [PATCH 2/3] drm/i915: Decode system memory bandwidth Mahesh Kumar
2017-03-15 21:19 ` Paulo Zanoni [this message]
2017-02-15 14:48 ` [PATCH 3/3] drm/i915/gen9: WM memory bandwidth related workaround Mahesh Kumar
2017-02-15 17:23 ` ✗ Fi.CI.BAT: failure for Enable IPC & WM related WA's (rev3) Patchwork
2017-02-16 13:02 ` ✗ Fi.CI.BAT: warning " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-01-31 14:57 [PATCH 0/3] Enable IPC & WM related WA's Mahesh Kumar
2017-01-31 14:57 ` [PATCH 2/3] drm/i915: Decode system memory bandwidth Mahesh 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=1489612781.2442.84.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 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.