Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jim Qu <Jim.Qu@amd.com>, tiwai@suse.com
Cc: alexander.deucher@amd.com, alsa-devel@alsa-project.org,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [V3] vga_switcheroo: set audio client id according to bound GPU id
Date: Tue, 17 Jul 2018 10:38:58 +0200	[thread overview]
Message-ID: <20180717083858.GA29241@wunner.de> (raw)
In-Reply-To: <1531815650-9786-1-git-send-email-Jim.Qu@amd.com>

On Tue, Jul 17, 2018 at 04:20:50PM +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 vga_switcheroo.
> 
> if the audio client is not the third registration, audio
> id will set in vga_switcheroo enable function. if the
> audio client is the last registration when vga_switcheroo
> _ready() get true, we should get audio client id from bound
> GPU directly.
> 
> Signed-off-by: Jim Qu <Jim.Qu@amd.com>

Reviewed-by: Lukas Wunner <lukas@wunner.de>

@Takashi, any preference which tree to merge this through?
sound or drm-misc, either way would seem fine to me.  I think
there's going to be one final drm-misc pull sent to Dave this
week, after that it's 4.20.

Thanks,

Lukas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-17  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  8:20 [V3] vga_switcheroo: set audio client id according to bound GPU id Jim Qu
2018-07-17  8:38 ` Lukas Wunner [this message]
     [not found]   ` <20180717083858.GA29241-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2018-07-17  8:52     ` Takashi Iwai
2018-07-17  8:56       ` jimqu
     [not found]         ` <4fcfa367-4387-7b08-cf29-85b9322da371-5C7GfCeVMHo@public.gmane.org>
2018-07-17  9:22           ` Takashi Iwai

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=20180717083858.GA29241@wunner.de \
    --to=lukas@wunner.de \
    --cc=Jim.Qu@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tiwai@suse.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