From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Menzel <pmenzel+intel-gfx@molgen.mpg.de>,
Jose Souza <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [v2] drm/i915/fbdev: Enable late fbdev initial configuration
Date: Mon, 23 Apr 2018 17:05:18 +0300 [thread overview]
Message-ID: <874lk2dnmp.fsf@intel.com> (raw)
In-Reply-To: <7e5ca905-2380-d3eb-23df-ccaca77d5a0a@molgen.mpg.de>
On Fri, 20 Apr 2018, Paul Menzel <pmenzel+intel-gfx@molgen.mpg.de> wrote:
> Dear Jose,
>
>
> On 04/19/18 01:41, Souza, Jose wrote:
>> If the initial fbdev configuration(intel_fbdev_initial_config()) runs and
>
> Nit: Space before (.
>
>> there still no sink connected it will cause
>> drm_fb_helper_initial_config() to return 0 as no error happened(but
>> internally the return is -EAGAIN).
>
> Nit: Space before (.
>
>> Because no framebuffer was allocated, when a sink is connected
>> intel_fbdev_output_poll_changed() will not execute
>> drm_fb_helper_hotplug_event() that would trigger another try to do the
>> initial fbdev configuration.
>>
>> So here allowing drm_fb_helper_hotplug_event() to be executed when there
>> is not frambebuffer allocated and fbdev was not setup yet.
>
> s/not/no/
> s/setup/set up/
>
>> This issue also happens when a MST DP sink is connected since boot, as
>> the MST topology is discovered in parallel if intel_fbdev_initial_config()
>> is executed before the first sink MST is discovered it will cause this
>> same issue.
>>
>> This is a follow up patch of
>
> follow-up
>
>> https://patchwork.freedesktop.org/patch/196089/
>>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104158
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104425
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
>> ---
>>
>> Changes from v1:
>> - not creating a dump framebuffer anymore, instead just allowing
>> drm_fb_helper_hotplug_event() to execute when fbdev is not setup yet.
>
> s/setup/set up/
>
>> drivers/gpu/drm/i915/intel_fbdev.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
>> index 7d41d139341b..e9e02b58b7be 100644
>> --- a/drivers/gpu/drm/i915/intel_fbdev.c
>> +++ b/drivers/gpu/drm/i915/intel_fbdev.c
>> @@ -807,7 +807,7 @@ void intel_fbdev_output_poll_changed(struct drm_device *dev)
>> return;
>>
>> intel_fbdev_sync(ifbdev);
>> - if (ifbdev->vma)
>> + if (ifbdev->vma || ifbdev->helper.deferred_setup)
>> drm_fb_helper_hotplug_event(&ifbdev->helper);
>> }
>>
>
> Tested-by: Paul Menzel <pmenzel@molgen.mpg.de>
Also from the bug,
Tested-by: frederik <frederik.schwan@linux.com> # 4.15.17
Tested-by: Ian Pilcher <arequipeno@gmail.com>
>
>
> Kind regards,
>
> Paul
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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:[~2018-04-23 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 23:41 [PATCH v2] drm/i915/fbdev: Enable late fbdev initial configuration José Roberto de Souza
2018-04-19 0:13 ` ✓ Fi.CI.BAT: success for drm/i915/fbdev: Enable late fbdev initial configuration (rev4) Patchwork
2018-04-19 2:08 ` ✓ Fi.CI.IGT: " Patchwork
2018-04-19 12:50 ` [PATCH v2] drm/i915/fbdev: Enable late fbdev initial configuration Jani Nikula
2018-04-19 20:12 ` Souza, Jose
2018-04-20 9:33 ` [v2] " Paul Menzel
2018-04-23 14:05 ` Jani Nikula [this message]
2018-04-24 8:47 ` [PATCH v2] " Chris Wilson
2018-04-24 14:50 ` 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=874lk2dnmp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=pmenzel+intel-gfx@molgen.mpg.de \
--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