From: Darren Hart <dvhart@infradead.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
platform-driver-x86@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Petri Hodju <petrihodju@yahoo.com>,
Matthew Garrett <matthew.garrett@nebula.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [Patch v3] apple-gmux: lock iGP IO to protect from vgaarb changes
Date: Wed, 18 Mar 2015 20:46:18 -0700 [thread overview]
Message-ID: <20150319034618.GB22993@fury.dvhart.com> (raw)
In-Reply-To: <20150311223445.6af76f7c@neptune.home>
On Wed, Mar 11, 2015 at 10:34:45PM +0100, Bruno Prémont wrote:
> As GMUX depends on IO for iGP to be enabled and active, lock the IO at
> vgaarb level. This should prevent GPU driver for dGPU to disable IO for
> iGP while it tries to own legacy VGA IO.
>
> This fixes usage of backlight control combined with closed nvidia
> driver on some Apple dual-GPU (intel/nvidia) systems.
>
> On those systems loading nvidia driver disables intel IO decoding,
> disabling the gmux backlight controls as a side effect.
> Prior to commits moving boot_vga from (optional) efifb to less optional
> vgaarb this mis-behavior could be avoided by using right kernel config
> (efifb enabled but vgaarb disabled).
>
> This patch explicitly does not try to trigger vgaarb changes in order
> to avoid confusing already running graphics drivers. If IO has been
> mis-configured by vgaarb gmux will thus fail to probe.
> It is expected to load/probe gmux prior to graphics drivers.
>
> Fixes: ce027dac592c0ada241ce0f95ae65856828ac450 # nvidia interaction
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=86121
> Reported-by: Petri Hodju <petrihodju@yahoo.com>
> Tested-by: Petri Hodju <petrihodju@yahoo.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Matthew Garrett <matthew.garrett@nebula.com>
> Signed-off-by: Bruno Prémont <bonbons@linux-vserver.org>
> ---
> Resending v2 in the hope Darren won't hit quoted-printable.
> Also adding linux-pci on CC by Bjorn's request in bugzilla.
Much better, thanks. Queued.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-19 3:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 20:51 [Patch] apple-gmux: lock iGP IO to protect from vgaarb changes Bruno Prémont
2015-03-03 17:27 ` Darren Hart
2015-03-05 22:20 ` [Patch v2] " Bruno Prémont
2015-03-06 17:42 ` Darren Hart
2015-03-07 0:15 ` Bruno Prémont
2015-03-09 21:52 ` [Patch v2 resend] " Bruno Prémont
2015-03-09 22:11 ` Bjorn Helgaas
2015-03-11 21:34 ` [Patch v3] " Bruno Prémont
2015-03-19 3:46 ` Darren Hart [this message]
2015-05-26 19:10 ` Michael Marineau
2015-05-27 4:47 ` Darren Hart
2015-05-27 5:35 ` Michael Marineau
2015-05-27 6:13 ` Bruno Prémont
2015-05-27 6:41 ` Michael Marineau
2015-05-29 16:36 ` Darren Hart
2015-06-01 6:22 ` Bruno Prémont
2015-06-01 17:31 ` Darren Hart
2015-05-27 5:53 ` Bruno Prémont
2015-05-27 6:28 ` Michael Marineau
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=20150319034618.GB22993@fury.dvhart.com \
--to=dvhart@infradead.org \
--cc=bhelgaas@google.com \
--cc=bonbons@linux-vserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=petrihodju@yahoo.com \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox