| Message ID | 20250128165424.1044479-1-luiz.dentz@gmail.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | [BlueZ,v1,1/2] org.bluez.GattCharacteristic: Add confirmation support to AcquireNotify | expand |
| Context | Check | Description |
|---|---|---|
| tedd_an/pre-ci_am | success | Success |
| tedd_an/BuildEll | success | Build ELL PASS |
| tedd_an/BluezMake | success | Bluez Make PASS |
| tedd_an/MakeCheck | success | Bluez Make Check PASS |
| tedd_an/MakeDistcheck | success | Make Distcheck PASS |
| tedd_an/CheckValgrind | success | Check Valgrind PASS |
| tedd_an/CheckSmatch | success | CheckSparse PASS |
| tedd_an/bluezmakeextell | success | Make External ELL PASS |
| tedd_an/ScanBuild | success | Scan Build PASS |
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=928892 ---Test result--- Test Summary: CheckPatch PENDING 0.21 seconds GitLint PENDING 0.24 seconds BuildEll PASS 20.08 seconds BluezMake PASS 1559.01 seconds MakeCheck PASS 13.12 seconds MakeDistcheck PASS 156.65 seconds CheckValgrind PASS 212.54 seconds CheckSmatch PASS 267.63 seconds bluezmakeextell PASS 97.26 seconds IncrementalBuild PENDING 0.35 seconds ScanBuild PASS 844.59 seconds Details ############################## Test: CheckPatch - PENDING Desc: Run checkpatch.pl script Output: ############################## Test: GitLint - PENDING Desc: Run gitlint Output: ############################## Test: IncrementalBuild - PENDING Desc: Incremental build with the patches in the series Output: --- Regards, Linux Bluetooth
diff --git a/doc/org.bluez.GattCharacteristic.rst b/doc/org.bluez.GattCharacteristic.rst index 784445234fe5..7b1b3fbb5446 100644 --- a/doc/org.bluez.GattCharacteristic.rst +++ b/doc/org.bluez.GattCharacteristic.rst @@ -212,6 +212,11 @@ fd, uint16 AcquireNotify(dict options) [optional] To release the lock the client shall close the file descriptor, a HUP is generated in case the device is disconnected. + As a client if indication procedure is used the confirmation is + generated automatically once received, for a server if the file + descriptor is writable (POLLOUT) then upon receiving a confirmation from + the client one byte (0x01) is written to the file descriptor. + Note: the MTU can only be negotiated once and is symmetric therefore this method may be delayed in order to have the exchange MTU completed, because of that the file descriptor is closed during reconnections as
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> This adds confirmation support for AcquireNotify when indication procedure is used, also document the behavior of clients vs servers. --- doc/org.bluez.GattCharacteristic.rst | 5 +++++ 1 file changed, 5 insertions(+)