From: Shengjiu Wang <shengjiu.wang@gmail.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org, Xiubo Li <Xiubo.Lee@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Mark Brown <broonie@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_asrc: Add initialization finishing check in runtime resume
Date: Tue, 6 Sep 2022 09:54:16 +0800 [thread overview]
Message-ID: <CAA+D8APOL1Qx0fAhyajXXzh0_tqEmDJoDBh3Xgo6uYNhV0usBw@mail.gmail.com> (raw)
In-Reply-To: <CAGoOwPQomcnO5dhkT9DBynwJo8LfVvuuwj5AYNpv0KhAGSWLEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Mon, Sep 5, 2022 at 9:15 PM Nicolin Chen <nicoleotsuka@gmail.com> wrote:
> On Mon, Sep 5, 2022 at 3:47 AM Shengjiu Wang <shengjiu.wang@nxp.com>
> wrote:
> > @@ -1295,6 +1301,17 @@ static int fsl_asrc_runtime_resume(struct device
> *dev)
> > regmap_update_bits(asrc->regmap, REG_ASRCTR,
> > ASRCTR_ASRCEi_ALL_MASK, asrctr);
> >
> > + /* Wait for status of initialization for every enabled pairs */
> > + do {
> > + udelay(5);
> > + regmap_read(asrc->regmap, REG_ASRCFG, ®);
> > + reg = (reg >> ASRCFG_INIRQi_SHIFT(0)) & 0x7;
> > + } while ((reg != ((asrctr >> ASRCTR_ASRCEi_SHIFT(0)) & 0x7)) &&
> --retry);
> > +
> > + /* FIXME: Doesn't treat initialization timeout as error */
> > + if (!retry)
> > + dev_warn(dev, "initialization isn't finished\n");
>
> Any reason why not just dev_err?
Just hesitate to use dev_err. if use dev_err, then should return an error.
May one of the pairs is finished, it still can continue.
Best regards
Wang Shengjiu
[-- Attachment #2: Type: text/html, Size: 1770 bytes --]
next prev parent reply other threads:[~2022-09-06 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:29 [PATCH] ASoC: fsl_asrc: Add initialization finishing check in runtime resume Shengjiu Wang
2022-09-05 13:15 ` Nicolin Chen
2022-09-06 1:54 ` Shengjiu Wang [this message]
2022-09-06 9:50 ` Nicolin Chen
2022-09-06 10:50 ` Shengjiu Wang
2022-09-06 11:41 ` Nicolin Chen
2022-09-06 13:55 ` Shengjiu Wang
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=CAA+D8APOL1Qx0fAhyajXXzh0_tqEmDJoDBh3Xgo6uYNhV0usBw@mail.gmail.com \
--to=shengjiu.wang@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@nxp.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).