Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sean Paul <seanpaul@chromium.org>
Cc: intel-gfx@lists.freedesktop.org, jglasgow@chromium.org
Subject: Re: [PATCH] drm/i915: Don't lock panel registers when downclocking
Date: Mon, 13 Feb 2012 17:39:49 +0100	[thread overview]
Message-ID: <20120213163949.GG5301@phenom.ffwll.local> (raw)
In-Reply-To: <CAOw6vbK8VGLNLmwTRVLTfMCm5y_UWNjA_2f9ggUt5pfyJnC9zQ@mail.gmail.com>

On Mon, Feb 13, 2012 at 10:13:02AM -0500, Sean Paul wrote:
> On Mon, Feb 13, 2012 at 5:08 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Feb 01, 2012 at 05:31:30PM -0500, Sean Paul wrote:
> >> This patch removes the locking from the downclock routines since we are no
> >> longer locking the registers at all. See ed10fca9 for the original commit
> >> changing this philosophy.
> >>
> >> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> >
> > I've thought this was due to paranoia because we don't trust our own code
> > and because we don't trust the bios to randomly lock this again. Without
> > any reasons to the contrary, I'll prefer to keep this.
> 
> Thanks for the explanation, Daniel, however I'd ask that you
> reconsider this patch.
> 
> The state coming into the downclock functions is unlocked and without
> this patch, the state coming out is locked. This causes at least one
> warning in the code from assert_panel_unlocked.

Ah, that's a pretty important thing missing from the commit message. I've
checked the code and we have indeed an issue there. Can you please:
- Extend your commit message to mention that you're actually hitting the
  assert_panel_unlocked assert (and how this happens). Maybe explain that
  you need lvds downclocking, which is disabled by default.
- Add an assert_panel_unlocked call instead of unlocking the panel in your
  patch (we do need to be paranoid about these things).

Then I think your patch is good to go into -next.

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-02-13 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:31 [PATCH] drm/i915: Don't lock panel registers when downclocking Sean Paul
2012-02-13 10:08 ` Daniel Vetter
2012-02-13 15:13   ` Sean Paul
2012-02-13 16:39     ` Daniel Vetter [this message]
2012-02-13 18:14       ` Sean Paul
2012-02-13 19:02         ` Jesse Barnes

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=20120213163949.GG5301@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jglasgow@chromium.org \
    --cc=seanpaul@chromium.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