From: Lukas Wunner <lukas@wunner.de>
To: jimqu <jimqu@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
alsa-devel@alsa-project.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] vgaswitchreoo: set audio client id in vgaswitchreoo enable function
Date: Mon, 16 Jul 2018 16:02:46 +0200 [thread overview]
Message-ID: <20180716140246.GA12334@wunner.de> (raw)
In-Reply-To: <8832b090-c399-ab88-8c56-4509a3413c44@amd.com>
On Sat, Jul 14, 2018 at 02:15:24PM +0800, jimqu wrote:
> ??? 2018/7/13 17:27, Lukas Wunner ??????:
> >On Fri, Jul 13, 2018 at 04:06:02PM +0800, Jim Qu wrote:
> >>On modern laptop, there are more and more platforms
> >>have two GPUs, and each of them maybe have audio codec
> >>for HDMP/DP output. For some dGPU which is no output,
> >>audio codec usually is disabled.
> >>
> >>In currect HDA audio driver, it will set all codec as
> >>VGA_SWITCHEROO_DIS, the audio which is binded to UMA
> >>will be suspended if user use debugfs to contorl power
> >>
> >>In HDA driver side, it is difficult to know which GPU
> >>the audio has binded to. So set the bound gpu pci dev
> >>to vgaswitchroo, the correct audio id will be set in
> >>vgaswitchreoo enable function.
> >>
> >>Signed-off-by: Jim Qu <Jim.Qu@amd.com>
> >The approach you've taken in this patch won't work if the HDA controller
> >is bound to a driver after both GPUs have already been bound to a driver
> >and the handler has already been registered.
> >
> >That's because vga_switcheroo_enable() is run when two GPUs have registered
> >as clients and the handler has also registered. If the HDA controller is
> >probed afterwards, its ID will be stuck at VGA_SWITCHEROO_UNKNOWN_ID.
>
> In genernic speaking, there are two cases , a. audio client is the third
> client. b. audio client is not the third client.
>
> if audio is third client. vga_switcheroo_ready() is true,
> vga_switcheroo_enable() can be called in audio client register fuction.
> if audio is not the third client, vga_switcheroo_enable() will be called in
> the second GFX client register.
> In vga_switcheroo_enable() , the first list loop will set two GPU clients'
> id, and the second list loop will select audio client, set id by its bound
> gpu pci dev.
No, if audio is the third client, vga_switcheroo_ready() is *not* true
because vgasr_priv.active is true. This is set to true once the two
GPUs and the handler have registered. If the audio device registers
afterwards, vga_switcheroo_enable() will already have been called.
It's never called twice because it sets vgasr_priv.active = true.
As a result, the audio device is stuck at VGA_SWITCHEROO_UNKNOWN_ID.
Thanks,
Lukas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-16 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 8:06 [PATCH 1/2] ALSA: HDA: use PCI_BASE_CLASS_DISPLAY to cover more display adapters Jim Qu
2018-07-13 8:06 ` [PATCH 2/2] vgaswitchreoo: set audio client id in vgaswitchreoo enable function Jim Qu
[not found] ` <1531469162-6472-2-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2018-07-13 8:46 ` [alsa-devel] " Takashi Iwai
[not found] ` <s5hmuuv8qvp.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
2018-07-13 15:25 ` jimqu
2018-07-13 16:38 ` Takashi Iwai
[not found] ` <s5hbmbbm6q9.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
2018-07-13 16:51 ` [alsa-devel] " jimqu
2018-07-13 9:27 ` Lukas Wunner
[not found] ` <20180713092742.GA4013-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2018-07-13 15:34 ` jimqu
2018-07-14 6:15 ` jimqu
2018-07-16 14:02 ` Lukas Wunner [this message]
[not found] ` <20180716140246.GA12334-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2018-07-16 14:45 ` jimqu
[not found] ` <1531469162-6472-1-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2018-07-13 8:31 ` [PATCH 1/2] ALSA: HDA: use PCI_BASE_CLASS_DISPLAY to cover more display adapters Lukas Wunner
2018-07-13 8:33 ` [alsa-devel] " Takashi Iwai
[not found] ` <s5ho9fb8rh9.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
2018-07-13 9:28 ` Qu, Jim
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=20180716140246.GA12334@wunner.de \
--to=lukas@wunner.de \
--cc=alexander.deucher@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jimqu@amd.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;
as well as URLs for NNTP newsgroup(s).