On Thu, Aug 27, 2020 at 12:51:11PM +0300, Kai Vehmanen wrote:
> For reasons that predate my time in the team, the minimum period size for
> many Intel platforms has been set to 192 bytes (in the topology file, i.e.
> user-space conf file). And when this is used to set the constraint in ALSA,
> you get the very JACK unfriendly period sizes. There's no fundamental limit
> in hw that would prevent JACK friendy period sizes.
According to which stange rules would this value (192 = 3 * 2^6) lead to
2^k being rejected and 2^k + 8 being accepted ??
> There's been a lengthy debate about this in SOF project and issue is still
> unsolved. I'll now promise to kick this forward. The main rub is that we are
> missing a place to declare hw specific granularity constraints (i.e. how to
> set period_size step site for each hw)
That looks like a serious design error...
Ciao,
-- FA _______________________________________________ Linux-audio-user mailing list Linux-audio-user@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Fri Aug 28 04:15:01 2020
This archive was generated by hypermail 2.1.8 : Fri Aug 28 2020 - 04:15:01 EEST