-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bugfix] Power manager now uses the last used profile_id to determine… #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
aa |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
N/A
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test
… the pm_action, instead of the first profile in the g_pm_cfg table. bug: v/50506 Rootcause: For example, if the previous SPP profile request entered idle mode, the device will enter sniff mode after 1 second. However, if the peer device later requests entering active mode, the power manager will query `g_pm_cfg` to find the matching current action and get the AG's `pm_action`. This results in using the AG's idle timeout of 7 seconds. But at this point, we want the power manager to use the SPP profile's `pm_action` with a timeout of 1 second. Signed-off-by: zhongzhijie1 <[email protected]>
… the pm_action, instead of the first profile in the g_pm_cfg table.
Rootcause: For example, if the previous SPP profile request entered idle mode, the device will enter sniff mode after 1 second. However, if the peer device later requests entering active mode, the power manager will query
g_pm_cfg
to find the matching current action and get the AG'spm_action
. This results in using the AG's idle timeout of 7 seconds. But at this point, we want the power manager to use the SPP profile'spm_action
with a timeout of 1 second.