Zephyr API Documentation 4.5.99
A Scalable Open Source RTOS
Loading...
Searching...
No Matches

FTP server RFCOMM registration structure. More...

#include <zephyr/bluetooth/classic/ftp.h>

Data Fields

struct bt_goep_transport_rfcomm_server server
 Underlying GOEP RFCOMM server.
int(* accept )(struct bt_conn *conn, struct bt_ftp_server_rfcomm *ftp_server_rfcomm, struct bt_ftp_server **ftp_server)
 Accept connection callback.

Detailed Description

FTP server RFCOMM registration structure.

Field Documentation

◆ accept

int(* bt_ftp_server_rfcomm::accept) (struct bt_conn *conn, struct bt_ftp_server_rfcomm *ftp_server_rfcomm, struct bt_ftp_server **ftp_server)

Accept connection callback.

Called for each new incoming RFCOMM connection. The application must return through ftp_server an FTP Server instance that has been registered through bt_ftp_server_register() before accept() returns; this is checked with an assertion. An instance stays registered after its transport has disconnected and can be returned again for a later connection: do not zero it or call bt_ftp_server_register() for it again (that returns -EALREADY). The returned instance must not be in use (its transport has not fully disconnected); this is checked with an assertion.

Parameters
connBluetooth connection object.
ftp_server_rfcommThe server registration structure.
ftp_serverOutput pointer for the allocated server instance.
Returns
0 on success, negative error code to reject the connection.

◆ server

struct bt_goep_transport_rfcomm_server bt_ftp_server_rfcomm::server

Underlying GOEP RFCOMM server.


The documentation for this struct was generated from the following file:
  • zephyr/bluetooth/classic/ftp.h