[lvc-project] [PATCH BlueZ v2 1/2] audio: actually try to enable MTU auto-tuning

[Luiz Augusto von Dentz]

Hi Fedor,

On Thu, Jan 30, 2025 at 12:30 PM <patchwork-bot+bluetooth at kernel.org> wrote:
>
> Hello:
>
> This series was applied to bluetooth/bluez.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz at intel.com>:
>
> On Wed, 29 Jan 2025 11:49:49 +0300 you wrote:
> > A "0" for the input MTU passed to the underlying socket is supposed to
> > indicate that its value should be determined by the L2CAP layer.
> > However, the current code treats a zero imtu just as if there is
> > nothing to change.
> >
> > Introduce an additional flag to indicate that the zero imtu is
> > explicitly requested by the caller for the purpose of auto-tuning.
> > Otherwise, the similar behavior remains.
> >
> > [...]
>
> Here is the summary with links:
>   - [BlueZ,v2,1/2] audio: actually try to enable MTU auto-tuning
>     (no matching commit)

Ive done quite a few modifications to the above change, so instead of
using a auto_mtu it now checks if -1 for not set, Ive checked with a
couple headsets I have and it seem to work fine but perhaps you want
to check as well just to make sure I didn't screw something up.

>   - [BlueZ,v2,2/2] a2dp: enable input MTU auto-tuning for the server
>     https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=252a32ac0b3f
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
>
>
>


-- 
Luiz Augusto von Dentz