From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Wang Subject: Re: [PATCH v2 4/7] Bluetooth: Add new quirk for non-persistent setup settings Date: Tue, 22 May 2018 16:05:23 +0800 Message-ID: <1526976323.18877.47.camel@mtkswgap22> References: <1d6097f538b3182b2876ad48225ecd6e2d1b128c.1526374087.git.sean.wang@mediatek.com> <920B3BE9-3FE8-4AC6-8C5F-63B0E00182AC@holtmann.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <920B3BE9-3FE8-4AC6-8C5F-63B0E00182AC@holtmann.org> Sender: linux-kernel-owner@vger.kernel.org To: Marcel Holtmann Cc: Rob Herring , Mark Rutland , Johan Hedberg , devicetree , BlueZ development , linux-arm-kernel , linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org On Tue, 2018-05-22 at 09:21 +0200, Marcel Holtmann wrote: > Hi Sean, > [ ... ] > > - if (hci_dev_test_flag(hdev, HCI_SETUP)) { > > + if (hci_dev_test_flag(hdev, HCI_SETUP) || > > + test_bit(HCI_QUIRK_NON_PERSISTENT_SETUP, &hdev->quirks)) { > > hci_sock_dev_event(hdev, HCI_DEV_SETUP); > > I am not 100% sure that we want to send the HCI_DEV_SETUP event also multiple times. That is a userspace change that I would need to think about. We need to check create_monitor_event() and see what the btmon trace for this looks like. Can you send me a btmon -w trace.log when this change is active. > > Regards > > Marcel > Sure, I'll send you the trace.log with the change is active. Sean