From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Dave Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge
Date: Mon, 29 Aug 2016 18:08:39 +0300 [thread overview]
Message-ID: <874m63ipe0.fsf@intel.com> (raw)
In-Reply-To: <20160829133241.l2txb2rpnahlfufb@redhat.com>
On Mon, 29 Aug 2016, Andrea Arcangeli <aarcange@redhat.com> wrote:
> On Mon, Aug 29, 2016 at 10:24:38AM +0300, Jani Nikula wrote:
>> If it's an Iybridge, there's no low vswing, and that explanation is
>> false. You can verify by trying i915.edp_vswing=1 or i915.edp_vswing=2
>> on an unpatched kernel.
>
> What I should look for when trying those two settings? Will they
> successfully fix my problem with intel_backlight with upstream 4.8-rc?
>
> I thought it had to be the same issue as on skylake as I get the
> backlight flikering at low frequency but getting brighter and darker
> in a cycle lasting a few seconds and I thought there couldn't be too
> many other random bugs that ends up with the same side effect.
Your Ivybridge does not have low voltage swing *and* low voltage swing
has nothing to do with the backlight. The regressing commit may be the
same for you, but the failure mode appears to be completely different.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-29 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 15:28 [PATCH 0/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge Andrea Arcangeli
2016-08-28 15:28 ` [PATCH 1/1] " Andrea Arcangeli
2016-08-29 7:24 ` Jani Nikula
2016-08-29 13:32 ` Andrea Arcangeli
2016-08-29 15:08 ` Jani Nikula [this message]
2016-08-29 18:48 ` Andrea Arcangeli
2016-08-30 6:54 ` Martin van Es
2016-08-30 8:13 ` Jani Nikula
2016-08-30 9:13 ` Martin van Es
2016-08-30 7:25 ` Jani Nikula
2016-09-06 9:20 ` Ville Syrjälä
2016-09-06 10:56 ` Ville Syrjälä
2016-09-06 18:40 ` Ville Syrjälä
2016-09-08 10:04 ` Martin van Es
2016-09-08 10:18 ` Ville Syrjälä
2016-09-08 11:09 ` Martin van Es
2016-09-08 13:53 ` Andrea Arcangeli
2016-09-14 9:40 ` [PATCH 0/1] " Jani Nikula
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=874m63ipe0.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--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 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.