From: Peter Antoine <peter.antoine@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, benjamin.widawsky@intel.com
Subject: Re: [PATCH] drm/i915/sysfs: Adding mocs_state
Date: Wed, 4 May 2016 14:32:53 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.10.1605041432100.3052@peterant-linux2> (raw)
In-Reply-To: <20160504132306.GB19266@nuc-i3427.alporthouse.com>
Will wait for more comments, then will respin with a different commit
message. Is the rest of the patch ok?
Peter.
On Wed, 4 May 2016, Chris Wilson wrote:
> On Wed, May 04, 2016 at 02:16:23PM +0100, Peter Antoine wrote:
>> The following patch adds the current MOCS state to the sysfs file
>> system. This patch has been added so that userspace can validate the
>> MOCS settings that have been programmed.
>
> These only correspond to the state the kernel may program, not the state
> that has been programmed.
> -Chris
>
>
--
Peter Antoine (Android Graphics Driver Software Engineer)
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-04 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:16 [PATCH] drm/i915/sysfs: Adding mocs_state Peter Antoine
2016-05-04 13:23 ` Chris Wilson
2016-05-04 13:32 ` Peter Antoine [this message]
2016-05-04 13:47 ` Chris Wilson
2016-05-04 14:23 ` Antoine, Peter
2016-05-04 14:38 ` Ville Syrjälä
2016-05-04 14:51 ` Peter Antoine
2016-05-04 16:55 ` Ville Syrjälä
2016-05-05 7:17 ` Antoine, Peter
2016-05-06 8:57 ` Antoine, Peter
2016-05-06 11:16 ` Ville Syrjälä
2016-05-06 13:26 ` Peter Antoine
2016-05-09 7:39 ` Daniel Vetter
2016-05-04 14:57 ` Chris Wilson
2016-05-04 14:23 ` ✗ Fi.CI.BAT: failure for " Patchwork
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=alpine.DEB.2.10.1605041432100.3052@peterant-linux2 \
--to=peter.antoine@intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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).