From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for v4.8
Date: Tue, 02 Aug 2016 15:22:01 +0300 [thread overview]
Message-ID: <87invjs6mu.fsf@intel.com> (raw)
In-Reply-To: <CA+55aFwmkuQRKV33V3DumqJpBjGkjDpoTBfCzO_K29xVd+mbnw@mail.gmail.com>
On Tue, 02 Aug 2016, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Aug 2, 2016 at 4:10 AM, Ville Syrjälä
> <ville.syrjala@linux.intel.com> wrote:
>>
>> I have a couple of pending PSR patches you may want to try as well,
>> if i915.enable_psr=0 helps.
>
> Yes. i915.enable_psr=0 seems to make the bad flickering go away.
>
> I'll try your git trees out later, but what exactly changed with
> regards to psr lately? It's set as a "dangerous" option, and even just
> clearing it caused
>
> Setting dangerous option enable_psr - tainting kernel
>
> which seems entirely bogus.
The warning comes from kernel/params.c for module_param_named_unsafe()
which has no way of knowing which values are safe, and complains if the
option is set at all.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-08-02 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 1:32 [git pull] drm for v4.8 Dave Airlie
2016-08-02 2:26 ` Linus Torvalds
2016-08-02 8:00 ` Daniel Vetter
2016-08-02 8:10 ` Ville Syrjälä
2016-08-02 11:28 ` Linus Torvalds
2016-08-02 12:22 ` Jani Nikula [this message]
2016-08-02 16:40 ` Linus Torvalds
2016-08-02 18:01 ` Daniel Vetter
2016-08-02 18:34 ` Ville Syrjälä
2016-08-02 11:47 ` Jiri Kosina
2016-08-02 12:19 ` Jiri Kosina
2016-08-02 12:27 ` Jani Nikula
2016-08-02 12:49 ` Jiri Kosina
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=87invjs6mu.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ville.syrjala@linux.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