From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org, Alastair Poole <netstar@gatheringofgray.com>
Subject: Re: new sound driver
Date: Fri, 24 Mar 2006 08:09:05 +1100 [thread overview]
Message-ID: <1143148145.4257.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1143134017.8395.19.camel@localhost>
> What I'm currently thinking of is creating one PCM per codec, and then
> if you can't use them at the same time just forbid access to it.
No, it should really be one PCM per bus... I don't see why you would
prevent somebody from outputing on both digital and analog outputs at
the same time for example (the same data of course). One PCM = one
stream = one bus carrying the samples. All codecs on that bus whould be
set to the same settings of course. If one can't but the other can, just
mute the one that can't I suppose...
Also, Alsa does have some means of asynchronous notifyication of a state
change on a control (and calls you back later with some locking) though
I'm not too familiar with the details. You should ask on the list once
you have the basic dbdma stuff there :)
> > Just sleep on it for now :) We definitely need a "core" module that
> > handles all of the gpio mess. ..
>
> Yeah. Haven't even opened that can of worms yet...
>
> johannes
next prev parent reply other threads:[~2006-03-23 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 9:35 new sound driver Johannes Berg
2006-03-22 21:50 ` Benjamin Herrenschmidt
2006-03-23 17:13 ` Johannes Berg
2006-03-23 21:09 ` Benjamin Herrenschmidt [this message]
2006-03-23 17:00 ` Johannes Berg
2006-03-24 11:37 ` Johannes Berg
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=1143148145.4257.8.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=netstar@gatheringofgray.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).