Den 2012-11-05 14:25, Vinicius Costa Gomes skrev:
Hi,
Right now, we are using only one set of (hardcoded) connection
parameters for LE. I guess the first step to have different
connection parameters classes for different Profiles requirements
(think "Low Latency", "Low Power", etc.) is to have a nice set of
parameters. For that we need to measure and see which are the sweet
spots, This series aims to help the measuring part.
This is an idea so we can easily change the connection parameters
without need for recompiling the kernel side, so tests can be more
practical.
[snip]
Good idea to split them out as every single profile defines their own.
Have you
concidered what should happen if two LE connections to two different
profils should
happen at the same time and the connection parameters are different?
i.e. should bluez
maybe have a per-profile set of connection parameters?
Also make room in the struct for Preferred Connection Paramters (the
values read
from the peer DB after connection) as these can differ from the ones
the profile proposes.
--
Kim Schulz
--
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
