From: Hans de Goede <hdegoede@redhat.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Enable fastboot by default on Skylake and newer
Date: Tue, 29 Jan 2019 10:46:46 +0100 [thread overview]
Message-ID: <deadd69e-45bf-e8f1-599a-d225c490ca20@redhat.com> (raw)
In-Reply-To: <425e3258-b507-1d6c-d85a-1d9855e40ddb@redhat.com>
Hi,
On 25-01-19 09:36, Hans de Goede wrote:
> Hi Rodrigo and Maarten,
>
> On 24-01-19 23:20, Rodrigo Vivi wrote:
>> On Thu, Jan 24, 2019 at 02:01:14PM +0100, Maarten Lankhorst wrote:
>>> From: Hans de Goede <hdegoede@redhat.com>
>>>
>>> We really want to have fastboot enabled by default to avoid an ugly
>>> modeset during boot.
>>>
>>> Rather then enabling it everywhere, lets start with enabling it on
>>> Skylake and newer.
>>>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>
>>
>> I believe at this point you both addressed all of my concerns.
>> And CI is happy. Let's give a try ;)
>
> Great, thank you.
>
> On IRC Maarten asked me about if we should also enable this for
> VLV/CHV. As you may know, as a spare time/weekend project, I've been
> working on making Linux support Bay and Cherry Trail based hardware,
> better. As such I've about 40 different devices with these SoCs and
> I've tested fastboot=1 on all of them. fastboot=1 not only works on
> all of them, on 2 devices the display goes black when we have
> fastboot=0 for some reason which I've been unable to figure out.
> These 2 devices do survive a full-modeset just fine after the initial
> one ?
>
> So my response to Maarten was, yes we should enable fastboot=1 by
> default on VLV/CHV too and I plan to submit a follow-up patch for
> that once we have agreement on this patch.
>
> Maarten suggested to just go for enabling it on gen7+ instead of
> the current gen9+.
>
> I personally tend towards merging this patch with your
> Reviewed-by + doing a follow-up patch for just VLV/CHV, but
> Maarten prefers doing the gen7+ solution, what is your take on this?
I've gone ahead and pushed this patch to dinq now. I will post a
follow-up patch to also enable fastboot on VLV/CHV.
Then once this mix has seen enough testing out there (and assuming the
testing goes well) then we can try to change to enabling fastboot
by default on gen7+.
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-29 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 13:01 [PATCH] drm/i915: Enable fastboot by default on Skylake and newer Maarten Lankhorst
2019-01-24 13:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Enable fastboot by default on Skylake and newer (rev2) Patchwork
2019-01-24 13:35 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-24 16:27 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-24 22:20 ` [PATCH] drm/i915: Enable fastboot by default on Skylake and newer Rodrigo Vivi
2019-01-25 8:36 ` Hans de Goede
2019-01-29 9:46 ` Hans de Goede [this message]
2019-01-29 14:02 ` Joonas Lahtinen
2019-01-29 15:14 ` Hans de Goede
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=deadd69e-45bf-e8f1-599a-d225c490ca20@redhat.com \
--to=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox