From: Lars-Peter Clausen <lars@metafoo.de>
To: Takashi Iwai <tiwai@suse.de>, Brian Austin <brian.austin@cirrus.com>
Cc: alsa-devel@alsa-project.org, charles.keepax@cirrus.com,
paul.handrigan@cirrus.com
Subject: Re: [PATCH] ALSA: core: Add 384kHz Support
Date: Wed, 27 Jan 2016 17:55:40 +0100 [thread overview]
Message-ID: <56A8F68C.7040805@metafoo.de> (raw)
In-Reply-To: <s5hsi1j6mxe.wl-tiwai@suse.de>
On 01/27/2016 04:51 PM, Takashi Iwai wrote:
> On Wed, 27 Jan 2016 16:02:35 +0100,
> Brian Austin wrote:
>>
>> On Wed, 27 Jan 2016, Takashi Iwai wrote:
>>
>>>> So we stay at SNDRV_PCM_RATE_192000 always for sample rate defines?
>>>> And everything else is just covered with SNDRV_PCM_RATE_KNOT?
>>>
>>> Depends. If a new sample rate is (or will be) demanded by many
>>> drivers, it's worth to add it, of course, as it would simplify the
>>> code.
>>>
>>> That's why I mentioned "why" is most important information; you need
>>> to convince others about the necessity of this change, after all.
>>> Then you see that "because I-wanna-it" doesn't sound convincing
>>> enough, right?
>>>
>>>
>>> Takashi
>>>
>> I really, really, really want it :)
>>
>> I understand. Going forward, from our perspective, 384 and
>> other high sample rates are going to be defaults for devices as the market
>> is moving that way. I just wanted to make it easier to use those instead
>> of doing all the contraint coding.
>
> Yeah that's the reason I could *guess*, but it wasn't mentioned.
>
>> Now my understanding on the KNOT define
>> may be wrong. I can add the other rates to this, but for now just wanted
>> to add one we use currently.
>>
>> Does that make sense?
>
> Just resubmit the patch with mo' better advertisement :)
For symmetry reasons maybe also include the matching 44.1kHz based rate.
Unless you think that is not going to be a thing.
next prev parent reply other threads:[~2016-01-27 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:53 [PATCH] ALSA: core: Add 384kHz Support brian.austin
2016-01-27 13:59 ` Clemens Ladisch
2016-01-27 14:01 ` Takashi Iwai
2016-01-27 14:11 ` Brian Austin
2016-01-27 14:16 ` Brian Austin
2016-01-27 14:36 ` Takashi Iwai
2016-01-27 15:02 ` Brian Austin
2016-01-27 15:51 ` Takashi Iwai
2016-01-27 16:55 ` Lars-Peter Clausen [this message]
2016-01-27 17:44 ` Charles Keepax
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=56A8F68C.7040805@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=charles.keepax@cirrus.com \
--cc=paul.handrigan@cirrus.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.