From: Lukas Wunner <lukas@wunner.de>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML nouveau <nouveau@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Nouveau] [PATCH v4] vga_switcheroo: Add helper for deferred probing
Date: Sat, 21 May 2016 16:08:47 +0200 [thread overview]
Message-ID: <20160521140847.GA4523@wunner.de> (raw)
In-Reply-To: <CACvgo505G8+Gq_o0FszYi74kJFqFV-=1Y2-Ed9PDRRDX1kaSXw@mail.gmail.com>
Hi Emil,
On Fri, May 20, 2016 at 12:41:04AM +0100, Emil Velikov wrote:
> On 19 May 2016 at 15:39, Lukas Wunner <lukas@wunner.de> wrote:
> > +bool vga_switcheroo_client_probe_defer(struct pci_dev *pdev)
> > +{
> > + if ((pdev->class >> 8) == PCI_CLASS_DISPLAY_VGA) {
> Not sure if we want/need this, yet at least. This changes behaviour
> which is not what refactoring patches should be doing, right ? if
> needed it ought to be a separate patch, imho.
Well, the commit message doesn't claim "no functional change", does it?
Daniel Vetter explicitly wanted the ability to use the helper in
vga_switcheroo audio clients, and those shouldn't run the apple-gmux
test. I think it makes sense to enclose it in the above-quoted if-block
*now* even though it's not needed. Once someone adds a check for an
audio client, chances are they'll forget to add this if-block.
> Furthermore on nouveau and AMD (iirc) front, some dual-gpu/optimus
> systems use PCI_CLASS_DISPLAY_3D. So if we add DISPLAY_VGA perhaps we
> should also check for DISPLAY_3D ?
Fair enough, I've changed it to match PCI_BASE_CLASS_DISPLAY
and sent it out as v5 a few minutes ago.
Thanks,
Lukas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-21 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:39 [PATCH v4] vga_switcheroo: Add helper for deferred probing Lukas Wunner
2016-05-19 16:08 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-05-20 13:49 ` Ville Syrjälä
[not found] ` <35e4cc1e5c711fa30c3081dc628ce672a0fea276.1463642956.git.lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2016-05-19 23:41 ` [PATCH v4] " Emil Velikov
2016-05-21 14:08 ` Lukas Wunner [this message]
2016-05-23 10:15 ` [Intel-gfx] [Nouveau] " 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=20160521140847.GA4523@wunner.de \
--to=lukas@wunner.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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 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.