From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
Mika Kahola <mika.kahola@intel.com>,
bruno.pagani@ens-lyon.org,
Daniel J Blueman <daniel.blueman@gmail.com>,
Joseph Yasi <joe.yasi@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things
Date: Tue, 1 Nov 2016 14:41:37 +0200 [thread overview]
Message-ID: <20161101124137.GT4617@intel.com> (raw)
In-Reply-To: <1477991271.2230.40.camel@tiscali.nl>
On Tue, Nov 01, 2016 at 10:07:51AM +0100, Paul Bolle wrote:
> On Tue, 2016-11-01 at 09:57 +0100, Maarten Lankhorst wrote:
> > Otherwise looks sane, I have a similar patch in my tree. I didn't
> > submit it yet but the fix was similar. Except for the
> > dev_cdclk stuff.
> >
> > With the last dev_cdclk assignment removed:
> >
> > Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> So I've been running this patch for a few days now. First I tested it
> on top of v4.8.4. Now I'm running it on top of v4.8.5.
>
> My current v4.8.5 boot saw this new (for me) *ERROR*, twice:
> � ��<3>[43483.521341] [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk change
> <3>[108639.090776] [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk change
>
> Related or a coincidence?
Not directly related. That's actually a more serious problem we really
need to figure out. I already tried to fix it but apparently I failed.
--
Ville Syrj�l�
Intel OTC
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: bruno.pagani@ens-lyon.org,
Daniel J Blueman <daniel.blueman@gmail.com>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
Joseph Yasi <joe.yasi@gmail.com>
Subject: Re: [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things
Date: Tue, 1 Nov 2016 14:41:37 +0200 [thread overview]
Message-ID: <20161101124137.GT4617@intel.com> (raw)
In-Reply-To: <1477991271.2230.40.camel@tiscali.nl>
On Tue, Nov 01, 2016 at 10:07:51AM +0100, Paul Bolle wrote:
> On Tue, 2016-11-01 at 09:57 +0100, Maarten Lankhorst wrote:
> > Otherwise looks sane, I have a similar patch in my tree. I didn't
> > submit it yet but the fix was similar. Except for the
> > dev_cdclk stuff.
> >
> > With the last dev_cdclk assignment removed:
> >
> > Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> So I've been running this patch for a few days now. First I tested it
> on top of v4.8.4. Now I'm running it on top of v4.8.5.
>
> My current v4.8.5 boot saw this new (for me) *ERROR*, twice:
> <3>[43483.521341] [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk change
> <3>[108639.090776] [drm:skl_set_cdclk [i915]] *ERROR* failed to inform PCU about cdclk change
>
> Related or a coincidence?
Not directly related. That's actually a more serious problem we really
need to figure out. I already tried to fix it but apparently I failed.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-01 12:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 16:59 [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things ville.syrjala
2016-10-28 16:59 ` ville.syrjala
2016-10-28 17:15 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-10-28 21:05 ` [PATCH] " Paul Bolle
2016-10-28 21:05 ` Paul Bolle
2016-10-28 21:30 ` Ville Syrjälä
2016-10-28 21:30 ` Ville Syrjälä
2016-10-28 21:38 ` Paul Bolle
2016-10-28 21:38 ` Paul Bolle
2016-10-28 22:01 ` Ville Syrjälä
2016-10-28 22:01 ` Ville Syrjälä
2016-11-01 8:57 ` Maarten Lankhorst
2016-11-01 8:57 ` Maarten Lankhorst
2016-11-01 9:07 ` Paul Bolle
2016-11-01 12:41 ` Ville Syrjälä [this message]
2016-11-01 12:41 ` Ville Syrjälä
2016-11-01 12:40 ` Ville Syrjälä
2016-11-01 12:40 ` Ville Syrjälä
2016-11-01 12:53 ` Ville Syrjälä
2016-11-01 12:53 ` Ville Syrjälä
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=20161101124137.GT4617@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=bruno.pagani@ens-lyon.org \
--cc=daniel.blueman@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe.yasi@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mika.kahola@intel.com \
--cc=pebolle@tiscali.nl \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.