linux-kernel - Re: [PATCH v2 3/4] ASoC: qdsp6: q6afe-dai: Update max rate for slim and tdm dais

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5h7e75v7en.wl-tiwai@suse.de>
Date:   Thu, 22 Aug 2019 12:09:04 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     broonie@...nel.org, spapothi@...eaurora.org,
        bgoswami@...eaurora.org, plai@...eaurora.org,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        lgirdwood@...il.com
Subject: Re: [PATCH v2 3/4] ASoC: qdsp6: q6afe-dai: Update max rate for slim and tdm dais

On Thu, 22 Aug 2019 11:56:52 +0200,
Srinivas Kandagatla wrote:
> 
> QDSP supports up to 384000 rates on SLIM dais and 352800 rate on TDM dais.
> Add this missing rates.
> 
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
> ---
>  sound/soc/qcom/qdsp6/q6afe-dai.c | 92 +++++++++++---------------------
>  1 file changed, 32 insertions(+), 60 deletions(-)
> 
> diff --git a/sound/soc/qcom/qdsp6/q6afe-dai.c b/sound/soc/qcom/qdsp6/q6afe-dai.c
> index c1a7624eaf17..ae2baefdb6e2 100644
> --- a/sound/soc/qcom/qdsp6/q6afe-dai.c
> +++ b/sound/soc/qcom/qdsp6/q6afe-dai.c
> @@ -18,14 +18,14 @@
>  			.stream_name = pre" TDM"#num" Playback",	\
>  			.rates = SNDRV_PCM_RATE_8000 | SNDRV_PCM_RATE_16000 |\
>  				SNDRV_PCM_RATE_32000 | SNDRV_PCM_RATE_48000 |\
> -				SNDRV_PCM_RATE_176400,			\
> +				SNDRV_PCM_RATE_176400 | SNDRV_PCM_RATE_352800,\

This will support a lot more than advertised, e.g. it contains 64000Hz
or 22050Hz.  Is this supposed?  If yes, mention it clearly in the
changelog, too.


thanks,

Takashi