Hi Jaganath, >>> --- >>> doc/mgmt-api.txt | 38 ++++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 38 insertions(+) >>> >>> diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt >>> index 69e84cd..b59bf0c 100644 >>> --- a/doc/mgmt-api.txt >>> +++ b/doc/mgmt-api.txt >>> @@ -2940,9 +2940,47 @@ Get PHY Information Command >>> LE 1M TX and LE 1M RX would be supported by default. >>> >>> This command is only available for LE capable controllers. >>> + It will return Not Supported otherwise. >>> + >>> + Possible errors: Not Supported >>> + Invalid Index >>> + >>> +Set Default PHY Command >>> +========================== >> >> I think the name “Set PHY Configuration” would be better. >> >>> + >>> + Command Code: 0x0044 >>> + Controller Index: <controller id> >>> + Command Parameters: Default_phy (1 Octet) >>> + Return Parameters: Current_phys (1 Octet) >> >> Returning the current selected PHYs is rather useless here. It would be exactly the same value we put in. However what might be useful is an event that indicates the change of the PHY Configuration. >> > > I will remove Current_phys. But do we really need PHY Configuration > Changed event since it > can be changed only by Set PHY Configuration command and user can > understand the currently > selected_phys based on whether command is succeeded or failed? and what about a 2nd mgmt user? We want to inform them that the configuration changed. They should be able to track selected PHYs without having to poll Get PHY Configuration. > We might need PHY changed event on a particular connection which > should correspond to > PHY Update Complete HCI Event. That is a different problem and I think that needs to be done via socket CMSG information. Regards Marcel -- 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
