From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88493] No hdmi audio an agd5f 3.20-wip since consolidate audio_get_pin() functions
Date: Mon, 02 Feb 2015 21:50:43 +0000 [thread overview]
Message-ID: <bug-88493-502-2UGCEdtnLQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88493-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88493
--- Comment #10 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Alex Deucher from comment #1)
> Are you sure that's the right commit? I don't see any functional change.
> It just switches a direct function call to a function pointer.
I played a bit more - trying to see if there was any real change or maybe some
unlucky h/w timing/order issue.
There is a functional change, I guess seeded in a preceding commit.
Testing with debugging like -
diff --git a/drivers/gpu/drm/radeon/dce6_afmt.c
b/drivers/gpu/drm/radeon/dce6_afmt.c
index 96f298c..266f32a 100644
--- a/drivers/gpu/drm/radeon/dce6_afmt.c
+++ b/drivers/gpu/drm/radeon/dce6_afmt.c
@@ -75,6 +75,7 @@ struct r600_audio_pin *dce6_audio_get_pin(struct
radeon_device *rdev)
{
int i;
+ DRM_ERROR("[ADF] in dce6_audio_get_pin\n");
dce6_afmt_get_connected_pins(rdev);
for (i = 0; i < rdev->audio.num_pins; i++) {
On the bad commit there is no output after doing
xrandr --output HDMI-0 --auto
on the commit before there is.
On the bad I do get the output with a second use of xrandr.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2140 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-02 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 12:28 [Bug 88493] No hdmi audio an agd5f 3.20-wip since consolidate audio_get_pin() functions bugzilla-daemon
2015-01-20 14:30 ` bugzilla-daemon
2015-01-20 17:14 ` bugzilla-daemon
2015-01-20 19:38 ` bugzilla-daemon
2015-01-21 0:10 ` bugzilla-daemon
2015-01-21 11:02 ` bugzilla-daemon
2015-01-21 12:23 ` bugzilla-daemon
2015-01-21 12:45 ` bugzilla-daemon
2015-01-21 14:45 ` bugzilla-daemon
2015-01-21 14:55 ` bugzilla-daemon
2015-02-02 21:50 ` bugzilla-daemon [this message]
2015-02-27 16:21 ` bugzilla-daemon
2015-02-27 23:48 ` bugzilla-daemon
2015-03-31 15:49 ` bugzilla-daemon
2015-03-31 19:22 ` bugzilla-daemon
2015-04-07 14:23 ` bugzilla-daemon
2015-04-07 20:06 ` bugzilla-daemon
2015-04-08 14:17 ` bugzilla-daemon
2015-07-30 11:38 ` 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-88493-502-2UGCEdtnLQ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox