From: Anssi Hannula <anssi.hannula@iki.fi>
To: Raymond Yau <superquad.vortex2@gmail.com>,
John Ettedgui <john.ettedgui@gmail.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>, Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [pulseaudio-discuss] Issue with multiple hdmi codecs in radeonhd, hacked to work
Date: Sun, 08 Dec 2013 02:59:01 +0200 [thread overview]
Message-ID: <52A3C455.5090207@iki.fi> (raw)
In-Reply-To: <CAN8ccibrFmQa4rPcP6gqt7h1MpMQ310b8y2zcbN-h_rtN_6vvw@mail.gmail.com>
07.12.2013 09:18, Raymond Yau kirjoitti:
> I just changed my RadeonHD 4670 for a 7870, and now when I type
> "aplay -l" I get many HDMI codecs instead of just one like for the
> previous
>
>
> Do your card specification support Discrete Digital Multi-Point Audio
> (DDMA) /?/
>
> DDMA enables Radeon™HD 7700-7900 Series GPUs with the ability to output
> multiple and independent audio streams simultaneously through digital
> interfaces that support audio, such as DisplayPort and HDMI®. Each audio
> stream can be multi-channel (up to 8 channels)
AFAIK yes, the multi-hdmi-device AMD cards are "DDMA".
[...]
> monitor_present 1
> eld_valid 1
> monitor_name
> connection_type HDMI
> eld_version [0x2] CEA-861D or below
> edid_version [0x0] no CEA EDID Timing Extension block present
> manufacture_id 0x0
> product_id 0x0
> port_id 0x0
> support_hdcp 0
> support_ai 0
> audio_sync_delay 0
> speakers [0x5f] FL/FR LFE FC RL/RR RC RLC/RRC
> sad_count 6
> sad0_coding_type [0x1] LPCM
> sad0_channels 8
> sad0_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000
> sad0_bits [0xe0000] 16 20 24
> sad1_coding_type [0x2] AC-3
> sad1_channels 6
> sad1_rates [0xe0] 32000 44100 48000
> sad1_max_bitrate 640000
> sad2_coding_type [0x7] DTS
> sad2_channels 6
> sad2_rates [0x6c0] 44100 48000 88200 96000
> sad2_max_bitrate 1536000
> sad3_coding_type [0xa] E-AC-3/DD+ (Dolby Digital Plus)
> sad3_channels 8
> sad3_rates [0xc0] 44100 48000
> sad4_coding_type [0xb] DTS-HD
> sad4_channels 8
> sad4_rates [0x1ec0] 44100 48000 88200 96000 176400 192000
> sad5_coding_type [0xc] MLP (Dolby TrueHD)
> sad5_channels 8
> sad5_rates [0x1ec0] 44100 48000 88200 96000 176400 192000
> monitor_present 1
> eld_valid 0
> monitor_present 1
> eld_valid 0
> monitor_present 1
> eld_valid 0
> monitor_present 1
> eld_valid 0
> monitor_present 1
> eld_valid 0
>
> e.g. HDMI status message in function hdmi_present_sense in patch_hdmi.c
>
> need to find out why eld->monitor_present was set for all six complexes
>
> the value return by function atihdmi_pin_get_eld since it change
> eld->eld_valid to false when it is negative
When CONFIG_SND_DEBUG_VERBOSE is enabled, hdmi_present_sense() prints
the actual hw Presence_Detect/ELD_Valid before eld->eld_valid is
overridden to 0 (and hdmi_intrinsic_event() prints the hot plug event
values).
Alex, do you have information regarding why "Presence detect" (aka
monitor_present above) seems to be set for all HDMI pins in the response
of Pin Sense 0xF09 verb (or if it is even expected), and/or if we should
use alternate means of getting jack status?
CONFIG_SND_DEBUG_VERBOSE log might also be interesting, I wonder if
eld_valid is also 1 for every pin or not (before ALSA forces 0). Also, I
wonder if all monitor_present fields are 1 with fglrx driver as well, or
when all displays are unplugged...
[...]
--
Anssi Hannula
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-12-08 0:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ3TwYRYGR5Z2m1XSQ9QOp3ffe9sb2C_znsVUeBpARySZ7KbMQ@mail.gmail.com>
[not found] ` <CAN8ccia9KA4fyU06LE3+DMPcj9w62Z8P-BvjR3-aA2Q9TWcC-A@mail.gmail.com>
[not found] ` <CAJ3TwYQOiV2DFbVHagJ+O+tSbcvmNUTrZng1C8Tgooz8SrdPgg@mail.gmail.com>
[not found] ` <CAJ3TwYQSYtv6qdCiTi9MHBoEnxqitXbSVgxq-8R+z7E0LQyhpg@mail.gmail.com>
2013-12-05 7:24 ` Issue with multiple hdmi codecs in radeonhd, hacked to work Raymond Yau
2013-12-05 7:40 ` John Ettedgui
2013-12-05 8:22 ` Raymond Yau
2013-12-05 8:38 ` John Ettedgui
2013-12-05 8:48 ` John Ettedgui
2013-12-05 12:20 ` Raymond Yau
2013-12-05 12:20 ` Raymond Yau
[not found] ` <CAJ3TwYRheSya2Y7y-e82=-HPv5j26n7SR-L1GeC=CPfrOKHpbA@mail.gmail.com>
[not found] ` <CAN8ccibrFmQa4rPcP6gqt7h1MpMQ310b8y2zcbN-h_rtN_6vvw@mail.gmail.com>
2013-12-08 0:59 ` Anssi Hannula [this message]
2013-12-09 15:24 ` [pulseaudio-discuss] " Deucher, Alexander
[not found] ` <CAJ3TwYQ_1BTmPafS-_BJWWNp1VSXA5K_e0vVHMipGrkdOjGuwA@mail.gmail.com>
2013-12-08 8:21 ` John Ettedgui
2013-12-08 13:56 ` Raymond Yau
2013-12-08 14:45 ` John Ettedgui
[not found] ` <CAN8cciZTuP8Y-nvv8ecJZBoJZBgsucb2p0sd-2dmyMWGxDgifQ@mail.gmail.com>
[not found] ` <CAJ3TwYQukvyyXvuOtquv3UmnToK3CwM1zNxrq6kr4QE2Sshx2A@mail.gmail.com>
2013-12-09 4:50 ` Raymond Yau
2013-12-09 6:01 ` [pulseaudio-discuss] " Anssi Hannula
2013-12-09 6:08 ` Anssi Hannula
2013-12-09 9:15 ` John Ettedgui
2013-12-10 5:39 ` Raymond Yau
2013-12-10 8:01 ` John Ettedgui
2013-12-10 13:54 ` Raymond Yau
2013-12-10 14:18 ` John Ettedgui
2013-12-10 16:22 ` Anssi Hannula
2013-12-09 9:25 ` Takashi Iwai
2013-12-09 15:12 ` [pulseaudio-discuss] " Deucher, Alexander
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=52A3C455.5090207@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=alexander.deucher@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=john.ettedgui@gmail.com \
--cc=superquad.vortex2@gmail.com \
--cc=tiwai@suse.de \
/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.