Hi Pauli, On Mon, Apr 1, 2024 at 4:00 PM <patchwork-bot+bluetooth@xxxxxxxxxx> wrote: > > Hello: > > This series was applied to bluetooth/bluetooth-next.git (master) > by Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>: > > On Thu, 14 Mar 2024 20:20:16 +0200 you wrote: > > Add support for TX timestamping in ISO/SCO/L2CAP sockets. > > > > These patches allow fixing / working around controller(?) issue where > > two ISO streams in same group get desynchronized. It also gives user > > applications the best latency information as available to kernel. > > > > Also add sockopt BT_NO_ERRQUEUE_POLL to optionally disable POLLERR > > wakeup on TX timestamp arrival, which is mainly a nuisance in the use > > case here. The alternative to this seems be to deal with the POLLERR > > wakeups in BlueZ side, but this seems hard as it's always enabled in > > poll() flags so not clear if anything else than polling at regular > > intervals can be done there. > > > > [...] > > Here is the summary with links: > - [v2,1/5] Bluetooth: add support for skb TX timestamping > https://git.kernel.org/bluetooth/bluetooth-next/c/0368e609d090 > - [v2,2/5] Bluetooth: ISO: add TX timestamping > https://git.kernel.org/bluetooth/bluetooth-next/c/3067d73e114f > - [v2,3/5] Bluetooth: L2CAP: add TX timestamping > https://git.kernel.org/bluetooth/bluetooth-next/c/e22f35ed23a7 > - [v2,4/5] Bluetooth: SCO: add TX timestamping > https://git.kernel.org/bluetooth/bluetooth-next/c/b7adccd0e8b6 > - [v2,5/5] Bluetooth: add BT_NO_ERRQUEUE_POLL socket option > (no matching commit) Ive left 5/5 out on purpose, let's have it behind an experimental flag so we can later rework it if necessary, I know it is a little annoying to have to do extra setup in order to test it but we are not supposed to introduce something like this without some safeguards that we can later rework if necessary. > You are awesome, thank you! > -- > Deet-doot-dot, I am a bot. > https://korg.docs.kernel.org/patchwork/pwbot.html > > > -- Luiz Augusto von Dentz
