[pulseaudio-tickets] [Bug 39412] Choppy Sound with Pulsesink on ARM

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=39412

--- Comment #3 from Vallabha <vallabha.pa at gmail.com> 2011-07-25 05:24:34 PDT ---
Hello Arun,

I am working on an embedded platform.

cat /proc/timer_list

gives me following information. Let me know if it suffices PA's requirement. I
see that the resolution available is 1/100th of a second.

Timer List Version: v0.6
HRTIMER_MAX_CLOCK_BASES: 2
now at 22634717484152 nsecs
cpu: 0
 clock 0:
  .base:       c0460160
  .index:      0
  .resolution: 10000000 nsecs
  .get_time:   ktime_get_real
active timers:
 clock 1:
  .base:       c0460188
  .index:      1
  .resolution: 10000000 nsecs
  .get_time:   ktime_get
active timers:
 #0: <c0484c58>, sched_rt_period_timer, S:01
 # expires at 22635000000000-22635000000000 nsecs [in 282515848 to 282515848
nsecs]
  .nohz_mode      : 1
  .idle_tick      : 22634720000000 nsecs
  .tick_stopped   : 0
  .idle_jiffies   : 2233471
  .idle_calls     : 3361941
  .idle_sleeps    : 3187525
  .idle_entrytime : 22634713881502 nsecs
  .idle_waketime  : 22634713881502 nsecs
  .idle_exittime  : 22634713918152 nsecs
  .idle_sleeptime : 21115835861013 nsecs
  .iowait_sleeptime: 49387606847 nsecs
  .last_jiffies   : 2233471
  .next_jiffies   : 2233500
  .idle_expires   : 22635000000000 nsecs
jiffies: 2233471

Tick Device: mode:     1
Per CPU device: 0
Clock Event Device: gp timer
 max_delta_ns:   214748367050
 min_delta_ns:   1000
 mult:           85899345
 shift:          32
 mode:           3
 next_event:     22634720000000 nsecs
 set_next_event: omap2_gp_timer_set_next_event
 set_mode:       omap2_gp_timer_set_mode
 event_handler:  tick_nohz_handler
 retries:        0

"without high-res timers, you can't run in "glitch-free" mode"

Does this mean, I am bound to encounter audio glitches as one of the blog by
Lennart suggests?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.