alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: rajeev <rajeev-dlh.kumar@st.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/2] sound: asoc: Adding support for SPEAr13XX ASoC driver
Date: Mon, 21 Mar 2011 16:59:30 +0530	[thread overview]
Message-ID: <4D87369A.5030809@st.com> (raw)
In-Reply-To: <20110318114317.GB14017@opensource.wolfsonmicro.com>

Hi Mark

On 3/18/2011 5:13 PM, Mark Brown wrote:
> On Fri, Mar 18, 2011 at 12:49:04PM +0530, rajeev wrote:
>> On 3/17/2011 8:35 PM, Mark Brown wrote:
>>> On Thu, Mar 17, 2011 at 04:53:35PM +0530, Rajeev Kumar wrote:
> 
>>>> +static int spear13xx_i2s_hw_params(struct snd_pcm_substream *substream,
>>>> +		struct snd_pcm_hw_params *params,
>>>> +		struct snd_soc_dai *dai)
>>>> +{
>>>> +	struct spear13xx_i2s_dev *dev = snd_soc_dai_get_drvdata(dai);
>>>> +	u32 channel;
> 
>>>> +	channel = params_channels(params);
> 
>>>> +	dev->mode = channel;
> 
>>> Having channel here isn't doing a lot...
> 
>> I was actually planning to expand this routine in future.
>> Should I remove it from the current version?
> 
> It's not too important either way.
>
OK I will remove this function 
 
>>> These constraints don't agree with each other - the rate limits claim to
>>> support 48kHz only, the rates setting tells a different story.
> 
>> At present I checked STA529(codec) only with 48Khz,I need to check with other data rates also.
> 
> It's fine to expand later but you should make sure that if you want to
> say the device currently only works at 48kHz all the constraints say
> that - the issue is the inconsistency.
> 
Ok I will check with rate minimum and rate maximum and update it accordingly.

>>> Rather than passing the channel count through from the I2S driver you
>>> could just get it directly here.
> 
>> Are you talking about this "struct spear13xx_runtime_data *prtd = runtime->private_data"
>> Could you please elaborate little bit more.
> 
> Yes, you're passing through data that doesn't need to be passed through
> since the DMA driver gets a hw_params() call too.
> .
>
Keeping a copy of substream in struct spear13xx_runtime_data as implementation is base on tasklet.Need to extract
this  prtd->substream before dma submit. 

Best Regards
Rajeev

  reply	other threads:[~2011-03-21 11:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 11:23 [PATCH 0/2] Adding support for ASoC drivers on SPEAr13XX platform Rajeev Kumar
2011-03-17 11:23 ` [PATCH 1/2] sound: asoc: Adding support for SPEAr13XX ASoC driver Rajeev Kumar
2011-03-17 11:23   ` [PATCH 2/2] sound: asoc: Adding support for STA529 Audio Codec Rajeev Kumar
2011-03-17 15:17     ` Mark Brown
2011-03-18  6:12       ` rajeev
2011-03-18 11:39         ` Mark Brown
2011-03-21 11:29           ` rajeev
2011-03-21 12:07             ` Mark Brown
2011-03-22  5:53               ` rajeev
2011-03-22 11:34                 ` Mark Brown
2011-03-17 15:05   ` [PATCH 1/2] sound: asoc: Adding support for SPEAr13XX ASoC driver Mark Brown
2011-03-18  7:19     ` rajeev
2011-03-18 11:43       ` Mark Brown
2011-03-21 11:29         ` rajeev [this message]
2011-03-29  6:54     ` rajeev
2011-03-29  7:56       ` Mark Brown

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=4D87369A.5030809@st.com \
    --to=rajeev-dlh.kumar@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --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;
as well as URLs for NNTP newsgroup(s).