From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, brian.gix@intel.com
Subject: [PATCH v6 00/10] Clean-up stale/unused hci_request.c code
Date: Mon, 1 Aug 2022 10:14:55 -0700 [thread overview]
Message-ID: <20220801171505.1271059-1-brian.gix@intel.com> (raw)
This will be a growing patch-set of conversions and dead-code removal
towards the goal of retiring hci_request.c
The patch sets will be split amoung the work queues and delayed work
queues as initialized in hci_request_setup(), with the ultimate goal of
eliminating hci_request.c entirely.
v2: Published
v3: Continuing work. This does include one conversion
(SCO configure_datapath) that has been tested with mgmt-tester and
sco-tester, but has not been tested with a controller with an
off-loadable codec.
v4: Clean-up checkpatch warnings.
v5: Remove remaining procedures from hci_request.c/h. Not that other
entities (notably amp.c, hci_event.c and hci_core.c) are still using
the hci_request mechanism, however, the mgmt-tester unit test only
currently execute opcode 0x1408 - HCI_OP_READ_ENC_KEY_SIZE during normal
testing.
v6: Fix CI reported errors, and recoded hci_abort_conn for optional sync
queue usage to fix some L2CAP test cases.
Brian Gix (10):
Bluetooth: Convert le_scan_disable timeout to hci_sync
Bluetooth: Rework le_scan_restart for hci_sync
Bluetooth: Delete unused hci_req_stop_discovery()
Bluetooth: Convert SCO configure_datapath to hci_sync
Bluetooth: Convert Interleave Scanning timeout to hci_sync
Bluetooth: Move Adv Instance timer to hci_sync
Bluetooth: Delete unreference hci_request code
Bluetooth: move hci_get_random_address() to hci_sync
Bluetooth: convert hci_update_adv_data to hci_sync
Bluetooth: Convert hci_abort_conn to hci_sync
include/net/bluetooth/hci_sync.h | 10 +-
net/bluetooth/hci_conn.c | 92 +-
net/bluetooth/hci_core.c | 4 +-
net/bluetooth/hci_event.c | 2 +-
net/bluetooth/hci_request.c | 2002 +-----------------------------
net/bluetooth/hci_request.h | 61 -
net/bluetooth/hci_sync.c | 567 ++++++++-
net/bluetooth/mgmt.c | 7 +-
8 files changed, 646 insertions(+), 2099 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-01 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 17:14 Brian Gix [this message]
2022-08-01 17:14 ` [PATCH v6 01/10] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-08-01 18:12 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-08-01 17:14 ` [PATCH v6 02/10] Bluetooth: Rework le_scan_restart for hci_sync Brian Gix
2022-08-01 17:14 ` [PATCH v6 03/10] Bluetooth: Delete unused hci_req_stop_discovery() Brian Gix
2022-08-01 17:14 ` [PATCH v6 04/10] Bluetooth: Convert SCO configure_datapath to hci_sync Brian Gix
2022-08-01 17:15 ` [PATCH v6 05/10] Bluetooth: Convert Interleave Scanning timeout " Brian Gix
2022-08-01 17:15 ` [PATCH v6 06/10] Bluetooth: Move Adv Instance timer " Brian Gix
2022-08-01 17:15 ` [PATCH v6 07/10] Bluetooth: Delete unreference hci_request code Brian Gix
2022-08-01 17:15 ` [PATCH v6 08/10] Bluetooth: move hci_get_random_address() to hci_sync Brian Gix
2022-08-01 17:15 ` [PATCH v6 09/10] Bluetooth: convert hci_update_adv_data " Brian Gix
2022-08-01 17:15 ` [PATCH v6 10/10] Bluetooth: Convert hci_abort_conn " Brian Gix
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=20220801171505.1271059-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).