From: Jyri Sarha <jsarha@ti.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: hdmi-codec: modifying params in hw_params() callback
Date: Thu, 28 Feb 2019 14:54:29 +0200 [thread overview]
Message-ID: <421c1217-6ff6-6ca2-8169-db026284fb29@ti.com> (raw)
In-Reply-To: <20190228121516.swd3vweisgcxlvld@shell.armlinux.org.uk>
On 28/02/2019 14:15, Russell King - ARM Linux admin wrote:
> Hi all,
>
> While looking at hdmi-codec issues, I spotted this code:
>
> static int hdmi_codec_hw_params(struct snd_pcm_substream *substream,
> struct snd_pcm_hw_params *params,
> struct snd_soc_dai *dai)
> {
> ...
> if (params_width(params) > 24)
> params->msbits = 24;
>
> params->msbits is a parameter that is negotiated and refined by
> libasound, and is part of the ALSA constraint system. The "Writing an
> ALSA driver" documentation says about the hw_params callback:
>
> "This is called when the hardware parameter (``hw_params``) is set up
> by the application, that is, once when the buffer size, the period
> size, the format, etc. are defined for the pcm substream."
>
> which suggests we should only be reading the parameters, not writing
> to them.
>
> What's more is that the msbits is a parameter that is refined with
> userspace, so surely the above should be a declared constraint?
>
Certainly not a constraint. While HDMI can only pass up to 24-bit per
sample audio the most (or at least the two I have worked with) encoders
can take 32-bit wide (and probably wider) samples trough i2s. So the
system can play 32-bit samples, just the 4 LSB is ignored.
Actually there is very little difference between the case of playing
32-bit stereo audio with matching i2s bclk ratio, and playing 24-bit
stereo audio with 64-bit bclk ratio. Especially when the 4 LSB is anyway
ignored like in HDMI audio case.
> Digging a bit deeper, ASoC passes a private copy of the params to each
> codec - a copy is made, then fixups for TDM slots are applied, followed
> by any topology fixups by the DAI link (be_hw_params_fixup) before the
> codec driver's hw_params() callback is made. Afterwards, ASoC reads
> back the rate, channels and physical (memory) width and stores them
> in the codec's DAI structure. The msbits are not read.
>
> hdmi-codec also seems to do nothing with the msbits parameter other
> than the above code.
>
> So, all in all, it seems that the above code limiting msbits is
> redundant - nothing will read this modified value. Can we kill it?
>
It certainly looks that way, so yes. In any case struct
snd_soc_dai_driver .playback.sig_bits = 24 should be all that is needed.
Regards,
Jyri
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-28 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:15 hdmi-codec: modifying params in hw_params() callback Russell King - ARM Linux admin
2019-02-28 12:54 ` Jyri Sarha [this message]
2019-02-28 13:10 ` Russell King - ARM Linux admin
2019-02-28 14:35 ` Jyri Sarha
2019-02-28 14:39 ` Russell King - ARM Linux admin
2019-02-28 14:41 ` Jyri Sarha
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=421c1217-6ff6-6ca2-8169-db026284fb29@ti.com \
--to=jsarha@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.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