From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Derek [方德義]" <derek.fang@realtek.com>,
"bard.liao@intel.com" <bard.liao@intel.com>,
"Shuming [范書銘]" <shumingf@realtek.com>,
"Flove(HsinFu)" <flove@realtek.com>,
"pierre-louis.bossart@intel.com" <pierre-louis.bossart@intel.com>
Subject: Re: [PATCH v2 2/3] ASoC: rt715: remove kcontrols which no longer be used
Date: Fri, 16 Apr 2021 10:36:44 -0500 [thread overview]
Message-ID: <43219280-2647-184d-eb73-7bc5e561d6a3@linux.intel.com> (raw)
In-Reply-To: <20210416130738.GB5560@sirena.org.uk>
On 4/16/21 8:07 AM, Mark Brown wrote:
> On Thu, Apr 15, 2021 at 04:35:14PM -0500, Pierre-Louis Bossart wrote:
>
>> Was there any sustained objection to this change? Mark and Jaroslav?
>
>> I would really like to fix the UCM files so that the mute and volume are
>> handled at the codec driver level, and not at the SOF level as it's
>> currently the case.
>
> Well, you seemed to be objecting because it broke the UCM files and Jack
> didn't reply so as far as I understand it it'll break userspace.
I guess my wording was unclear.
No, I was not objecting, just clarifying that there will be a UCM change
but that's needed anyways.
next prev parent reply other threads:[~2021-04-16 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 6:54 [PATCH v2 2/3] ASoC: rt715: remove kcontrols which no longer be used Jack Yu
2021-03-30 17:09 ` Mark Brown
2021-03-30 17:23 ` Jaroslav Kysela
2021-03-30 19:26 ` Pierre-Louis Bossart
2021-04-15 21:35 ` Pierre-Louis Bossart
2021-04-16 13:07 ` Mark Brown
2021-04-16 15:36 ` Pierre-Louis Bossart [this message]
2021-04-16 13:40 ` Jaroslav Kysela
2021-04-16 15:58 ` Pierre-Louis Bossart
2021-04-16 18:34 ` 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=43219280-2647-184d-eb73-7bc5e561d6a3@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@intel.com \
--cc=shumingf@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.