Re: [pulseaudio-discuss] [alsa-devel] [PATCH 1/3] add API to allow disabling period interrupts
On Mon, May 17, 2010 at 11:42 PM, Jaroslav Kysela pe...@perex.cz wrote:
On Mon, 17 May 2010, Jassi Brar wrote:
On Mon, May 17, 2010 at 8:16 PM, Clemens Ladisch clem...@ladisch.de
wrote:
Jassi Brar wrote:
I am in favor of support variable hw_interrupt at lowest level, i.e, in
ring buffer driver, instead of disabling hw_interrupt altogether.
Removing the constant-sized periods restriction would certainly be
useful. However, it doesn't look as if anybody has the time to redesign
the ALSA API, the kernel framework and all the drivers.
No need to redesign ALSA API and certainly no need to change _any_ driver,
just like this interrupt disable call is optional so would period resize
be.
I only ask to make this newly added call as period-resize rather than
a special case of period-disable.
This is very good point. But I have two comments:
1) Period-disable function is OK, but it should not have a name no
period irq: SNDRV_PCM_INFO_PERIOD_DISABLE or DISABLE_PERIOD looks
better. This change does imply to set the period size automatically in
the driver - probably to highest value (applications cannot choose/set
the period size in this operation mode - it's useless anyway).
2) The avail_min parameter in sw_params was overlooked. The lowlevel
drivers can use this value to compute the wake-up point and set hw
appropriately, to do wake-up at requested time. We can add a support
functions like return how many samples are expected to be transferred
for next wake-up point to linux/sound/pcm.h. In case when this value
is high, no interrupts (wake ups) will be processed in the driver. If
hardware cannot do the precise transfers, we can program a system
timer as the wake-up source.
Sounds good, though I had a different implementation in mind...
A new _optionally_ supported call to set the ratio of h/w period
to ring buffer.
The fields are returned with actually set ratio by the low
level driver upon call return. The boundary case of say 0/0
can be interpreted as intr disable and n/n as period := ring
The call can be used to query current ratio by asking for
a/b where a b i.e, invalid ratio.
Depending upon the capability of the h/w and it's driver,
fine-tuning can be achieved to max possible extent.
something like
snd_pcm_uframes_t prd, ring;
/* Get current ratio */
prd = 257, ring = 256; /* Invalid ratio */
snd_pcm_set_ratio(prd, ring);
/* Increase the period by desirable amount */
prd += incr;
snd_pcm_set_ratio(prd, ring);
/* Disable period interrupts */
prd = 0, ring = 0;
snd_pcm_set_ratio(prd, ring);
if (!prd !ring) {
Interrupts are successfull disabled;
} else {
prd/ring ratio is max supported by h/w
}
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Help with Udev Please
I just upgraded from fc11 to fc12. With fc12 comes PA 0.9.21.
Pulseaudio fails to detect any of my audio cards, I have two cards.
I'm positive the problem is with UDEV. When I boot the system,
I'm getting a cryptic message from udev about some {ATTR ... uvent}
file not found. I'm having trouble getting the error message to
report, it flies off the screen before I can record it.
I'm looking for advice on maybe how best to debug how udev deals
with audio cards? Maybe someone has already seen this issue?
I'm looking at the udev site too.
Thanks,
Jim
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Help with Udev Please
I just upgraded from fc11 to fc12. With fc12 comes PA 0.9.21.
Pulseaudio fails to detect any of my audio cards, I have two cards.
I'm positive the problem is with UDEV. When I boot the system,
I'm getting a cryptic message from udev about some {ATTR ... uvent}
file not found. I'm having trouble getting the error message to
report, it flies off the screen before I can record it.
Looks like a syntax error in one of the udev rules.
Perhaps you can see if the message shows up in /var/log/syslog and then
grep for that string in the udev rules directory?
// David
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Help with Udev Please
On 05/18/2010 07:50 PM, David Henningsson wrote: Looks like a syntax error in one of the udev rules. Perhaps you can see if the message shows up in /var/log/syslog and then grep for that string in the udev rules directory? // David Unfortunately, I don't get any udev message in syslog. I have 2 machines up on fc12. Udev appears to work on one, but not the other. The /etc/udev/rules.d/90-alsa.rules file is identical on both. jim cat 90-alsa.rules ACTION==add, SUBSYSTEM==sound, KERNEL==controlC*, \ RUN+=/sbin/alsactl -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main restore /dev/$name ACTION==remove, SUBSYSTEM==sound, KERNEL==controlC*, \ RUN+=/sbin/alsactl -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf store /dev/$name On the machine which works, I'm using the stock kernel from fc12. On the machine which doesn't work, I have to use my own kernel build. Both kernels are of the 2.6.32 (one is .11 the other .13) All of the sysfs stuff for both kernels are the same. Jim ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] module_combine arguments 0.9.21
Can someone tell me if the arguments for module_combine have changed recently? These no longer work with 0.9.21, but did with the earlier release with fc11 (0.9.15 I believe). load-module module-combine sink_name=combined master=alsa_output.hw_AudioPCI slaves=alsa_output.hw_ICH5,rtp,sphinx_playback load-module module-combine sink_name=combined_local master=alsa_output.hw_AudioPCI slaves=alsa_output.hw_ICH5 Thanks, Jim ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] module_combine arguments 0.9.21
On Tue, May 18, 2010 at 21:47, Jim Duda j...@duda.tzo.com wrote: Can someone tell me if the arguments for module_combine have changed recently? These no longer work with 0.9.21, but did with the earlier release with fc11 (0.9.15 I believe). load-module module-combine sink_name=combined master=alsa_output.hw_AudioPCI slaves=alsa_output.hw_ICH5,rtp,sphinx_playback load-module module-combine sink_name=combined_local master=alsa_output.hw_AudioPCI slaves=alsa_output.hw_ICH5 From the module documentation [0] you can see 'master' argument became obsolete on 0.9.11. [0] http://pulseaudio.org/wiki/Modules#module-combine -- João Paulo Rechi Vita http://jprvita.wordpress.com/ ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] module_combine arguments 0.9.21
On 05/18/2010 10:51 PM, João Paulo Rechi Vita wrote: From the module documentation [0] you can see 'master' argument became obsolete on 0.9.11. [0] http://pulseaudio.org/wiki/Modules#module-combine I even read that, but missed the note (-: Thank you. Jim ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
