From: Daniel Vetter <daniel@ffwll.ch>
To: James Cloos <cloos@jhcloos.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: HDMI Audio screwed up w/ recent kernels
Date: Tue, 27 Dec 2016 19:20:25 +0100 [thread overview]
Message-ID: <20161227182025.GA347@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <m3d1gdjnpk.fsf@jhcloos.com>
On Tue, Dec 27, 2016 at 12:17:43PM -0500, James Cloos wrote:
> >>>>> "DV" == Daniel Vetter <daniel@ffwll.ch> writes:
>
> DV> amdgpu doesn't yet support hdmi audio.
>
> Then why does it support the amdgpu.audio command line option, and why
> does booting an amdgpu kernel with amdgpu.audio=1 sound the same as
> booting a radeon kernel w/ radeon.audio=1?
Hm, I thought there was in issue there still. Anyway, was just a drive-by
comment, please ignore me ;-)
-Daniel
>
> In linux/drivers/gpu/drm/amd/amdgpu:
>
> :; grep -l audio_enable *.c|xargs
> dce_v10_0.c dce_v11_0.c dce_v6_0.c dce_v8_0.c
>
> :; grep -l amdgpu_audio *.c |xargs
> amdgpu_connectors.c amdgpu_display.c amdgpu_drv.c atombios_encoders.c
> dce_v10_0.c dce_v11_0.c dce_v6_0.c dce_v8_0.c
>
> -JimC
> --
> James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-27 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 0:49 HDMI Audio screwed up w/ recent kernels James Cloos
2016-12-27 9:47 ` Daniel Vetter
2016-12-27 17:17 ` James Cloos
2016-12-27 18:20 ` Daniel Vetter [this message]
2016-12-27 18:32 ` Bridgman, John
2016-12-28 19:43 ` James Cloos
2016-12-31 5:36 ` Alex Deucher
2016-12-31 7:55 ` James Cloos
2017-01-02 16:04 ` Alex Deucher
2017-01-02 17:11 ` James Cloos
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=20161227182025.GA347@dvetter-linux.ger.corp.intel.com \
--to=daniel@ffwll.ch \
--cc=cloos@jhcloos.com \
--cc=dri-devel@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.