From: Matthias Reichl <hias@horus.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: hdmi-codec: Fix broken channel map reporting
Date: Sun, 10 Sep 2023 14:14:34 +0200 [thread overview]
Message-ID: <ZP2zKg88n4MaD53z@camel3.lan> (raw)
In-Reply-To: <ZPxo8qKMDkmBqGxw@finisterre.sirena.org.uk>
On Sat, Sep 09, 2023 at 01:45:38PM +0100, Mark Brown wrote:
> On Sat, Sep 09, 2023 at 01:46:33PM +0200, Matthias Reichl wrote:
> > Commit 4e0871333661 ("ASoC: hdmi-codec: fix channel info for
> > compressed formats") accidentally changed hcp->chmap_idx from
> > ca_id, the CEA channel allocation ID, to idx, the index to
> > the table of channel mappings ordered by preference.
> >
> > This resulted in wrong channel maps being reported to userspace,
> > eg for 5.1 "FL,FR,LFE,FC" was reported instead of the expected
> > "FL,FR,LFE,FC,RL,RR":
>
> Presumably this will cause a regression for people using compressed
> formats - isn't the fix here to make this behaviour conditional on if
> the format is compressed?
This change won't affect passthrough, the values of the HDMI audio
infoframe are stored separately, in hdmi_codec_params.cea.
chmap_idx in hdmi_codec_priv is only used by the get PCM channel map
control - which userspace shouldn't use in the non-PCM case.
Before the "fix channel info for compressed formats" change the control
would always return a matching channel map, i.e. "FL FR" in the 2-channel
case, regardless if PCM or non-PCM was used.
When using high bitrate compressed streams, which are passed through as
8ch (containing 4 consecutive frames), this leads to a problem though as
the sink might not announce support for 8 speakers (eg on TVs with 2 speakers
and "virtual surround") and thus finding a channel map would fail.
The "fix channel info" patch addressed this issue by only searching for a
channel map in the PCM case.
In the non-PCM case ca_id is set to 0 which means "FL, FR" - CTA doesn't
have a separate value for "n/a" but specifies that the channel allocation
only applies to PCM streams with more than 2 channels. Although the spec
says the value doesn't apply to non-PCM some TVs seem to look at it and
refuse to output HBR (TrueHD etc) if it's set to something other than 0.
My plan was to return the exact same info via the channel map control
as we set in the info frame but unfortunately I messed up and accidentally
used the wrong value which this patch tries to rectify.
I'm not really sure though if that's the best (or even proper) way for
the channel map control to behave in the non-PCM case - it'll either return
"FL, FR" or "FL, FR, UNKNOWN, UNKNOWN, UNKNOWN, UNKNOWN, UNKNOWN, UNKNOWN"
with this patch.
An alternative would be to set chmap_idx to HDMI_CODEC_CHMAP_IDX_UNKNOWN
in the non-PCM case so the channel map control will return UNKNOWN for
all channels. i.e. use this code instead:
if (pcm_audio)
hcp->chmap_idx = ca_id;
else
hcp->chmap_idx = HDMI_CODEC_CHMAP_IDX_UNKNOWN;
Any input on that topic is highly appreciated.
so long & thanks,
Hias
next prev parent reply other threads:[~2023-09-10 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 11:46 [PATCH] ASoC: hdmi-codec: Fix broken channel map reporting Matthias Reichl
2023-09-09 12:45 ` Mark Brown
2023-09-10 12:14 ` Matthias Reichl [this message]
2023-09-13 19:23 ` Mark Brown
2023-09-26 15:29 ` Mark Brown
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=ZP2zKg88n4MaD53z@camel3.lan \
--to=hias@horus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=tiwai@suse.com \
/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