public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexey Zaytsev <alexey.zaytsev@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Rodrigo Vivi <rodrigo.vivi@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@gmail.com>,
	stable <stable@vger.kernel.org>
Subject: Re: Linux 3.8-rc2
Date: Sun, 6 Jan 2013 21:55:11 +0100	[thread overview]
Message-ID: <20130106205511.GR5737@phenom.ffwll.local> (raw)
In-Reply-To: <CA+55aFw5hnByqQHhsOYgc14DHTejHqmWV=fW2pm4LuzF6UxwCQ@mail.gmail.com>

On Thu, Jan 03, 2013 at 03:18:54PM -0800, Linus Torvalds wrote:
> On Thu, Jan 3, 2013 at 3:12 PM, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
> >
> > Chris: The patch does not seem to have any effect on the problem.
> >
> > Peter: I've attached the dmesgs, as well as the diff between the
> > interesting parts. The patch does not seem to make any difference
> > there.
> 
> Alexey, what happens if you just avoid the divide-by-zero? There might
> be other complications downstream, but something like the attached
> patch should at least avoid doing the "divide-by-clock" when clock is
> zero..

Yeah, that looks like the better duct-tape. For context, we're in the
middle of the long road to fastboot, i.e. taking over the output setup
done by the bios to avoid a costly modeset at boot-up (at least for
somewhat sane firmware which doesn't use legacy vga mode any more but the
native resolution of the panel). But since we don't yet read out the full
hw state some assumptions are now broken in our code, so we need to catch
them.

Chris has a more complete patch covering all the other
generations/code-paths accessing crtc->mode.clock (but lost you from cc).
I'll forward his patch asap (still digging through the mail flood from
vacation).

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2013-01-06 20:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  3:36 Linux 3.8-rc2 Linus Torvalds
2013-01-03 21:09 ` Alexey Zaytsev
2013-01-03 21:32   ` Linus Torvalds
2013-01-03 22:06     ` Peter Ujfalusi
2013-01-03 22:45     ` Chris Wilson
2013-01-03 23:12       ` Alexey Zaytsev
2013-01-03 23:18         ` Linus Torvalds
2013-01-03 23:40           ` Alexey Zaytsev
2013-01-04 11:39             ` [PATCH] drm/i915: Treat crtc->mode.clock == 0 as disabled Chris Wilson
2013-01-04 14:58               ` Alexey Zaytsev
2013-01-06 20:56               ` Daniel Vetter
2013-01-07 10:11                 ` Chris Wilson
2013-01-07 16:40                   ` Daniel Vetter
2013-01-06 20:55           ` Daniel Vetter [this message]
2013-01-03 23:56       ` Linux 3.8-rc2 Shuah Khan

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=20130106205511.GR5737@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=alexey.zaytsev@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.com \
    --cc=rodrigo.vivi@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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