From: Daniel Vetter <daniel@ffwll.ch>
To: jeff.mcgee@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: Update rps interrupt limits
Date: Fri, 7 Feb 2014 10:26:28 +0100 [thread overview]
Message-ID: <20140207092628.GW17001@phenom.ffwll.local> (raw)
In-Reply-To: <1391535421-28132-1-git-send-email-jeff.mcgee@intel.com>
On Tue, Feb 04, 2014 at 11:37:01AM -0600, jeff.mcgee@intel.com wrote:
> From: Jeff McGee <jeff.mcgee@intel.com>
>
> sysfs changes to rps min and max delay were only triggering an update
> of the rps interrupt limits if the active delay required an update.
> This change ensures that interrupt limits are always updated.
>
> v2: correct compile issue missed on rebase
> v3: add igt testcases to signed-off-by section
>
> Testcase: igt/pm_rps/min-max-config-idle
> Testcase: igt/pm_rps/min-max-config-loaded
> Signed-off-by: Jeff McGee <jeff.mcgee@intel.com>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-02-07 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 20:32 [PATCH] drm/i915: Update rps interrupt limits jeff.mcgee
2013-11-12 20:32 ` jeff.mcgee
2013-11-12 21:04 ` [PATCH v2] " jeff.mcgee
2013-11-13 19:09 ` Daniel Vetter
2014-02-04 17:37 ` [PATCH v3] " jeff.mcgee
2014-02-07 9:26 ` Daniel Vetter [this message]
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=20140207092628.GW17001@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeff.mcgee@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