All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Liu <yudiliu@google.com>
To: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	chromeos-bluetooth-upstreaming@chromium.org
Cc: Yu Liu <yudiliu@google.com>, Miao-chen Chou <mcchou@chromium.org>,
	Alain Michaud <alainm@chromium.org>
Subject: [RFC PATCH v1] doc/mgmt-api - Return connection direction in Device Connected Event
Date: Tue, 23 Mar 2021 14:56:15 -0700	[thread overview]
Message-ID: <20210323145555.RFC.v1.1.I530e1c3e621abd34c342d657df119e12e576d8a7@changeid> (raw)

When an MGMT_EV_DEVICE_CONNECTED event is reported back to the user
space we will set the flags to tell if the established connection is
outbound or not. This is useful for the user space to log better metrics
and error messages.

Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Reviewed-by: Alain Michaud <alainm@chromium.org>
---

Changes in v1:
- Initial change

 doc/mgmt-api.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index cab1fffc5..534272045 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -4085,7 +4085,7 @@ Device Connected Event
 	start using its identity.
 
 	The following bits are defined for the Flags parameter:
-		0	Reserved (not in use)
+		0	Outbound Connection
 		1	Legacy Pairing
 		2	Reserved (not in use)
 
-- 
2.31.0.291.g576ba9dcdaf-goog


             reply	other threads:[~2021-03-23 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 21:56 Yu Liu [this message]
2021-03-23 22:40 ` [RFC,v1] doc/mgmt-api - Return connection direction in Device Connected Event bluez.test.bot
2021-03-24  7:55 ` [RFC PATCH v1] " Marcel Holtmann

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=20210323145555.RFC.v1.1.I530e1c3e621abd34c342d657df119e12e576d8a7@changeid \
    --to=yudiliu@google.com \
    --cc=alainm@chromium.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mcchou@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.