From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: DigitalDreamtime <clive.messer@digitaldreamtime.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: Add rate defines for 352k8 and 384k
Date: Tue, 7 Jun 2016 13:26:31 +0100 [thread overview]
Message-ID: <20160607122631.GO20422@localhost.localdomain> (raw)
In-Reply-To: <1465137301-21042-1-git-send-email-clive.messer@digitaldreamtime.co.uk>
On Sun, Jun 05, 2016 at 03:35:01PM +0100, DigitalDreamtime wrote:
> Add SNDRV_PCM_RATE_352800 and SNDRV_PCM_RATE_384000 defines to pcm.h,
> for 352k8 and 384k sample rates.
>
> Add SNDRV_PCM_RATE_8000_384000 define to pcm.h.
>
> Update rates list in pcm_native.c.
>
> Yes, we can use CONTINUOUS/KNOT and constraints, to support the x8
> sample rates, but having the defines requires less code in drivers.
> Many more DAC chips are now supporting the x8 44k1/48k multiples.
> >From a high-res viewpoint, the DXD standard is 352k8, 24 bit.
> That alone should justify the addition of a define for it.
>
> Signed-off-by: DigitalDreamtime <clive.messer@digitaldreamtime.co.uk>
> ---
Certainly looks like these rates are going to become pretty
widely used from our side so for what is worth:
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
I am sure Brian would weight in on the side of this one as
well but he is on holiday this week.
Thanks,
Charles
next prev parent reply other threads:[~2016-06-07 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 14:35 [PATCH] ALSA: Add rate defines for 352k8 and 384k DigitalDreamtime
2016-06-05 15:24 ` Clive Messer
2016-06-07 12:26 ` Charles Keepax [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-06 12:19 DigitalDreamtime
2016-06-06 12:59 ` Takashi Iwai
2016-06-06 17:07 ` Clive Messer
2016-06-06 20:29 ` Takashi Iwai
2016-06-06 21:22 ` Clive Messer
2016-06-06 21:58 ` Takashi Iwai
2016-06-06 23:00 ` Clive Messer
2016-06-07 9:27 ` Takashi Iwai
2016-06-06 17:16 ` Clive Messer
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=20160607122631.GO20422@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clive.messer@digitaldreamtime.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).