* pcm hw parameters?
@ 2006-03-24 13:19 Johannes Berg
2006-03-27 15:37 ` Takashi Iwai
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Berg @ 2006-03-24 13:19 UTC (permalink / raw)
To: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
Hi,
Quick question: When are the pcm hardware parameters surfaced to
userspace? Are those the ones I register in snd_pcm_new?
Thing is -- I have the problem that in theory, my codec can support
anything from 8KHz to 96KHz but when turning on digital output, it needs
to be restricted to the ones the digital output is ok with.
Of course I can trivially forbid turning on the digital out when a wrong
stream is open, but what about the other way around? When digital out is
turned on, and I forbid opening the stream when say 8KHz is selected,
does it screw over userspace and fail, or can I tell it what else to
use?
Similar things happen when you have digital input and it clocks both out
and in -- then you have to output the same bitrate as the input is
coming in at...
Thanks,
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pcm hw parameters?
2006-03-24 13:19 pcm hw parameters? Johannes Berg
@ 2006-03-27 15:37 ` Takashi Iwai
2006-03-28 12:11 ` Johannes Berg
0 siblings, 1 reply; 3+ messages in thread
From: Takashi Iwai @ 2006-03-27 15:37 UTC (permalink / raw)
To: Johannes Berg; +Cc: alsa-devel
At Fri, 24 Mar 2006 14:19:47 +0100,
Johannes Berg wrote:
>
> Hi,
>
> Quick question: When are the pcm hardware parameters surfaced to
> userspace? Are those the ones I register in snd_pcm_new?
>
> Thing is -- I have the problem that in theory, my codec can support
> anything from 8KHz to 96KHz but when turning on digital output, it needs
> to be restricted to the ones the digital output is ok with.
It's hard to restrict parameters on demands (although theoretically
it's possible). We usually provide two different devices, one for
the normal i/o and another for the digital i/o, to avoid such
conflicts.
The apps that send to the digital data would choose "spdif" or
whatever appropriate PCM name, and the system will reroute it.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pcm hw parameters?
2006-03-27 15:37 ` Takashi Iwai
@ 2006-03-28 12:11 ` Johannes Berg
0 siblings, 0 replies; 3+ messages in thread
From: Johannes Berg @ 2006-03-28 12:11 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Mon, 2006-03-27 at 17:37 +0200, Takashi Iwai wrote:
> It's hard to restrict parameters on demands (although theoretically
> it's possible). We usually provide two different devices, one for
> the normal i/o and another for the digital i/o, to avoid such
> conflicts.
I'm doing something like that now... Mind taking a look at i2sbus-pcm.c
in my git repo http://johannes.sipsolutions.net/snd-aoa.git/ ?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-03-28 12:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-24 13:19 pcm hw parameters? Johannes Berg
2006-03-27 15:37 ` Takashi Iwai
2006-03-28 12:11 ` Johannes Berg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox