From: Takashi Iwai <tiwai@suse.de>
To: chri <chripell@gmail.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-arm-kernel@lists.arm.linux.org.uk, ben-linux@fluff.org
Subject: Re: [PATCH] ALSA SOC driver for s3c24xx: 8 bit sound fix
Date: Mon, 10 Nov 2008 08:30:19 +0100 [thread overview]
Message-ID: <s5h3ai0jawk.wl%tiwai@suse.de> (raw)
In-Reply-To: <cabda6420811092320m41cecd4brd7e20c1ce338957e@mail.gmail.com>
At Mon, 10 Nov 2008 08:20:13 +0100,
chri wrote:
>
> Hi,
>
> On Mon, Nov 10, 2008 at 7:50 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Sat, 8 Nov 2008 08:44:16 +0100,
> >
> > I don't think it's good to overwrite the global variables in this way.
> >
>
> I see. I just tried to keep the modifications minimal. Perhaps Ben
> Dooks, the author of the code, can suggest a better way to proceed. I
> will be happy to follow his suggestion.
OK.
> > And, what if playback and capture use the different formats in full
> > duplex streams...?
> >
>
> I dont' think that this is possible on the S3C24{1,4}0 since the
> configuration registers are shared between playback and record path
> (so this applies to sample frequency too for example). I guess you are
> suggesting that given parameters should be checked against those of
> the currently playing stream to see if they are compatible?
Yes. Without a proper check and/or hw_param constraints, the driver
thinks the streams are individual and allows apps to set up
independent parameters, which may result in a hardware error.
Creating hw constraints sharing both playback and capture streams is a
bit tricky and even racy. But, it'd be much better than nothing.
thanks,
Takashi
next prev parent reply other threads:[~2008-11-10 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 7:44 [PATCH] ALSA SOC driver for s3c24xx: 8 bit sound fix Christian Pellegrin
2008-11-10 6:50 ` Takashi Iwai
2008-11-10 7:20 ` chri
2008-11-10 7:30 ` Takashi Iwai [this message]
2008-11-10 11:47 ` 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=s5h3ai0jawk.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chripell@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
/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.