From: Jesse Barnes <jesse.barnes@intel.com>
To: dedekind1@gmail.com
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: v3.12 does not work on ByT-I
Date: Fri, 8 Nov 2013 10:38:14 -0800 [thread overview]
Message-ID: <20131108103814.34156b3e@jbarnes-desktop> (raw)
In-Reply-To: <1383922411.2722.298.camel@sauron.fi.intel.com>
On Fri, 8 Nov 2013 16:53:31 +0200
Artem Bityutskiy <dedekind1@gmail.com> wrote:
> Thanks Jesse for you answer, but it brought more questions.
>
> On Thu, 2013-11-07 at 08:04 -0800, Jesse Barnes wrote:
> > Hm, I wonder if this bug is also related to the backlight stuff Jani
> > recently pushed fixes for.
>
> OK.
>
> > It looks like you have an eDP panel here,
>
> No, we do not have it at all.
>
> > but if for some reason it got bounced between two CRTCs due to bad
> > detection on one, it could cause a blank screen issue.
>
> OK, not sure I understand what you mean, but yes, blank screen is
> something which we observe without your patch.
Ok if you do not have eDP then the panel power sequencing stuff I saw
in the log is being done unnecessarily. Ville has some patches to
better detect eDP panels:
"drm/i915: Give names to the VBT child device type bits" on the mailing
list is the thread.
If you don't have eDP then the patches from Jani I pointed you at
shouldn't help. Another one to make sure you have is:
ommit f60711666bcab6df2c6c91d851e07ed54088453c
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Tue Oct 1 10:41:38 2013 -0700
i915/vlv: untangle integrated clock source handling v4
I don't know if that ended up in 3.12.x or not...
Jesse
next prev parent reply other threads:[~2013-11-08 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 12:21 v3.12 does not work on ByT-I Bityutskiy, Artem
2013-11-07 16:04 ` Jesse Barnes
2013-11-08 14:53 ` Artem Bityutskiy
2013-11-08 18:38 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 12:23 Artem Bityutskiy
2013-11-07 12:30 ` Daniel Vetter
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=20131108103814.34156b3e@jbarnes-desktop \
--to=jesse.barnes@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dedekind1@gmail.com \
--cc=intel-gfx@lists.freedesktop.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