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 6/7] drm/i915: Add support to parse DMI table and get platform memory info
Date: Wed, 27 Jan 2016 21:34:19 +0530 [thread overview]
Message-ID: <56A8EA83.90103@linux.intel.com> (raw)
In-Reply-To: <20160115014401.GF13799@intel.com>
On 01/15/2016 07:14 AM, Matt Roper wrote:
> On Thu, Jan 14, 2016 at 05:32:47PM +0530, Shobhit Kumar wrote:
>> This is needed for WM computation workaround for arbitrated display
>> bandwidth.
>>
>> Signed-off-by: Shobhit Kumar <shobhit.kumar@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_dma.c | 19 +++++++++++++++++++
>> drivers/gpu/drm/i915/i915_drv.h | 6 ++++++
>> 2 files changed, 25 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
>> index a0f5659..03c3131 100644
>> --- a/drivers/gpu/drm/i915/i915_dma.c
>> +++ b/drivers/gpu/drm/i915/i915_dma.c
>> @@ -49,6 +49,7 @@
>> #include <linux/pm.h>
>> #include <linux/pm_runtime.h>
>> #include <linux/oom.h>
>> +#include <linux/dmi.h>
>>
>>
>> static int i915_getparam(struct drm_device *dev, void *data,
>> @@ -855,6 +856,21 @@ static void intel_init_dpio(struct drm_i915_private *dev_priv)
>> }
>> }
>>
>> +static void dmi_decode_memory_info(const struct dmi_header *hdr, void *priv)
>> +{
>> + struct drm_i915_private *dev_priv = (struct drm_i915_private *) priv;
>> + const u8 *data = (const u8 *) hdr;
>> +
>> + if (hdr->type == 17 && hdr->length > 0x17) {
>
> I think there are some constants in include/linux/dmi.h that we can use
> instead of magic numbers. DMI_ENTRY_MEM_DEVICE.
>
Yeah will do that.
> I'm not familiar with any of this DMI stuff; it seems like there are
> functions elsewhere in the kernel (e.g., decode_dclk() in
> drivers/edac/i7core_edac.c) that decode this into a memdev_dmi_entry and
> then do some more robust/paranoid checking to determine the actual
> speed. Unfortunately it's static to that file and not directly callable
> by us.
>
> I wonder if it would make sense to refactor that structure and decoding
> out into the general DMI files and export them for module use so that we
> could just call those functions.
>
Perhaps we can but that will take some time. I will add paranoid parsing
as done in edac with minimal #defined offsets for now. Think that should
suffice. At next level we can work on exporting new functionality from
the DMI files.
Regards
Shobhit
>
> Matt
>
>> +
>> + /* Found a memory channel */
>> + dev_priv->dmi.mem_channel++;
>> +
>> + /* Get the speed */
>> + dev_priv->dmi.mem_speed = (uint16_t) (*((uint16_t *)(data + 0x15)));
>> + }
>> +}
>> +
>> /**
>> * i915_driver_load - setup chip and create an initial config
>> * @dev: DRM device
>> @@ -882,6 +898,9 @@ int i915_driver_load(struct drm_device *dev, unsigned long flags)
>> dev->dev_private = dev_priv;
>> dev_priv->dev = dev;
>>
>> + /* walk the dmi device table for getting platform memory information */
>> + dmi_walk(dmi_decode_memory_info, (void *) dev_priv);
>> +
>> /* Setup the write-once "constant" device info */
>> device_info = (struct intel_device_info *)&dev_priv->info;
>> memcpy(device_info, info, sizeof(dev_priv->info));
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 104bd18..f588993 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -1962,6 +1962,12 @@ struct drm_i915_private {
>> * NOTE: This is the dri1/ums dungeon, don't add stuff here. Your patch
>> * will be rejected. Instead look for a better place.
>> */
>> +
>> + /* DMI data for memory bandwidth calculation */
>> + struct {
>> + uint16_t mem_channel;
>> + uint16_t mem_speed;
>> + } dmi;
>> };
>>
>> static inline struct drm_i915_private *to_i915(const struct drm_device *dev)
>> --
>> 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-27 16:04 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 [this message]
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
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=56A8EA83.90103@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).