All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Thierry <michel.thierry@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@gmail.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/kbl: Adding missing IS_KABYLAKE checks.
Date: Wed, 16 Mar 2016 14:31:10 +0000	[thread overview]
Message-ID: <56E96E2E.1040602@intel.com> (raw)
In-Reply-To: <87a8mjtwii.fsf@intel.com>

On 2/29/2016 2:35 PM, Jani Nikula wrote:
> On Fri, 26 Feb 2016, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
>> Hi Jani and Daniel,
>>
>> I believe I forgot to cc:stable on this one and this is missing on
>> most branches out there including Linus 4.5-r5.
>> Is there any chance to get this patch in for 4.5? without this i915 is
>> not working on KBL.
>
> Is the referenced commit by Michel also required?
>
>      Michel had found the main error first and his
>      fix had better details on the history and got
>      merged already:
>
>      commit 16fbc291cb87c7defcd13ad715d3e4af0d523e43
>      Author: Michel Thierry <michel.thierry@intel.com>
>      Date:   Wed Jan 6 12:08:36 2016 +0000
>
>          drm/i915/kbl: Enable PW1 and Misc I/O power wells
>
> If that's needed, what else is needed? Where does the rabbit hole end?
>
>> Good thing is that this platform is still protected by preliminary_hw_support.
>
> We do not backport cc: stable fixes for platforms that only have
> preliminary hw support.
>
> v4.5 is not released yet, and although towards the later -rc's the rules
> are pretty much the same as for stable kernels, I might consider
> cherry-picking kbl fixes that make platform enabling or early adoption
> easier.
>

Hi Jani,

Now that v4.5 has been released, would you consider _backporting_ these 
two patches to allow kbl to boot?

AFAIK, these are the only patches needed,
drm/i915/kbl: Enable PW1 and Misc I/O power wells
[https://cgit.freedesktop.org/drm-intel/commit/?id=16fbc291cb87c7defcd13ad715d3e4af0d523e43]
and
drm/i915/kbl: Adding missing IS_KABYLAKE checks
[https://cgit.freedesktop.org/drm-intel/commit/?id=8d7a1c4a579c4ecfe360044c24dc1fbf97096752]

Thanks,

-Michel

> BR,
> Jani.
>
>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-16 14:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  1:15 [PATCH 1/3] drm/i915/kbl: Adding missing IS_KABYLAKE checks Rodrigo Vivi
2016-01-07  1:15 ` [PATCH 2/3] drm/i915: Don't warn if the workaround list is empty part 2 Rodrigo Vivi
2016-01-08  0:49   ` Rodrigo Vivi
2016-01-07  1:15 ` [PATCH 3/3] drm/i915/kbl: Remove preliminary_hw_support protection from Kabylake Rodrigo Vivi
2016-01-07  9:30   ` Daniel Vetter
2016-01-07 16:14 ` [PATCH 1/3] drm/i915/kbl: Adding missing IS_KABYLAKE checks Michel Thierry
2016-01-08  0:32   ` Vivi, Rodrigo
2016-01-08  0:49   ` [PATCH] " Rodrigo Vivi
2016-02-26  0:23     ` Rodrigo Vivi
2016-02-29 14:35       ` Jani Nikula
2016-03-16 14:31         ` Michel Thierry [this message]
2016-03-16 15:15           ` Jani Nikula
2016-03-16 15:32             ` 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=56E96E2E.1040602@intel.com \
    --to=michel.thierry@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=rodrigo.vivi@gmail.com \
    --cc=rodrigo.vivi@intel.com \
    /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.