All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	kernel@collabora.com
Subject: Re: [PATCH] drm/i915: only disable default vga device
Date: Tue, 18 May 2021 12:09:56 +0100	[thread overview]
Message-ID: <CACvgo53H7GAjN_aFsCBOw+xtVbjcbR1q-U3vdgjT1KUPKoMkkg@mail.gmail.com> (raw)
In-Reply-To: <YKKmsbvTZBwCUiRu@intel.com>

Hi Ville,

On Mon, 17 May 2021 at 18:24, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
>
> On Sun, May 16, 2021 at 06:14:32PM +0100, Emil Velikov wrote:
> > From: Vivek Das Mohapatra <vivek@collabora.com>
> >
> > This patch is to do with seamless handover, eg when the sequence is
> > bootloader → plymouth → desktop.
> >
> > It switches the vga arbiter from the "other" GPU to the default one
> > (intel in this case), so the driver can issue some io().
>
> I don't understand what this commit message is trying to say.
>
Bunch of context is lost due to the patch age, so I'm not 100% sure of
the actual hardware setup where this occurs.
Does the following make sense?

Currently on dual GPU systems, we do not get seamless handover as the
output flickers during the transition bootloader -> plymouth ->
desktop.
This happens as a result of switching (via the VGA arbiter) from the
"other" GPU back to the default i915 one and issuing io() commands.

-Emil

WARNING: multiple messages have this Message-ID (diff)
From: Emil Velikov <emil.l.velikov@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	kernel@collabora.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: only disable default vga device
Date: Tue, 18 May 2021 12:09:56 +0100	[thread overview]
Message-ID: <CACvgo53H7GAjN_aFsCBOw+xtVbjcbR1q-U3vdgjT1KUPKoMkkg@mail.gmail.com> (raw)
In-Reply-To: <YKKmsbvTZBwCUiRu@intel.com>

Hi Ville,

On Mon, 17 May 2021 at 18:24, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
>
> On Sun, May 16, 2021 at 06:14:32PM +0100, Emil Velikov wrote:
> > From: Vivek Das Mohapatra <vivek@collabora.com>
> >
> > This patch is to do with seamless handover, eg when the sequence is
> > bootloader → plymouth → desktop.
> >
> > It switches the vga arbiter from the "other" GPU to the default one
> > (intel in this case), so the driver can issue some io().
>
> I don't understand what this commit message is trying to say.
>
Bunch of context is lost due to the patch age, so I'm not 100% sure of
the actual hardware setup where this occurs.
Does the following make sense?

Currently on dual GPU systems, we do not get seamless handover as the
output flickers during the transition bootloader -> plymouth ->
desktop.
This happens as a result of switching (via the VGA arbiter) from the
"other" GPU back to the default i915 one and issuing io() commands.

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

  reply	other threads:[~2021-05-18 11:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 17:14 [PATCH] drm/i915: only disable default vga device Emil Velikov
2021-05-16 17:14 ` [Intel-gfx] " Emil Velikov
2021-05-17 10:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-05-17 11:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-17 16:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-05-17 17:24 ` [PATCH] " Ville Syrjälä
2021-05-17 17:24   ` [Intel-gfx] " Ville Syrjälä
2021-05-18 11:09   ` Emil Velikov [this message]
2021-05-18 11:09     ` Emil Velikov
2021-05-18 11:17     ` Ville Syrjälä
2021-05-18 11:17       ` [Intel-gfx] " Ville Syrjälä
2021-05-18 12:39       ` Emil Velikov
2021-05-18 12:39         ` [Intel-gfx] " Emil Velikov
2021-05-26 16:21       ` Emil Velikov
2021-05-26 16:21         ` [Intel-gfx] " Emil Velikov
2021-06-04 13:47         ` Emil Velikov
2021-06-04 13:47           ` [Intel-gfx] " Emil Velikov
2021-06-04 14:08           ` Ville Syrjälä
2021-06-04 14:08             ` [Intel-gfx] " Ville Syrjälä
2021-06-04 15:53             ` Emil Velikov
2021-06-04 15:53               ` [Intel-gfx] " Emil Velikov

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=CACvgo53H7GAjN_aFsCBOw+xtVbjcbR1q-U3vdgjT1KUPKoMkkg@mail.gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kernel@collabora.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=ville.syrjala@linux.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.