All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [patch 1/2] alsa: ASoC driver for s6000 I2S	interface
Date: Fri, 27 Mar 2009 16:20:49 +0000	[thread overview]
Message-ID: <20090327162048.GA7542@sirena.org.uk> (raw)
In-Reply-To: <49CCFA24.3020203@emlix.com>

On Fri, Mar 27, 2009 at 05:09:08PM +0100, Daniel Glöckner wrote:
> On 03/26/2009 03:15 PM, Mark Brown wrote:

> > I'm not seeing any hits on XTENSA_VARIANT_S6000 in next?  While that
> > shouldn't hurt immediately since it'll just never appear it'd be good to
> > make sure that the APIs this depends on are going into mainline in the
> > form they're in.  Do you know what the status is there?

> The patch introducing XTENSA_VARIANT_S6000 has already been reviewed by
> the architecture maintainer and there is hope that it will make it into
> 2.6.30. The dma api, which we posted four days ago to LKML, has not
> received any comments so far.

OK, might be worth nagging the architecture maintainer to get their tree
included in -next if it isn't already.

> >> +#define S6000_I2S_RATES	(SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_KNOT | \
> >> +			 SNDRV_PCM_RATE_5512 | SNDRV_PCM_RATE_8000_192000)
> > 
> > SND_PCM_RATE_KNOT doesn't work with ASoC (though it shouldn't do any
> > harm since it'll just get removed).

> Except for the maximum bit clock (50 MHz) the interface doesn't care about
> the sampling rate, so I put in all SNDRV_PCM_RATE_* constants.
> Shall I remove it?

Yes, please - this applies to almost all CPU side drivers, it's kind of
unfortunate but in practice it generally makes very little practical
difference since applications tend to use one of the standard audio
rates.

> > Any reason to expose these to users? 

> This was an attempt to avoid symbol exports..
> I'll move everything to s6000-i2s.c and export the three necessary
> functions.

Which functions are you exporting?  None of this looked like anything
that I'd expect to see used outside of the driver.

  reply	other threads:[~2009-03-27 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:36 [patch 1/2] alsa: ASoC driver for s6000 I2S interface Daniel Glöckner
2009-03-26 13:36 ` [patch 2/2] alsa: s6105 IP camera machine specific ASoC code Daniel Glöckner
2009-03-26 14:26   ` Mark Brown
2009-03-27 16:33     ` Daniel Glöckner
2009-03-27 16:39       ` Mark Brown
2009-03-26 14:15 ` [patch 1/2] alsa: ASoC driver for s6000 I2S interface Mark Brown
2009-03-27 16:09   ` Daniel Glöckner
2009-03-27 16:20     ` Mark Brown [this message]
2009-03-27 16:49       ` Daniel Glöckner
2009-03-27 16: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=20090327162048.GA7542@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=dg@emlix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.