Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, patches.audio@intel.com,
	Hardik T Shah <hardik.t.shah@intel.com>,
	Guneshwor Singh <guneshwor.o.singh@intel.com>,
	liam.r.girdwood@linux.intel.com, broonie@kernel.org
Subject: Re: [PATCH v3 5/5] ALSA - hda: Add support for link audio time reporting
Date: Thu, 4 Aug 2016 07:30:10 +0530	[thread overview]
Message-ID: <20160804020010.GZ9681@localhost> (raw)
In-Reply-To: <s5hh9b19630.wl-tiwai@suse.de>

On Wed, Aug 03, 2016 at 06:21:07PM +0200, Takashi Iwai wrote:
> > +{
> > +	struct snd_pcm_substream *substream = (struct snd_pcm_substream *)ctx;
> 
> Superfluous cast.

ok

> > +		dma_select = (direction << GTSCC_CDMAS_DMA_DIR_SHIFT) |
> > +					(azx_dev->core.stream_tag - 1);
> > +		_snd_hdac_chip_write(l, azx_bus(chip), AZX_REG_GTSCC,
> > +						dma_select);
> 
> You can use
> 		snd_hdac_chip_writel(azx_bus(chip), GTSCC, dma_select);
> 
> The use of _snd_hdac_chip_write() is for non-constant registers.  When
> you pass AZX_REG_XXX, you can use the standard macro.  For example:

Yes I remeber that. I did see this earlier but missed to update :(

> > +		/* Enable the capture */
> > +		_snd_hdac_chip_write(l, azx_bus(chip), AZX_REG_GTSCC,
> > +				     _snd_hdac_chip_read(l, azx_bus(chip),
> > +					AZX_REG_GTSCC) | GTSCC_TSCCI_MASK);
> 
> This can be simplified with snd_hdac_chip_updatel().

ok


> > +	if (retry_count == HDA_MAX_CYCLE_READ_RETRY) {
> > +		dev_err(chip->card->dev, "Error in WALFCC cycle count\n");
> 
> Hrm, this has a danger to spew huge amount of error messages, since
> this gets called so often.

print once or rate limit?


> > -	} else
> > +	} else if ((runtime->hw.info &
> > +			SNDRV_PCM_INFO_HAS_LINK_SYNCHRONIZED_ATIME) &&
> > +			(audio_tstamp_config->type_requested ==
> > +			SNDRV_PCM_AUDIO_TSTAMP_TYPE_LINK_SYNCHRONIZED)) {
> 
> The indentation is hard to follow here...

will fix

> 
> > +
> > +		azx_get_crosststamp(substream, &xtstamp);
> 
> No error check?

yes will add

-- 
~Vinod

      reply	other threads:[~2016-08-04  1:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 16:06 [PATCH v3 0/5] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-08-03 16:06 ` [PATCH v3 1/5] ALSA: hda - move bus_parse_capabilities to core Vinod Koul
2016-08-03 16:09   ` Takashi Iwai
2016-08-04  1:56     ` Vinod Koul
2016-08-03 16:06 ` [PATCH v3 2/5] ALSA: convert users to core bus_parse_capabilities Vinod Koul
2016-08-09 12:44   ` Applied "ALSA: convert users to core bus_parse_capabilities" to the asoc tree Mark Brown
2016-08-03 16:06 ` [PATCH v3 3/5] ALSA - Ext hda: remove bus_parse_capabilities Vinod Koul
2016-08-09 12:44   ` Applied "ALSA - Ext hda: remove bus_parse_capabilities" to the asoc tree Mark Brown
2016-08-03 16:06 ` [PATCH v3 4/5] ALSA - hda: Add support for parsing new HDA capabilities Vinod Koul
2016-08-03 16:11   ` Takashi Iwai
2016-08-04  2:00     ` Vinod Koul
2016-08-04  5:51       ` Vinod Koul
2016-08-04  5:46         ` Takashi Iwai
2016-08-03 16:06 ` [PATCH v3 5/5] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-08-03 16:21   ` Takashi Iwai
2016-08-04  2:00     ` Vinod Koul [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=20160804020010.GZ9681@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=guneshwor.o.singh@intel.com \
    --cc=hardik.t.shah@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.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