From: jassi brar <jassisinghbrar@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: kyungmin.park@samsung.com, alsa-devel@alsa-project.org,
Joonyoung Shim <jy0922.shim@samsung.com>
Subject: Re: Separate dma driver for cpu_dais
Date: Tue, 23 Feb 2010 14:45:47 +0900 [thread overview]
Message-ID: <1b68c6791002222145r543b0e45sfd842d8ddde4280f@mail.gmail.com> (raw)
In-Reply-To: <20100218131027.GF3542@rakim.wolfsonmicro.main>
On Thu, Feb 18, 2010 at 10:10 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Thu, Feb 18, 2010 at 08:59:38PM +0900, jassi brar wrote:
>> On Thu, Feb 18, 2010 at 7:57 PM, Mark Brown
>> IMO codecs should simply do as directed by the ASOC.
>
> Right, but that doesn't mean that the device drivers can't do anything
> useful here - in terms of restrictions they can't do anything the
> hardware can't implmenent. Another example here is that startup
> function can set constraints based on the configuration of other running
> links if the hardware has any limitations in that regard (some will,
> some won't, and the limitations may not even be anything to do with
> audio in some designs).
Okay. Here's another perspective ...
If a dai can have further parallel sub-configurations, perhaps it should
be further divided into more dais.
So, I see a snd_soc_dai as the simplest h/w unit in the system and
presumably already fully exploited by the active dai_link i.e, none of
its bits can be changed without disturbing the active stream. The
number of shares should be transparent to a dai.
If this assumption is valid please read on, otherwise correct me.
The set of {rate, sample size & format, channels} defines one active
dai. The second stream sharing this dai can not change any of these
parameters without spoiling the active playback/capture - we can allow
this configuration overriding as a feature or prevent as a bug. I
prefer latter. Since there isn't anything new to do now, the ASoC core
can
simply avoid calling hooks in drivers rather than having 50 drivers
implement a check.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-02-23 5:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 2:39 Separate dma driver for cpu_dais jassi brar
2010-02-17 6:58 ` Joonyoung Shim
2010-02-17 7:24 ` jassi brar
2010-02-17 7:37 ` Joonyoung Shim
2010-02-17 10:52 ` Mark Brown
2010-02-17 12:15 ` jassi brar
2010-02-17 13:14 ` Mark Brown
2010-02-18 2:14 ` jassi brar
2010-02-18 9:35 ` Mark Brown
2010-02-18 9:42 ` jassi brar
2010-02-18 9:52 ` Mark Brown
2010-02-18 10:32 ` jassi brar
2010-02-18 10:57 ` Mark Brown
2010-02-18 11:59 ` jassi brar
2010-02-18 13:10 ` Mark Brown
2010-02-23 5:45 ` jassi brar [this message]
2010-02-23 10:37 ` Mark Brown
2010-02-19 9:48 ` jassi brar
2010-02-19 9:50 ` Mark Brown
2010-02-18 6:12 ` Joonyoung Shim
2010-02-18 9:42 ` Mark Brown
2010-02-17 10:42 ` Mark Brown
2010-02-17 12:13 ` jassi brar
2010-02-17 12:42 ` 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=1b68c6791002222145r543b0e45sfd842d8ddde4280f@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.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 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).