Skip to content
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

[PW_SID:550611] [v3] bluetooth: Fix Advertisement Monitor Suspend/Resume #512

Closed
wants to merge 2 commits into from

Commits on Sep 21, 2021

  1. workflow: Add workflow files for ci

    This patch adds workflow files for ci:
    
    [schedule_work.yml]
     - The workflow file for scheduled work
     - Sync the repo with upstream repo and rebase the workflow branch
     - Review the patches in the patchwork and creates the PR if needed
    
    [ci.yml]
     - The workflow file for CI tasks
     - Run CI tests when PR is created
    
    Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
    tedd-an authored and BluezTestBot committed Sep 21, 2021
    Configuration menu
    Copy the full SHA
    4bcf66d View commit details
    Browse the repository at this point in the history
  2. bluetooth: Fix Advertisement Monitor Suspend/Resume

    During system suspend, advertisement monitoring is disabled by setting
    the HCI_VS_MSFT_LE_Set_Advertisement_Filter_Enable to False. This
    disables the monitoring during suspend, however, if the controller is
    monitoring a device, it sends HCI_VS_MSFT_LE_Monitor_Device_Event to
    indicate that the monitoring has been stopped for that particular
    device. This event may occur after suspend depending on the
    low_threshold_timeout and peer device advertisement frequency, which
    causes early wake up.
    
    Right way to disable the monitoring for suspend is by removing all the
    monitors before suspend and re-monitor after resume to ensure no events
    are received during suspend. This patch fixes this suspend/resume issue.
    
    Following tests are performed:
    - Add monitors before suspend and make sure DeviceFound gets triggered
    - Suspend the system and verify that all monitors are removed by kernel
      but not Released by bluetoothd
    - Wake up and verify that all monitors are added again and DeviceFound
      gets triggered
    
    Signed-off-by: Manish Mandlik <mmandlik@google.com>
    Reviewed-by: Archie Pusaka <apusaka@google.com>
    Reviewed-by: Miao-chen Chou <mcchou@google.com>
    liveusr authored and BluezTestBot committed Sep 21, 2021
    Configuration menu
    Copy the full SHA
    f4006b0 View commit details
    Browse the repository at this point in the history