[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGoOwPQomcnO5dhkT9DBynwJo8LfVvuuwj5AYNpv0KhAGSWLEw@mail.gmail.com>
Date: Mon, 5 Sep 2022 06:15:27 -0700
From: Nicolin Chen <nicoleotsuka@...il.com>
To: Shengjiu Wang <shengjiu.wang@....com>
Cc: Xiubo.Lee@...il.com, festevam@...il.com, shengjiu.wang@...il.com,
lgirdwood@...il.com, broonie@...nel.org, perex@...ex.cz,
tiwai@...e.com, alsa-devel@...a-project.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: fsl_asrc: Add initialization finishing check in
runtime resume
On Mon, Sep 5, 2022 at 3:47 AM Shengjiu Wang <shengjiu.wang@....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?
Powered by blists - more mailing lists