From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Baojun Xu <baojun.xu@ti.com>
Cc: <tiwai@suse.de>, <andriy.shevchenko@linux.intel.com>,
<13916275206@139.com>, <alsa-devel@alsa-project.org>,
<shenghao-ding@ti.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <k-yi@ti.com>, <henry.lo@ti.com>,
<robinchen@ti.com>, <niranjan.hy@ti.com>, <pin-hao.huang@hp.com>,
<Syed.SabaKareem@amd.com>, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v4] ASoC: tas2783-sdw: add firmware download status check
Date: Tue, 15 Sep 2026 21:06:11 +0200 [thread overview]
Message-ID: <e1f78e4f-f9dd-4cc5-bacb-6b61294cebca@intel.com> (raw)
In-Reply-To: <20260915035223.1518-1-baojun.xu@ti.com>
On 9/15/2026 5:52 AM, Baojun Xu wrote:
> Currently, the firmware download is unnecessarily triggered on every
> system resume from suspend, causing significant wake-up latency. However,
> this step is redundant if the AMP remains powered on.
Either drop 'unnecessarily' in the first sentence or shorten the second
sentence to 'The step is redundant (...)'.
> @@ -996,7 +997,7 @@ static s32 tas_sdw_hw_params(struct snd_pcm_substream *substream,
> TAS2783_SDCA_POW_STATE_ON);
> if (!ret)
> break;
> - usleep_range(2000, 2200);
> + fsleep(2200);
Is this a crucial part of the patch? Looks out of scope and if so,
please move it to a separate patch.
> } while (retry--);
> }
> @@ -1252,25 +1253,29 @@ static s32 tas_fw_load(struct tas2783_prv *tas_dev, struct sdw_slave *slave)
> static s32 tas_io_init(struct device *dev, struct sdw_slave *slave)
> {
> struct tas2783_prv *tas_dev = dev_get_drvdata(dev);
> + unsigned int val;
> s32 ret;
>
> if (tas_dev->hw_init)
> return 0;
>
> - tas_dev->fw_dl_success = false;
> + regmap_read(tas_dev->regmap, TASDEV_REG_SDW(0, 0, 7), &val);
> + /* Check if the AMP is in reset status. */
Please add a newline between regmap_read() and the comment.
> + if (val == 0x20) {
> + tas_dev->fw_dl_success = false;
>
prev parent reply other threads:[~2026-09-15 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 3:52 Baojun Xu
2026-09-15 18:53 ` Mark Brown
2026-09-15 19:06 ` Cezary Rojewski [this message]
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=e1f78e4f-f9dd-4cc5-bacb-6b61294cebca@intel.com \
--to=cezary.rojewski@intel.com \
--cc=13916275206@139.com \
--cc=Syed.SabaKareem@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=henry.lo@ti.com \
--cc=k-yi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niranjan.hy@ti.com \
--cc=pin-hao.huang@hp.com \
--cc=robinchen@ti.com \
--cc=shenghao-ding@ti.com \
--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
all inboxes | Powered by JetHome®