summaryrefslogtreecommitdiff
path: root/drivers/net/can
diff options
context:
space:
mode:
authorEugeni Dodonov <eugeni.dodonov@intel.com>2012-02-14 17:44:48 +0400
committerJesse Barnes <jbarnes@virtuousgeek.org>2012-02-16 05:43:41 +0400
commit1c8ecf80fdee4e7b23a9e7da7ff9bd59ba2dcf96 (patch)
tree0cbb7a8b88c100acb3df605fc8908845729765cb /drivers/net/can
parentd71de14ddf423ccc9a2e3f7e37553c99ead20d7c (diff)
downloadlinux-1c8ecf80fdee4e7b23a9e7da7ff9bd59ba2dcf96.tar.xz
drm/i915: do not enable RC6p on Sandy Bridge
With base on latest findings, RC6p seems to be respondible for RC6-related issues on Sandy Bridge platform. To work-around those issues, the previous solution was to completely disable RC6 on Sandy Bridge for the past few releases, even if plain RC6 was not giving any issues. What this patch does is preventing RC6p from being enabled on Sandy Bridge even if users enable RC6 via a kernel parameter. So it won't change the defaults in any way, but will ensure that if users do enable RC6 manually it won't break their machines by enabling this extra state. Proper fix for this (enabling specific RC6 states according to the GPU generation) were proposed for the -next kernel, but we are too late in the release process now to pick such changes. Acked-by: Keith Packard <keithp@keithp.com> Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/net/can')
0 files changed, 0 insertions, 0 deletions