From: Rymarkiewicz Waldemar <waldemar.rymarkiewicz@tieto.com>
To: <johan.hedberg@gmail.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] bloodpressure: Add Blood Pressure API
Date: Thu, 28 Feb 2013 15:00:00 +0100 [thread overview]
Message-ID: <512F62E0.1030706@tieto.com> (raw)
In-Reply-To: <20130220075725.GA14731@x220>
Hi Johan,
>
> Please provide a proper commit message.
Sure. Change ID will be removed in v2.
>> +Methods RegisterWatcher(object agent)
>> +
>> + Registers a watcher to monitor blood pressure
>> + measurements. This agent will be notified about
>> + final pressure measurements.
>> +
> I'm a bit confused, what's the difference between "watcher" and "agent"?
> If they're the same thing just pick one term and stick to it.
Both mean the same, I guess. I've followed the description of existing
profiles thermometer, cscp, hrp.
All of them use 'agent' term for parameter and 'watcher' in description.
I will go for watcher it seems to be more relevant.
Methods RegisterWatcher(object watcher)
Registers a watcher to monitor blood pressure
measurements. This watcher will be notified about
final pressure measurements.
Is this ok?
>
>> +Blood Pressure Profile hierarchy
>> +================================
>> +
>> +Service org.bluez
>> +Interface org.bluez.BloodPressure1
>> +Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
>> +
>> +Properties boolean Intermediate [readonly]
>> +
>> + True if the device supports intermediate
>> + measurement notifications.
> What's the use of this property (and the interface)? I don't see how it
> relates to any other APIs in this specification.
The device may support notifications of intermediate cuff pressure. That
means during measurement it notifies the Collector what is current
pressure in cuff (my device sends 5 notifications per sec) until it is
ready to send final measurements (diastolic, systolic and MAP pressure).
Based on this property an app can decide if it wants to
EnableIntermediateMeasurement (CCC of right characteristic in configured
then) or not.
Similarly as in thermometer api.
Thanks,
/Waldek
next prev parent reply other threads:[~2013-02-28 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 11:21 [RFC] bloodpressure: Add Blood Pressure API Waldemar Rymarkiewicz
2013-02-20 7:57 ` Johan Hedberg
2013-02-28 14:00 ` Rymarkiewicz Waldemar [this message]
2013-02-28 14:18 ` Johan Hedberg
2013-03-01 8:34 ` Rymarkiewicz Waldemar
2013-03-01 8:39 ` Johan Hedberg
2013-03-01 12:11 ` Rymarkiewicz Waldemar
2013-03-01 13:37 ` Johan Hedberg
2013-03-02 3:09 ` Marcel Holtmann
2013-03-05 11:39 ` Rymarkiewicz Waldemar
2013-03-05 16:15 ` Marcel Holtmann
2013-03-06 8:51 ` Rymarkiewicz Waldemar
2013-03-13 6:51 ` Rymarkiewicz Waldemar
2013-05-08 7:41 ` Johan Hedberg
2013-05-16 12:17 ` Waldemar Rymarkiewicz
2013-05-16 12:22 ` Waldemar Rymarkiewicz
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=512F62E0.1030706@tieto.com \
--to=waldemar.rymarkiewicz@tieto.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.