All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Jurgen Kramer <gtmkramer@xs4all.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] add native DSD support for XMOS based DACs.
Date: Fri, 05 Sep 2014 12:29:06 +0200	[thread overview]
Message-ID: <54099072.3040202@ladisch.de> (raw)
In-Reply-To: <1409910794.2959.1.camel@xs4all.nl>

Jurgen Kramer wrote:
> On Fri, 2014-09-05 at 11:36 +0200, Clemens Ladisch wrote:
>> Jurgen Kramer wrote:
>>> Add quirk for XMOS based DACs for native DSD playback support using the new DSD_U32_LE sample
>>> format. Works for all DAC vendors which use XMOS as idVendor. E.g. iFi Audio
>>> with their micro iDSD and nano iDSD.
>>>
>>> +++ b/sound/usb/quirks.c
>>> +	/* XMOS based DACs, e.g. iFi Audio micro/nano iDSD */
>>> +	if (le16_to_cpu(chip->dev->descriptor.idVendor) == 0x20b1) {
>>> +		switch (fp->altsetting) {
>>> +		case 2:
>>> +			return SNDRV_PCM_FMTBIT_DSD_U32_LE;
>>
>> Can you confirm that all XMOS devices ever built will have DSD on that
>> alternate setting?
>
> No, I can not. Most newer implementations will use alt setting 2 for
> native DSD support.

But it's possible to have other XMOS-based devices that use multiple
alternate settings for PCM.

> My first version also used idProduct to only target iFi devices. If
> this is required, I'll rework my patch.

I guess there isn't any property of the descriptors to distinguish DoP
from PCM?  How does the generic Windows driver know which alternate
settings are DoP?


Regards,
Clemens

  reply	other threads:[~2014-09-05 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  8:49 [PATCH] add native DSD support for XMOS based DACs Jurgen Kramer
2014-09-05  9:36 ` Clemens Ladisch
2014-09-05  9:53   ` Jurgen Kramer
2014-09-05 10:29     ` Clemens Ladisch [this message]
2014-09-05 11:01       ` Jurgen Kramer

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=54099072.3040202@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=gtmkramer@xs4all.nl \
    /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.