Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp1254306pxp; Sun, 6 Mar 2022 09:44:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJzRFF+Hn3f4nbcLgwcbiMAw9dis3mMqAfZ8z0tf7jMXss8lrwuRTupt/ldcS3An+aa4ldMH X-Received: by 2002:a17:902:7296:b0:151:62b1:e2b0 with SMTP id d22-20020a170902729600b0015162b1e2b0mr8416501pll.165.1646588681238; Sun, 06 Mar 2022 09:44:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646588681; cv=none; d=google.com; s=arc-20160816; b=TX68MQCKmeCgRIce0Yt+xl1gMlVo5hTf6OstZ0qinbdKXsu5xU0PxcI3GaIdEd7Prp 5zELaKFpIQpwxxkFeCRg1DnAZa4ifhO3PpBb4wAIFaWHzlqNaVAcHWu+YFgcAGfyyRMu f1s87QDFisYOoCMCdaIBtW8cxazvY3W4D7sA/ckap+R+isL7PJFz83Z5EWYplY31Y/vs VY2/0aAxp+hOHb8GIBEutSDfR3S98LQQOVZwOhkKfq7sa2fNYdALZZ+nm8/3ydq166Nc eVExhL0dJv+N7HaFaot/Gsy2EwGR40ynlrcAdzAYsPRiEdMt1S/dRgD+tkU5qtJ6Fjdt noMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=Bt4d3nD1AIg+Hxqi4U8YqYR6NYxrHD4BudIZH93XuWA=; b=UUu5dUWpzPTV0bSmoMxYRrtpb/XzfcZPJAUxr4kTomL+qtZ1PA8sTwI0QiOvfqio27 diAWqf2/O6+qYJQmkndggdWpLEj/yQqyZDlQsLsryPZLRl/XEDMDIyZahMogEezm3L90 U1BDbdRV4e+amaJdCJ36qmDR9D8lmdhXfzcz79VcdtYxJylAFM8Vcy5uMVkspWlJW1Cw h6vuyfB2ENplUjQrb/o+WZmWuZBVvhhjwC2hsbqTDFohNMjv66XNywGg9B68aKJdt1WI yUj9BTNVFSq0sx84ZhFjOjp1SFGEyQ7wOkTfWsUO5v+NcH29Tv1ThR4Zk3yG5aCZX8JG WPyg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b3-20020a655783000000b00373cbfb95ccsi10084063pgr.438.2022.03.06.09.44.04; Sun, 06 Mar 2022 09:44:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232469AbiCFIuZ (ORCPT + 99 others); Sun, 6 Mar 2022 03:50:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53014 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230026AbiCFIuZ (ORCPT ); Sun, 6 Mar 2022 03:50:25 -0500 Received: from mail.holtmann.org (coyote.holtmann.net [212.227.132.17]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 32DA458E4A for ; Sun, 6 Mar 2022 00:49:33 -0800 (PST) Received: from smtpclient.apple (p5b3d2910.dip0.t-ipconnect.de [91.61.41.16]) by mail.holtmann.org (Postfix) with ESMTPSA id 3C986CECF9; Sun, 6 Mar 2022 09:49:32 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Subject: Re: [BlueZ PATCH v4 1/8] doc: Introduce the quality report command and event From: Marcel Holtmann In-Reply-To: Date: Sun, 6 Mar 2022 09:49:31 +0100 Cc: BlueZ , Luiz Augusto von Dentz , pali@kernel.org, chromeos-bluetooth-upstreaming@chromium.org Content-Transfer-Encoding: 7bit Message-Id: <44687930-3737-46E5-991C-F6C1910C48F7@holtmann.org> References: <20220215133636.2827039-1-josephsih@chromium.org> <666C5B97-A51C-48B9-AC91-0655C0D158B5@holtmann.org> <8AD1FDEA-CB22-4DEE-9ACE-CAAD3459DEF0@holtmann.org> To: Joseph Hwang X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Joseph, > What I plan to do about adapter power cycle for quality report: > > Step 1: At power off, do not clear the flag of HCI_QUALITY_REPORT in > hci_dev_clear_volatile_flags(). Will use HCI_QUALITY_REPORT to track > if the quality report is enabled before power off. Will also disable > the quality report explicitly in hci_sync.c:hci_dev_open_sync() just > before aosp_do_close() so that different vendor chips will have > quality off at power off. > > Step 2: In hci_sync.c:hci_dev_open_sync(), re-enable quality report > explicitly just after aosp_do_open() if HCI_QUALITY_REPORT is true so > that all vendor chips have quality back on at power on. > > If the quality report is not enabled before power cycle, > HCI_QUALITY_REPORT will always stay false. Nothing mentioned above > will be executed in this case. > > One thing is worth noting here. The HCI_QUALITY_REPORT represents > the host setting instead of the controller state. During power off, > the HCI_QUALITY_REPORT host setting remains true while the controller > state about quality report is turned off. This behavior is similar to > "wide-band-speech" whose setting remains true during power off. > > Does this sound good to you? If yes, I will append a new patch to > the next Series-version. Thanks! yes, that sounds good. Please provide the mgmt addition as first patches. Regards Marcel