Re: [pulseaudio-discuss] [PATCH] bluez5-device, bluez5-discover: add hsp_source_buffer_msec argument

On 10.04.2018 14:52, Luiz Augusto von Dentz wrote: Hi George, On Mon, Apr 9, 2018 at 7:16 PM, Georg Chini wrote: Currently the PA bluetooth code calls source_push() for each HSP source packet. The default HSP MTU is 48 bytes, this means that source_push() is called every 3ms,

Re: [pulseaudio-discuss] [PATCH] bluez5-device, bluez5-discover: add hsp_source_buffer_msec argument

Hi George, On Mon, Apr 9, 2018 at 7:16 PM, Georg Chini wrote: > Currently the PA bluetooth code calls source_push() for each HSP source > packet. > The default HSP MTU is 48 bytes, this means that source_push() is called every > 3ms, which leads to increased CPU load especially

[pulseaudio-discuss] [PATCH] bluez5-device, bluez5-discover: add hsp_source_buffer_msec argument

Currently the PA bluetooth code calls source_push() for each HSP source packet. The default HSP MTU is 48 bytes, this means that source_push() is called every 3ms, which leads to increased CPU load especially on embedded systems. This patch adds a hsp_source_buffer_msec argument to