From: "Ding, Shenghao" <shenghao-ding@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: "andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"13916275206@139.com" <13916275206@139.com>,
"perex@perex.cz" <perex@perex.cz>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"Xu, Baojun" <baojun.xu@ti.com>, "Lu, Kevin(AE)" <k-lu@ti.com>
Subject: RE: Re: [PATCH v1] ASoC: tas2781: Optimize calibration to avoid full device reboot after calibration
Date: Fri, 31 Jul 2026 00:34:33 +0000 [thread overview]
Message-ID: <8efdadb0ff64495eaae66482e4871790@ti.com> (raw)
In-Reply-To: <43286199-dde8-474f-929b-a9ccdb9dc598@sirena.org.uk>
Hi Brown
> On Fri, Jul 24, 2026 at 06:25:43PM +0800, Shenghao Ding wrote:
> > Some clients have specified a new requirement: complete device
> > restarts should be avoided after calibration. Only a hot boot of the
> > Smart Audio Amplifier is required.
>
> > + /*
> > + * Set reloading-firmware flag after calibration, the flag will work
> > + * during next playback, then set to the program id after reloading
> > + * firmware.
> > + */
> > + for (i = 0; i < priv->ndev; i++)
> > + priv->tasdevice[i].cur_prog = -1;
> > +
>
> I'll apply this since this is preexisting, but it might be worth checking the
> interaction with DAPM delayed powerdown (or indeed active streams).
> There's an element of user error here of course.
Thank you very much for your valuable feedback. I will forward all your comments
directly to our customer side for full visibility.
next prev parent reply other threads:[~2026-07-31 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 10:25 [PATCH v1] ASoC: tas2781: Optimize calibration to avoid full device reboot after calibration Shenghao Ding
2026-07-30 16:40 ` Mark Brown
2026-07-31 0:34 ` Ding, Shenghao [this message]
2026-07-30 16:41 ` 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=8efdadb0ff64495eaae66482e4871790@ti.com \
--to=shenghao-ding@ti.com \
--cc=13916275206@139.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=k-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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