summaryrefslogtreecommitdiffstats
path: root/EventLogTags.logtags
diff options
context:
space:
mode:
authorPavlin Radoslavov <pavlin@google.com>2016-09-14 16:39:02 -0700
committerPavlin Radoslavov <pavlin@google.com>2016-09-16 21:46:23 +0000
commite1c8ed17c7a35510f00997ca329687f73cd193d8 (patch)
tree56f9303dc7a891edc56fd928da98158c65bf5fdf /EventLogTags.logtags
parent1e688824d969cab2c01130bdfd3283a2719c28e8 (diff)
downloadandroid_system_bt-e1c8ed17c7a35510f00997ca329687f73cd193d8.tar.gz
android_system_bt-e1c8ed17c7a35510f00997ca329687f73cd193d8.tar.bz2
android_system_bt-e1c8ed17c7a35510f00997ca329687f73cd193d8.zip
Add BT_HCI_UNKNOWN_MESSAGE_TYPE log event
If the received HCI type is unknown, then log an event and abort. The most likely reason for that to happen is if the UART stream is corrupted. We cannot recover from that, and there is not much else we can do. Also, fixed a bug in an HCI-related unit test that was exposed by the above change. Bug: 31432127 Change-Id: Ia888c485f177af4962268bf8f593b27fd7a4b080 (cherry picked from commit 27ec0c7824cf67b8a36bf5391734e6d2fc6207e2)
Diffstat (limited to 'EventLogTags.logtags')
-rw-r--r--EventLogTags.logtags1
1 files changed, 1 insertions, 0 deletions
diff --git a/EventLogTags.logtags b/EventLogTags.logtags
index 32493d812..dc1d239b7 100644
--- a/EventLogTags.logtags
+++ b/EventLogTags.logtags
@@ -35,3 +35,4 @@
1010000 bt_hci_timeout (opcode|1)
1010001 bt_config_source (opcode|1)
+1010002 bt_hci_unknown_type (hci_type|1)