All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Foerster <mls.JOFT@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Lorenz Kolb <lorenz.kolb@lkmail.de>
Subject: Re: How to enforce 32bit access?
Date: Wed, 10 Oct 2007 17:40:08 +0200	[thread overview]
Message-ID: <1192030808.5545.23.camel@localhost> (raw)
In-Reply-To: <s5hr6k3qf3a.wl%tiwai@suse.de>

On Wed, 2007-10-10 at 15:22 +0200, Takashi Iwai wrote:
> > > At Fri, 05 Oct 2007 19:09:53 +0200,
> > > Joachim Foerster wrote:
> > > > 
> > > > Hi ALSA devs,
> > > > 
> > > > meanwhile I tried to put a constraint on SNDRV_PCM_HW_PARAM_FRAME_BITS
> > > > by the use of snd_pcm_hw_constraint_minmax() function with min=32 and
> > > > max=32, but still no success - the ALSA Library still makes 16bit
> > > > accesses, when playing mono (1 channel) files.
> > > > 
> > > > Any ideas?
> > > 
> > > Could you show the chain of plugins via aplay -v ?
> > > I'm not sure which plugin requires S16.  Possibly, the rate converter.
> > 
> > bash-3.00# aplay -v -M ../Absage.wav
> > Playing WAVE '../Absage.wav' : Signed 16 bit Little Endian, Rate 16000
> > Hz, Mono
> 
> Well, the sample itself is 16bit format, and your hardware *does*
> support 16bit format.  Why to be 32bit?

Well actually, we are on a embedded system here. The bus is 32bit wide
(Xilinx ML403, PowerPC 405, OBP). So, why waste resources with two 16bit
accesses?
One sample is 16bits. But we have two channels (stereo only). Thus the
controller expects a frame with 32bit data - two samples at the same
time.

 Joachim

PS: As soon as stereo .wav-files are used, there is no problem, because
then the "conversion framework" and the Plug PCM are not used - just a
plain memcpy which results in 32bit accesses.

  reply	other threads:[~2007-10-10 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 15:34 How to enforce 32bit access? Joachim Foerster
2007-10-05 17:09 ` Joachim Foerster
2007-10-09  9:08   ` Takashi Iwai
2007-10-10 13:19     ` Joachim Foerster
2007-10-10 13:22       ` Takashi Iwai
2007-10-10 15:40         ` Joachim Foerster [this message]
2007-10-11  8:50           ` Takashi Iwai
2007-10-11 13:30             ` Joachim Foerster
2007-10-11 19:29               ` Trent Piepho

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=1192030808.5545.23.camel@localhost \
    --to=mls.joft@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=lorenz.kolb@lkmail.de \
    --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 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.