From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Moise Gergaud <moise.gergaud@st.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, broonie@kernel.org,
arnaud.pouliquen@st.com, lgirdwood@gmail.com
Subject: Re: [PATCH 1/3] ALSA: pcm: add IEC958 channel status update
Date: Wed, 2 Dec 2015 19:00:36 +0000 [thread overview]
Message-ID: <20151202190036.GD8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1449066126-19431-2-git-send-email-moise.gergaud@st.com>
On Wed, Dec 02, 2015 at 03:22:04PM +0100, Moise Gergaud wrote:
> Add a helper to update only the IEC958 channel status sampling freq and
> word length parameters from an ALSA snd_pcm_runtime structure, taking
> account of the sample rate and sample size.
>
> Signed-off-by: Moise Gergaud <moise.gergaud@st.com>
> Acked-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
NAK.
> diff --git a/include/sound/pcm_iec958.h b/include/sound/pcm_iec958.h
> index 0eed397..0c84c69 100644
> --- a/include/sound/pcm_iec958.h
> +++ b/include/sound/pcm_iec958.h
> @@ -3,7 +3,24 @@
>
> #include <linux/types.h>
>
> +#ifdef CONFIG_SND_PCM_IEC958
> int snd_pcm_create_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> - size_t len);
> + size_t len);
> +
> +int snd_pcm_update_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> + size_t len);
> +#else
> +int snd_pcm_create_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> + size_t len)
> +{
> + return len;
> +}
> +
> +int snd_pcm_update_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> + size_t len)
> +{
> + return len;
> +}
Firstly, this is dangerous. If you don't have anything defined here,
then the channel status ends up being undefined.
The intention here is that if you're a user of this, then select the
config symbol. That makes providing stubs totally unnecessary and
removes this problem.
> +#endif
>
> #endif
> diff --git a/sound/core/pcm_iec958.c b/sound/core/pcm_iec958.c
> index 36b2d7a..abe3967 100644
> --- a/sound/core/pcm_iec958.c
> +++ b/sound/core/pcm_iec958.c
> @@ -11,67 +11,72 @@
> #include <sound/pcm.h>
> #include <sound/pcm_iec958.h>
>
> -/**
> - * snd_pcm_create_iec958_consumer - create consumer format IEC958 channel status
> +/*
> + * snd_pcm_update_iec958_consumer - update consumer format IEC958 channel status
> * @runtime: pcm runtime structure with ->rate filled in
> * @cs: channel status buffer, at least four bytes
> * @len: length of channel status buffer
> *
> - * Create the consumer format channel status data in @cs of maximum size
> - * @len corresponding to the parameters of the PCM runtime @runtime.
> - *
> - * Drivers may wish to tweak the contents of the buffer after creation.
> + * Update sampling frequency and word length parameters of the consumer format
> + * channel status data in @cs of maximum size @len.
> + * Values correspond to the rate and format parameters of the PCM runtime
> + * @runtime.
> *
> * Returns: length of buffer, or negative error code if something failed.
> */
> -int snd_pcm_create_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> - size_t len)
> +int snd_pcm_update_iec958_consumer(struct snd_pcm_runtime *runtime, u8 *cs,
> + size_t len)
> {
> - unsigned int fs, ws;
> -
> if (len < 4)
> return -EINVAL;
>
> + cs[3] &= ~IEC958_AES3_CON_FS;
> +
> switch (runtime->rate) {
> + case 22050:
> + cs[3] |= IEC958_AES3_CON_FS_22050;
> + break;
> case 32000:
> - fs = IEC958_AES3_CON_FS_32000;
> + cs[3] |= IEC958_AES3_CON_FS_32000;
> break;
> case 44100:
> - fs = IEC958_AES3_CON_FS_44100;
> + cs[3] |= IEC958_AES3_CON_FS_44100;
> break;
> case 48000:
> - fs = IEC958_AES3_CON_FS_48000;
> + cs[3] |= IEC958_AES3_CON_FS_48000;
> break;
> case 88200:
> - fs = IEC958_AES3_CON_FS_88200;
> + cs[3] |= IEC958_AES3_CON_FS_88200;
> break;
> case 96000:
> - fs = IEC958_AES3_CON_FS_96000;
> + cs[3] |= IEC958_AES3_CON_FS_96000;
> break;
> case 176400:
> - fs = IEC958_AES3_CON_FS_176400;
> + cs[3] |= IEC958_AES3_CON_FS_176400;
> break;
> case 192000:
> - fs = IEC958_AES3_CON_FS_192000;
> + cs[3] |= IEC958_AES3_CON_FS_192000;
> break;
Again, I'm not happy with this change. The intention here is that we
validate all arguments before we change anything. This breaks that
principle.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-12-02 19:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:22 [PATCH 0/3] ASoC: sti: correction for HBRA support Moise Gergaud
2015-12-02 14:22 ` [PATCH 1/3] ALSA: pcm: add IEC958 channel status update Moise Gergaud
2015-12-02 14:32 ` Takashi Iwai
2015-12-02 19:00 ` Russell King - ARM Linux [this message]
2015-12-03 10:58 ` Moise Gergaud
2015-12-03 11:13 ` Russell King - ARM Linux
2015-12-03 12:03 ` Takashi Iwai
2015-12-07 8:46 ` Moise Gergaud
2015-12-07 9:51 ` Takashi Iwai
2015-12-08 14:30 ` Moise Gergaud
2015-12-08 14:47 ` Russell King - ARM Linux
2015-12-02 19:01 ` Russell King - ARM Linux
2015-12-02 14:22 ` [PATCH 2/3] ASoC: sti: use pcm iec958 channel status helper Moise Gergaud
2015-12-02 14:50 ` Takashi Iwai
2015-12-02 14:22 ` [PATCH 3/3] ASoC: sti: correction for HBRA (High Bit Rate Audio) support Moise Gergaud
2015-12-09 8:27 ` [PATCH 0/3] ASoC: sti: correction for HBRA support Moise Gergaud
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=20151202190036.GD8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=moise.gergaud@st.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 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).