Hi Arun,
On Mon, Jul 4, 2011 at 9:23 AM, Arun Kumar SINGH
<arunkr.singh@xxxxxxxxxxxxxx> wrote:
> Also how about setting profile specific LSTO? Proximity specs recommends this value to be 6X connection interval but I guess we may give the user/application some flexibility to play around on this? Same may be the case for connection interval, scan interval, latency values etc...I believe these values can be pretty much user/platform specific and user should have control over these ...
I still think we should try to come up with a "connection parameter
profile" (e.g. "low latency/fast connection", "low power",
"reconnection" etc.), instead of allowing applications to tune
specific values by hand. A couple of reasons:
* Exposing every single parameter to userspace will require one or
more mgmt commands which will just reflect the actual HCI commands.
This is usually not desirable (see Marcel's comments on this list
regarding the mgmt API being more "intelligent" than HCI)
* It will be too easy for custom/proprietary profiles to interfere
with core profiles (or with other custom/proprietary profiles).
* Some parameters are just "hints" for the controller, so there is no
need (IMHO) to use the exact same values recommended by the profile.
Note that (in adopted profiles), the connection parameters are usually
recommendations ("should") not requirements ("shall").
(I will use the word "mode" to avoid confusion below... better names
are welcome)
With just a few "modes", we should be able to cover all currently
adopted profiles. And we could easily extend by adding more "modes",
or a mgmt API to allow registering temporary modes whose parameters
can be checked against those of currently running profiles, making
sure they will not be affected. What do you think?
IIRC Ville had some comments/ideas regarding this. Ville?
Regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
