All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	Alexey Orishko <alexey.orishko@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	stable@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>,
	Francois Tigeot <ftigeot@wolfpond.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Unlock panel even when LVDS is disabled
Date: Tue, 02 Dec 2014 15:21:45 +0200	[thread overview]
Message-ID: <87k32anq52.fsf@intel.com> (raw)
In-Reply-To: <20141202130002.GR32117@phenom.ffwll.local>

On Tue, 02 Dec 2014, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Dec 02, 2014 at 01:43:59PM +0100, Alexey Orishko wrote:
>> On Mon, Dec 1, 2014 at 5:56 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> > Otherwise we'll have backtraces in assert_panel_unlocked because the
>> > BIOS locks the register. In the reporter's case this regression was
>> > introduced in
>> >
>> > commit c31407a3672aaebb4acddf90944a114fa5c8af7b
>> > Author: Chris Wilson <chris@chris-wilson.co.uk>
>> > Date:   Thu Oct 18 21:07:01 2012 +0100
>> >
>> >     drm/i915: Add no-lvds quirk for Supermicro X7SPA-H
>> >
>> > Alexey, please test this patch.
>> >
>> 
>> Thank you for the patch.
>> I've tested this patch on the failed system (BIOS ver.1.0) with 3.17.4
>> kernel and it looks good.
>> - Do you need dmesg log?
>
> Nope.
>
>> - Could this patch be merged into 3.18 kernel?
>
> Jani, can you please pick this one up as a regression fix?

Pushed to drm-intel-fixes, thanks for the patch and testing.

BR,
Jani.


>
>> I've also checked that everything still ok on other mobos with BIOS
>> ver.1.0c and 1.2a.
>> 
>> One more question slightly out off topic:
>> - could I use i915 driver with other Intel Atom CPUs, such as D2550
>> and Avoton C2550?
>
> Anything newer than what you have right now likely means gma500 (which is
> horrible), unless it's a baytrail. Buyer beware, please triple-check that
> it works before placing an order. Since I have no clue about marketing
> names I'll refrain from a recommendation (too many ppl burned already).
> -Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

-- 
Jani Nikula, Intel Open Source Technology Center

  parent reply	other threads:[~2014-12-02 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 22:14 i915 driver failure Alexey Orishko
2014-12-01  9:10 ` Daniel Vetter
2014-12-01 10:56   ` Alexey Orishko
2014-12-01 16:56     ` [PATCH] drm/i915: Unlock panel even when LVDS is disabled Daniel Vetter
2014-12-01 18:38       ` Alexey Orishko
2014-12-02 12:43       ` Alexey Orishko
2014-12-02 13:00         ` Daniel Vetter
2014-12-02 13:12           ` Francois Tigeot
2014-12-02 13:21           ` Jani Nikula [this message]
2014-12-03  0:53       ` shuang.he
2014-12-29  8:00       ` 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=87k32anq52.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=alexey.orishko@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=ftigeot@wolfpond.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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.