[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAGoOwPQfkT2ptdt6mBTAgPfN0NOoR4KfdLE9B2AoL+Qn6bWdFw@mail.gmail.com>
Date: Tue, 6 Sep 2022 02:50:23 -0700
From: Nicolin Chen <nicoleotsuka@...il.com>
To: Shengjiu Wang <shengjiu.wang@...il.com>
Cc: Shengjiu Wang <shengjiu.wang@....com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Fabio Estevam <festevam@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_asrc: Add initialization finishing check in
runtime resume
On Mon, Sep 5, 2022 at 6:54 PM Shengjiu Wang <shengjiu.wang@...il.com> wrote:
>> > + /* 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.
Makes sense. In that case, why "FIXME" :)
Powered by blists - more mailing lists