All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Filip Van Lunteren <filip.pinkfaun@outlook.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"perex@perex.cz" <perex@perex.cz>
Subject: Re: native DSD on PCI linux driver
Date: Tue, 03 Dec 2024 13:43:35 +0100	[thread overview]
Message-ID: <87y10xx7go.wl-tiwai@suse.de> (raw)
In-Reply-To: <871pypymm0.wl-tiwai@suse.de>

On Tue, 03 Dec 2024 13:31:03 +0100,
Takashi Iwai wrote:
> 
> On Tue, 26 Nov 2024 10:41:21 +0100,
> Filip Van Lunteren wrote:
> > 
> > 
> > Hello,
> > 
> > I am currently developing PCI audio output hardware and driver and want to
> > integrate native DSD playback. I am struggling to find documentation on this.
> > Is there DSD native support in ALSA? And how do I incorporate it? PCM is
> > already set up and works.
> 
> AFAIK, in the driver side, there is not much special; it assumes that
> DSD samples are passed over the standard PCM stream, and the driver
> uses special formats SNDRV_PCM_FORMAT_DSD_U8, *_U16 and *_U32 (with
> _LE and _BE suffix) for 8, 16 and 32bit, instead of the standard
> SNDRV_PCM_FORMAT_U8, *_S16, etc.  For those formats, the silence data
> is assumed to be 0x69, 0x6969, etc.

To be more exactly, the above statement is about PCM core.

Most of DSD stuff is found in USB audio driver, and if you need a DoP
support, the driver has to convert it manually.
(We may push it to PCM core, once when needed, but as currently it's 
required only by USB-audio, it's locally handled.)

Similarly, there is also bit-reversed transfer for some devices.

Both can be found in sound/usb/pcm.c.


HTH,

Takashi

      reply	other threads:[~2024-12-03 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AS4P189MB20372D46254D6425C820FC9C882F2@AS4P189MB2037.EURP189.PROD.OUTLOOK.COM>
2024-12-03 12:31 ` native DSD on PCI linux driver Takashi Iwai
2024-12-03 12:43   ` Takashi Iwai [this message]

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=87y10xx7go.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=filip.pinkfaun@outlook.com \
    --cc=perex@perex.cz \
    /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.