On 06.02.2015 11:02, Alexander E. Patrakov wrote:
06.02.2015 14:56, Georg Chini wrote:
One more thing: There is a systematic error in the adjust_time I could
not work around without
introducing too much overhead. The latency snapshot varies widely in the
execution time, I
measured values
06.02.2015 14:56, Georg Chini wrote:
One more thing: There is a systematic error in the adjust_time I could
not work around without
introducing too much overhead. The latency snapshot varies widely in the
execution time, I
measured values between 50 us and more than 60 ms. So if the extreme
08.02.2015 11:06, Raymond Yau wrote:
Hrm, that is actually a good question. In theory, I would expect
module-switch-on-port-available to switch profiles between 2.0 and 2.1
as headphones are plugged in and out, but in practice,
- I'm not 100% sure if our don't switch to HDMI
On 07.02.2015 20:50, Alexander E. Patrakov wrote:
06.02.2015 14:56, Georg Chini wrote:
One more thing: There is a systematic error in the adjust_time I could
not work around without
introducing too much overhead. The latency snapshot varies widely in the
execution time, I
measured values
Hrm, that is actually a good question. In theory, I would expect
module-switch-on-port-available to switch profiles between 2.0 and 2.1
as headphones are plugged in and out, but in practice,
- I'm not 100% sure if our don't switch to HDMI might prevent
switching from 2.1 to 2.0
