From: Steve Lee <SteveS.Lee@maximintegrated.com>
To: Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"rf@opensource.wolfsonmicro.com" <rf@opensource.wolfsonmicro.com>,
"shumingf@realtek.com" <shumingf@realtek.com>,
"srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"dmurphy@ti.com" <dmurphy@ti.com>,
"jack.yu@realtek.com" <jack.yu@realtek.com>,
"nuno.sa@analog.com" <nuno.sa@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"ryan.lee.maxim@gmail.com" <ryan.lee.maxim@gmail.com>,
"steves.lee.maxim@gmail.com" <steves.lee.maxim@gmail.com>
Subject: RE: [EXTERNAL] Re: [PATCH] ASoC: max98390: Add support change dsm param name
Date: Mon, 9 Aug 2021 00:57:48 +0000 [thread overview]
Message-ID: <CO1PR11MB5089212BFBF03F82AE41E34C92F69@CO1PR11MB5089.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210806110301.GW26252@sirena.org.uk>
On Fri, Aug 06, 2021 at 05:08:34PM +0900, Steve Lee wrote:
>
> > ret = request_firmware(&fw, filename, component->dev);
> > if (ret) {
> > - ret = request_firmware(&fw, "dsm_param.bin", component-
> >dev);
> > + ret = request_firmware(&fw, "dsmparam.bin", component-
> >dev);
>
> This will break anything using dsm_param.bin as the default - why make the
> change?
I'd like to make that as same name with other using SoF project line.
This originally production default is "dsm_param_%s_%s.bin with vendor and product name".
next prev parent reply other threads:[~2021-08-09 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 8:08 [PATCH] ASoC: max98390: Add support change dsm param name Steve Lee
2021-08-06 11:03 ` Mark Brown
2021-08-09 0:57 ` Steve Lee [this message]
2021-08-09 12:21 ` [EXTERNAL] " Mark Brown
2021-08-09 13:55 ` Steve Lee
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=CO1PR11MB5089212BFBF03F82AE41E34C92F69@CO1PR11MB5089.namprd11.prod.outlook.com \
--to=steves.lee@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=dmurphy@ti.com \
--cc=geert@linux-m68k.org \
--cc=jack.yu@realtek.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=perex@perex.cz \
--cc=rf@opensource.wolfsonmicro.com \
--cc=ryan.lee.maxim@gmail.com \
--cc=shumingf@realtek.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=steves.lee.maxim@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).