From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, michal.lowas-rzechonek@silvair.com,
brian.gix@intel.com
Subject: [PATCH BlueZ 1/8] doc: Cleanup API Provisioner1 interface
Date: Wed, 10 Jul 2019 16:07:50 -0700 [thread overview]
Message-ID: <20190710230757.8425-2-brian.gix@intel.com> (raw)
In-Reply-To: <20190710230757.8425-1-brian.gix@intel.com>
Modified the RequestProvData In and Out param list to eliminate
parameters which can be provided by the Node which owns the
procedure, and clean-up the actual error list.
---
doc/mesh-api.txt | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 893a1a6c0..0ac2fdfd1 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -365,7 +365,9 @@ Methods:
ScanResult() method on the app will be called with the result.
PossibleErrors:
+ org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.NotAuthorized
+ org.bluez.mesh.Error.Busy
void UnprovisionedScanCancel(void)
@@ -374,6 +376,7 @@ Methods:
(scanning) for unprovisioned devices in the area.
PossibleErrors:
+ org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.NotAuthorized
void AddNode(array{byte}[16] uuid)
@@ -860,7 +863,7 @@ Service unique name
Interface org.bluez.mesh.Provisioner1
Object path freely definable
- ScanResult(int8 rssi, array{byte} data)
+ void ScanResult(int16 rssi, array{byte} data)
The method is called from the bluetooth-meshd daemon when a
unique UUID has been seen during UnprovisionedScan() for
@@ -881,17 +884,17 @@ Object path freely definable
was recieved at a higher rssi power level.
- uint16 net_index, uint8 flags, uint32 iv_index, uint16 unicast
- RequestProvData()
+ uint16 net_index, uint16 unicast RequestProvData(uint8 count)
This method is implemented by a Provisioner capable application
and is called when the remote device has been fully
authenticated and confirmed.
+ The count parameter is the number of consecutive unicast
+ addresses the remote device is requesting.
+
Return Parameters are from the Mesh Profile Spec:
net_index - Subnet index of the net_key
- flags - Flags for IV_Update and Key Refresh
- iv_index - Current IvIndex being used on the network
unicast - Primary Unicast address of the new node
PossibleErrors:
--
2.14.5
next prev parent reply other threads:[~2019-07-10 23:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 23:07 [PATCH BlueZ 0/8] mesh: Provisioner Initiator added Brian Gix
2019-07-10 23:07 ` Brian Gix [this message]
2019-07-10 23:07 ` [PATCH BlueZ 2/8] mesh: Fix support for Provisioner Initiator Brian Gix
2019-07-11 7:10 ` Michał Lowas-Rzechonek
2019-07-10 23:07 ` [PATCH BlueZ 3/8] mesh: Add special Beacon handler for Provisioning Brian Gix
2019-07-10 23:07 ` [PATCH BlueZ 4/8] mesh: Expose mapping function for D-Bus errors Brian Gix
2019-07-10 23:07 ` [PATCH BlueZ 5/8] mesh: Expose resources needed by Management1 interface Brian Gix
2019-07-10 23:07 ` [PATCH BlueZ 6/8] mesh: Fix implementation of Provisioner Initiator Brian Gix
2019-07-11 7:33 ` Michał Lowas-Rzechonek
2019-07-11 15:48 ` Gix, Brian
2019-07-10 23:07 ` [PATCH BlueZ 7/8] mesh: Implement DBus Provisioning methods Brian Gix
2019-07-10 23:07 ` [PATCH BlueZ 8/8] test: This extends the mesh tool to exercise " 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=20190710230757.8425-2-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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 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).