public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sean.wang@mediatek.com (Sean Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [SPAM]Re: [PATCH v2 4/7] Bluetooth: Add new quirk for non-persistent setup settings
Date: Wed, 23 May 2018 14:37:03 +0800	[thread overview]
Message-ID: <1527057423.4607.3.camel@mtkswgap22> (raw)
In-Reply-To: <1526976323.18877.47.camel@mtkswgap22>

On Tue, 2018-05-22 at 16:05 +0800, Sean Wang wrote:
> 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
> 

Hi, Marcel

Attached trace.log was captured when I inputted commands power on and
then off in bluetoothctl.

	Sean 

> 
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek

-------------- next part --------------
A non-text attachment was scrubbed...
Name: trace.log
Type: text/x-log
Size: 6573 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180523/db18fea4/attachment.bin>

  reply	other threads:[~2018-05-23  6:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  8:52 [PATCH v2 0/7] add support for Bluetooth on MT7622 SoC sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 1/7] dt-bindings: net: bluetooth: Add mediatek-bluetooth sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 2/7] serdev: add dev_pm_domain_attach|detach() sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 3/7] Bluetooth: Add new serdev based driver for UART attached controllers sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 4/7] Bluetooth: Add new quirk for non-persistent setup settings sean.wang at mediatek.com
2018-05-22  7:21   ` Marcel Holtmann
2018-05-22  8:05     ` Sean Wang
2018-05-23  6:37       ` Sean Wang [this message]
2018-05-23 12:31         ` Marcel Holtmann
2018-05-23 14:09           ` Sean Wang
2018-05-24  7:47             ` Marcel Holtmann
2018-05-24 15:30               ` Sean Wang
2018-05-30  6:26                 ` Marcel Holtmann
2018-06-12  9:58                   ` Sean Wang
2018-05-15  8:52 ` [PATCH v2 5/7] Bluetooth: Extend btuart driver for join more vendor devices sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 6/7] Bluetooth: mediatek: Add protocol support for MediaTek serial devices sean.wang at mediatek.com
2018-05-15  8:52 ` [PATCH v2 7/7] MAINTAINERS: add an entry for MediaTek Bluetooth driver sean.wang at mediatek.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1527057423.4607.3.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox