Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Andrej Falout <andrej@falout.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Direct Stream Digital (DSD/DST, One Bit Audio) HDMI	pass-trough
Date: Wed, 15 Oct 2014 11:41:58 +0200	[thread overview]
Message-ID: <543E4166.7050704@ladisch.de> (raw)
In-Reply-To: <CAGzU1+ERCK+nA2F9tXdR18ZQU=RJ1cUwzF3hRkDTHgc1sGd33A@mail.gmail.com>

Andrej Falout wrote:
> On Wed, Oct 15, 2014 at 3:43 AM, Pierre-Louis Bossart wrote:
>> On 10/13/14, 7:49 PM, Andrej Falout wrote:
>>> What are you basing your assessment that "HDMI controllers typically
>>> don't support DSD in the PC space"? I looked, but could not find any
>>> evidence for this.
>>
>> I am basing my judgement on first-hand experience with silicon.
>
> Me too :) Absolutely every HDMI related chip I examined specs for and
> tested, including the cheapest of the cheap ones made as HDMI repeaters for
> splitters and audio extractors, supported DSD stream passing (Both up and
> down stream), just as they did all other audio bitstreams.

Because they just need to copy the packets from the input to the output.

> Can you please point out a specification or other document that say
> otherwise?

For PCs, all HDMI outputs are handled with HDA controllers.  The HDA
specification does not mention DSD.  AMD's HDA verb documentation has
the following list of audio formats codes:
0: reserved
1: LPCM
2: AC-3
3: MPEG1 (Layers 1 and 2)
4: MP3 (MPEG1 Layer 3)
5: MPEG2 (Multichannel)
6: AAC
7: DTS
8: ATRAC
9: Reserved
10: Dolby Digital +
11: DTS-HD
12: MAT/MLP (Dolby True HD)
13: Reserved
14: WMA Pro

Would DSD be one of the reserved ones?

> As you say, these are rather straightforward to implement

... if one bothers to implement it.

> Same specification also described DSD stream setup, which is is
> essence exactly the same, just uses the different identifiers.

So the hardware needs some mechanism to output these identifiers.

>> HDMI only requires 48kHz 2ch really.
>
> Even the HDMI version 1 requires "8 channel LPCM, 192 kHz, 24-bit
> audio capability": http://en.wikipedia.org/wiki/HDMI#Version_comparison

That page lists the version where a feature was introduced; these are
not requirements.

The HDMI specification says:
| If an HDMI Source supports any HDMI audio transmission, then it shall
| support 2 channel L-PCM ..., with either 32kHz, 44.1kHz or 48kHz
| sampling rate and a sample size of 16 bits or more.  [...]
| An HDMI Sink that is capable of accepting any audio format is required
| to accept two channel ... L-PCM audio at sample rates of 32kHz,
| 44.1kHz, and 48kHz.


Regards,
Clemens

  reply	other threads:[~2014-10-15  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11  6:33 Direct Stream Digital (DSD/DST, One Bit Audio) HDMI pass-trough Andrej Falout
2014-10-13 22:56 ` Pierre-Louis Bossart
2014-10-14  0:49   ` Andrej Falout
2014-10-14 14:43     ` Pierre-Louis Bossart
2014-10-15  3:30       ` Andrej Falout
2014-10-15  9:41         ` Clemens Ladisch [this message]
2014-10-15 13:38         ` Pierre-Louis Bossart
2014-10-19 16:50         ` Anssi Hannula

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=543E4166.7050704@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=andrej@falout.org \
    --cc=pierre-louis.bossart@linux.intel.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