From: Iulia Tanasescu <iulia.tanasescu@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Subject: [PATCH 0/1] Split bt_iso_qos into dedicated structures
Date: Mon, 20 Mar 2023 16:36:07 +0200 [thread overview]
Message-ID: <20230320143608.25399-1-iulia.tanasescu@nxp.com> (raw)
This patch splits the "bt_iso_qos" structure into dedicated
unicast and broadcast structures, so that ISO sockets
can be configured with dedicated QoS options.
This patch also adds some missing broadcast parameters
to the Sink and Source bt_iso_qos structures, so that
the parameters of the ISO Broadcast procedures that
take place in the Bluetooth kernel can be controlled
from the user space.
This patch depends on the BlueZ patch series
[PATCH BlueZ] Split bt_iso_qos into dedicated structures.
Iulia Tanasescu (1):
Split bt_iso_qos into dedicated structures
include/net/bluetooth/bluetooth.h | 47 ++++--
include/net/bluetooth/hci_core.h | 21 +--
net/bluetooth/hci_conn.c | 104 ++++++++-----
net/bluetooth/hci_event.c | 38 +++--
net/bluetooth/iso.c | 247 ++++++++++++++++++++++++++----
5 files changed, 346 insertions(+), 111 deletions(-)
base-commit: dd41882582a9ab19938598179386b81b793b4a5c
--
2.34.1
next reply other threads:[~2023-03-20 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 14:36 Iulia Tanasescu [this message]
2023-03-20 14:36 ` [PATCH 1/1] Bluetooth: Split bt_iso_qos into dedicated structures Iulia Tanasescu
2023-03-20 15:03 ` bluez.test.bot
2023-03-20 18:43 ` [PATCH 1/1] Bluetooth: " Luiz Augusto von Dentz
2023-03-21 8:08 ` Iulia Tanasescu
2023-03-22 15:23 ` Iulia Tanasescu
2023-03-22 17:38 ` Luiz Augusto von Dentz
2023-03-23 15:06 ` Iulia Tanasescu
2023-03-20 22:49 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 13:45 [PATCH 0/1] " Iulia Tanasescu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230320143608.25399-1-iulia.tanasescu@nxp.com \
--to=iulia.tanasescu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox