All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iulia Tanasescu <iulia.tanasescu@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: claudia.rosu@nxp.com, mihai-octavian.urzica@nxp.com,
	andrei.istodorescu@nxp.com, luiz.dentz@gmail.com,
	Iulia Tanasescu <iulia.tanasescu@nxp.com>
Subject: [PATCH BlueZ 0/3] bap: Update bt_bap user data handling
Date: Thu, 20 Feb 2025 10:58:08 +0200	[thread overview]
Message-ID: <20250220085811.5033-1-iulia.tanasescu@nxp.com> (raw)

For the BAP Broadcast Assistant/Scan Delegator implementation
(BASS Client/Server), BAP sessions with Broadcasters are notified
in the bap_attached/bap_detached callbacks registered by BASS.
The associated btd_service must be available in the bt_bap
user data, to match the session with the Broadcaster device.

This patch updates the way bt_bap user data is handled, to ensure
the above.

Iulia Tanasescu (3):
  bap: Do not clear user_data before detaching bt_bap
  bap: Do not set adapter as bt_bap user_data
  bass: Add checks for bap user data

 profiles/audio/bap.c  |  5 +----
 profiles/audio/bass.c | 23 ++++++++++++++++++-----
 2 files changed, 19 insertions(+), 9 deletions(-)


base-commit: 264bf951f2d687f520898fa3e182291f1261e3a7
-- 
2.43.0


             reply	other threads:[~2025-02-20  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  8:58 Iulia Tanasescu [this message]
2025-02-20  8:58 ` [PATCH BlueZ 1/3] bap: Do not clear user_data before detaching bt_bap Iulia Tanasescu
2025-02-20 10:11   ` bap: Update bt_bap user data handling bluez.test.bot
2025-02-20  8:58 ` [PATCH BlueZ 2/3] bap: Do not set adapter as bt_bap user_data Iulia Tanasescu
2025-02-20  8:58 ` [PATCH BlueZ 3/3] bass: Add checks for bap user data Iulia Tanasescu
2025-02-21 16:50 ` [PATCH BlueZ 0/3] bap: Update bt_bap user data handling patchwork-bot+bluetooth

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=20250220085811.5033-1-iulia.tanasescu@nxp.com \
    --to=iulia.tanasescu@nxp.com \
    --cc=andrei.istodorescu@nxp.com \
    --cc=claudia.rosu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mihai-octavian.urzica@nxp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.