All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199493] no audio over HDMI with amdgpu.dc=1 (on R9 380X)
Date: Sat, 19 May 2018 20:46:24 +0000	[thread overview]
Message-ID: <bug-199493-2300-MpkEvaCcuh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199493-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=199493

--- Comment #4 from Andy Furniss (adf.lists@gmail.com) ---
I build my own kernels, usually using agd5f testing branches.

Currently I get the warnings and no sound with dc=1.

dc=0 never worked with this card + my old TV, though it did work with an HDMI
monitor I once tried.

dc=1 worked for me ever since it was available, until the regression in
December.

I can currently get sound and loose the warnings, by reverting the commits
mentioned in my FDO bug. I still have to work around the alsa bug, which I do
by using it via jack.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-05-19 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 15:26 [Bug 199493] New: no audio over HDMI with amdgpu.dc=1 (on R9 380X) bugzilla-daemon
2018-04-25 16:05 ` [Bug 199493] " bugzilla-daemon
2018-05-19  9:08 ` bugzilla-daemon
2018-05-19 19:25 ` bugzilla-daemon
2018-05-19 20:46 ` bugzilla-daemon [this message]
2018-05-20 10:22 ` bugzilla-daemon
2018-05-28 10:46 ` bugzilla-daemon

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=bug-199493-2300-MpkEvaCcuh@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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.