From: Simon Ho <simon.ho.cnxt@gmail.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Simon Ho <simon.ho@conexant.com>,
tiwai@suse.com, lgirdwood@gmail.com,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org
Subject: Re: [PATCH v4 2/2] ASoC: Add support for Conexant CX2092X DSP
Date: Thu, 6 Apr 2017 09:32:36 +0800 [thread overview]
Message-ID: <20170406013236.GA3818@GMAIL.COM> (raw)
In-Reply-To: <20170405151704.GA3412@localhost.localdomain>
On Wed, Apr 05, 2017 at 04:17:04PM +0100, Charles Keepax wrote:
> On Wed, Apr 05, 2017 at 06:27:13PM +0800, simon.ho.cnxt@gmail.com wrote:
> > From: Simon Ho <simon.ho@conexant.com>
> >
> > Initial commit of Conexant CX20921/CX20924 I2S Audio DSP driver
> >
> > The CX2092X devices are designed for virtual assisant application need to
> > be always open, listening for users to summon it. There is no any power
> > saving mode support on this device. The processed voice data will be sent
> > to automatic speech recognition (ASR) application for further processing.
> >
> > Signed-off-by: Simon Ho <simon.ho@conexant.com>
> > ---
>
> Just a couple of very minor points.
>
Thank you for your useful comments, I will fix them.
> > +static int cx2092x_sendcmd(struct snd_soc_codec *codec,
> > + struct cx2092x_cmd *cmd)
> > +{
> > + struct cx2092x_priv *cx2092x = snd_soc_codec_get_drvdata(codec);
> > + int ret = 0;
> > + int num_32b_words = cmd->num_32b_words;
> > + unsigned long time_out;
> > + u32 *i2c_data = (u32 *)cmd;
> > + int size = num_32b_words + 2;
> > +
> > + /* calculate how many WORD that will be wrote to device*/
> > + cmd->num_32b_words = cmd->command_id & CX2092X_CMD_GET(0) ?
> > + CX2092X_CMD_SIZE : num_32b_words;
> > +
> > + /* write all command data except fo frist 4 bytes*/
> > + ret = regmap_bulk_write(cx2092x->regmap, 4, &i2c_data[1], size - 1);
> > + if (ret < 0) {
> > + dev_err(cx2092x->dev, "Failed to write command data\n");
> > + goto LEAVE;
>
> All caps for a label is a bit unusual probably would be more
> normal kernel style to make this lower case.
>
> > + }
> > +
> > + /* write first 4 bytes command data*/
> > + ret = regmap_bulk_write(cx2092x->regmap, 0, i2c_data, 1);
> > + if (ret < 0) {
> > + dev_err(cx2092x->dev, "Failed to write command\n");
> > + goto LEAVE;
> > + }
> > +
> > + /* continuously read the first bytes data from device until
> > + * either timeout or the flag 'reply' is set.
> > + */
> > + time_out = msecs_to_jiffies(2000);
> > + time_out += jiffies;
> > + do {
> > + regmap_bulk_read(cx2092x->regmap, 0, &i2c_data[0], 1);
> > + if (cmd->reply == 1)
> > + break;
> > + mdelay(10);
>
> Do you really want to use mdelay's, they are busy wait loops
> so thrash the processor, a usleep_range or an msleep might be a
> more friendly.
>
> Thanks,
> Charles
prev parent reply other threads:[~2017-04-06 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 10:27 [PATCH v4 0/2] ASoC: add driver support for CX2092X DSP simon.ho.cnxt
2017-04-05 10:27 ` [PATCH v4 1/2] doc: cx2092x: Add DT bingings doc " simon.ho.cnxt
2017-04-05 10:27 ` [PATCH v4 2/2] ASoC: Add support for Conexant " simon.ho.cnxt
2017-04-05 15:17 ` Charles Keepax
2017-04-06 1:32 ` Simon Ho [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=20170406013236.GA3818@GMAIL.COM \
--to=simon.ho.cnxt@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=simon.ho@conexant.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