Skip to content

Bluetooth: Classic: GOEP: Support multiple OBEX sessions #95057

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 10, 2025
Merged

Bluetooth: Classic: GOEP: Support multiple OBEX sessions #95057

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9586adc
Bluetooth: Classic: GOEP: Support multiple OBEX sessions
lylezhu2012 Aug 27, 2025
893e6ad
Bluetooth: Classic: OBEX: Optimize MOPL configuration
lylezhu2012 Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 16 additions & 8 deletions include/zephyr/bluetooth/classic/goep.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,11 @@ struct bt_goep_transport_rfcomm_server {
* This callback is called whenever a new incoming GOEP connection requires
* authorization.
*
* Before returning the callback, @ref bt_goep::transport_ops should be initialized with
* valid address of type @ref bt_goep_transport_ops object. The field `mtu` of
* @ref bt_obex::rx could be passed with valid value. Or set it to zero, the mtu will be
* calculated according to @kconfig{CONFIG_BT_GOEP_RFCOMM_MTU}.
*
* @warning It is the responsibility of the caller to zero out the parent of the GOEP
* object.
*
Expand Down Expand Up @@ -184,10 +189,9 @@ int bt_goep_transport_rfcomm_server_register(struct bt_goep_transport_rfcomm_ser
* The GOEP object is passed (over an address of it) as second parameter, application should
* create transport dedicated GOEP object @ref bt_goep. Then pass to this API the location
* (address).
* Before calling the API, @ref bt_obex::client_ops and @ref bt_goep::transport_ops should
* be initialized with valid address of type @ref bt_obex_client_ops object and
* @ref bt_goep_transport_ops object. The field `mtu` of @ref bt_obex::rx could be passed with
* valid value. Or set it to zero, the mtu will be calculated according to
* Before calling the API, @ref bt_goep::transport_ops should be initialized with valid address
* of type @ref bt_goep_transport_ops object. The field `mtu` of @ref bt_obex::rx could be passed
* with valid value. Or set it to zero, the mtu will be calculated according to
* @kconfig{CONFIG_BT_GOEP_RFCOMM_MTU}.
* The RFCOMM channel is passed as third parameter. It is the RFCOMM channel of RFCOMM server of
* peer device.
Expand Down Expand Up @@ -241,6 +245,11 @@ struct bt_goep_transport_l2cap_server {
* This callback is called whenever a new incoming GOEP connection requires
* authorization.
*
* Before returning the callback, @ref bt_goep::transport_ops should be initialized with
* valid address of type @ref bt_goep_transport_ops object. The field `mtu` of
* @ref bt_obex::rx could be passed with valid value. Or set it to zero, the mtu will be
* calculated according to @kconfig{CONFIG_BT_GOEP_L2CAP_MTU}.
*
* @warning It is the responsibility of the caller to zero out the parent of the GOEP
* object.
*
Expand Down Expand Up @@ -286,10 +295,9 @@ int bt_goep_transport_l2cap_server_register(struct bt_goep_transport_l2cap_serve
* The GOEP object is passed (over an address of it) as second parameter, application should
* create transport dedicated GOEP object @ref bt_goep. Then pass to this API the location
* (address).
* Before calling the API, @ref bt_obex::client_ops and @ref bt_goep::transport_ops should
* be initialized with valid address of type @ref bt_obex_client_ops object and
* @ref bt_goep_transport_ops object. The field `mtu` of @ref bt_obex::rx could be passed with
* valid value. Or set it to zero, the mtu will be calculated according to
* Before calling the API, @ref bt_goep::transport_ops should be initialized with valid address
* of type @ref bt_goep_transport_ops object. The field `mtu` of @ref bt_obex::rx could be passed
* with valid value. Or set it to zero, the mtu will be calculated according to
* @kconfig{CONFIG_BT_GOEP_L2CAP_MTU}.
* The L2CAP PSM is passed as third parameter. It is the RFCOMM channel of RFCOMM server of peer
* device.
Expand Down
Loading