From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Pan Xiuli <xiuli.pan@linux.intel.com>,
alsa-devel@alsa-project.org, stable@vger.kernel.org
Subject: Re: Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree
Date: Mon, 26 Feb 2018 19:34:07 +0100 [thread overview]
Message-ID: <20180226183407.22335-1-k.marinushkin@gmail.com> (raw)
In-Reply-To: <E1eqGmV-0005Rk-Jt@debutante>
Hello Mark Brown, Pan Xiuli,
As far as I understand, the suggested commit *breaks* the functionality instead
of fixing it, and should not be applied. Please correct me if I am wrong.
1. The existing functionality works correctly, nothing to fix here.
Below is a comment from include/sound/soc-dai.h:77
~~~~
/*
* DAI hardware clock masters.
*
* This is wrt the codec, the inverse is true for the interface
* i.e. if the codec is clk and FRM master then the interface is
* clk and frame slave.
*/
#define SND_SOC_DAIFMT_CBM_CFM (1 << 12) /* codec clk & FRM master */
#define SND_SOC_DAIFMT_CBS_CFM (2 << 12) /* codec clk slave & FRM master */
#define SND_SOC_DAIFMT_CBM_CFS (3 << 12) /* codec clk master & frame slave */
#define SND_SOC_DAIFMT_CBS_CFS (4 << 12) /* codec clk & FRM slave */
~~~~
According to the comment, the existing functionality works correctly "WRT the
interface". The suggested commit doesn't fix the behaviour: instead, it reverts
the logic to "WRT the codec". But the existing implementation is also valid.
2. The suggested commit breaks the existing ASoC.
The existing functionality already works with several existing ASoC by
Intel. The suggested commit will break it for the following reason:
The ALSA topology mechanism loads the binary topology file into ASoC. The
suggested commit modifies the parser, but the binaries are already created for
the existing functionality. As a result, all existing binaries will be parsed
incorrectly.
3. The suggested commit should not go into stable.
For the reasons explained earlier, applying the suggested commit into stable
kernel will break the stable kernel.
As I am not in the mailing list, I will not be able to stop Greg K-H
<gregkh@linuxfoundation.org> when he will ask "If you, or anyone else, feels it
should not be added to the stable tree, please let <stable@vger.kernel.org> know
about it."
@Mark Brown could you please add me to the thread if such situation happens, so
that I could share my point for the stable patches.
Best Regards,
Kirill
next prev parent reply other threads:[~2018-02-26 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519336888-71831-1-git-send-email-xiuli.pan@linux.intel.com>
2018-02-26 11:17 ` Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree Mark Brown
2018-02-26 18:34 ` Kirill Marinushkin [this message]
2018-02-26 19:47 ` Mark Brown
2018-02-27 4:38 ` Kirill Marinushkin
2018-02-27 2:30 ` [alsa-devel] " Pierre-Louis Bossart
2018-02-27 4:50 ` Kirill Marinushkin
2018-02-27 10:38 ` Mark Brown
2018-02-27 15:13 ` Pierre-Louis Bossart
2018-02-27 15:57 ` Mark Brown
2018-02-28 6:22 ` Pierre-Louis Bossart
2018-03-12 16:14 ` Mark Brown
2018-03-12 23:29 ` [alsa-devel] " Pierre-Louis Bossart
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=20180226183407.22335-1-k.marinushkin@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiuli.pan@linux.intel.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