Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp167827pxp; Sat, 5 Mar 2022 00:59:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJwhxI1izO9Xc7uXN4IUOvBrEaT7MqE3zo9TNn6SqKUNqxHp497z/tnRoFlGnHGqWSHlPlKs X-Received: by 2002:a17:90b:1e53:b0:1bf:ac1:2a0b with SMTP id pi19-20020a17090b1e5300b001bf0ac12a0bmr13738719pjb.87.1646470765393; Sat, 05 Mar 2022 00:59:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646470765; cv=none; d=google.com; s=arc-20160816; b=EdZ60wfw2STVsWgv7PhcqVMKSNEtPIYQl+sPySMiDddhIjvAVgtOqzCyUvDFPLSZgF dlm7xO5IMBmxWJehRvF1Mwl+Rm7O8erq3sJuDAu8tXc46wdynQCnrohOcB8LLbtvaFvI v8H/UNc3kWMWM2H+Y++u7QUXpBBNZ5LDgdUx0v1VgR9p5vghfgyOc7pWns9jGOYcAxtc NpS7oCPNVkZQSlXfFYk7skRdZZE2/vej0ClZ2BBpXQMzZE7oCueZKR+gF42LKd8U77Qq OUrUJs6rvyCRkSF7KT9ovBFolm75N5GTWvguOpyMIFEaIeMfkKmArIHwz+iMf4/rjOLh wZPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=W/dFrJg+fXaLNA1NRQF8JSAMMhXMcsmxtldejIHxlqQ=; b=xqO3JaQdqrXkRgK1cZeVRNU+Gx0WPEORIg8aShJuuC4Ze3Yykqlk8QneUTK16qNiJ7 EYVpXuNs1xD3ZcISF6Hkxlb3N2lGnQzbN7WkOwm8ffFKTMZLl1nfOIskyM0kU0vtbEsO PtDfAcFT4s41Xz+iDJw7klCI0CyqMXQChzF4l5sENxhZ9FmGjTFV/Em8jKhr+ZAokaUN 0Z2SJqZvDRGzDHbGNNp7i99XOQzSkmkifEyY4iSHVy3jTzXNaaAkPsWUE9rGrytT3qnj 9LxteZqjnTgnGMABPK4ga0oOsena3IhI2Kn5RsOfldxb9Tqr+Ijf5xIDhPeDMwO1DLcx F1Cg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=MvlGq3VO; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l3-20020a63da43000000b00372ff807f9csi6653692pgj.279.2022.03.05.00.59.11; Sat, 05 Mar 2022 00:59:25 -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; dkim=pass header.i=@google.com header.s=20210112 header.b=MvlGq3VO; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230401AbiCEHnU (ORCPT + 99 others); Sat, 5 Mar 2022 02:43:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230378AbiCEHnU (ORCPT ); Sat, 5 Mar 2022 02:43:20 -0500 Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F326510AE for ; Fri, 4 Mar 2022 23:42:28 -0800 (PST) Received: by mail-yb1-xb2e.google.com with SMTP id g1so21271730ybe.4 for ; Fri, 04 Mar 2022 23:42:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=W/dFrJg+fXaLNA1NRQF8JSAMMhXMcsmxtldejIHxlqQ=; b=MvlGq3VOaqKS9jvPrOYlaE+iwZgqp7PI5zqp3mWo4uUDTyVpOdeV3bytQrdxNIyr1k Yx5gkuRxZPYtuL8uSd6Wtqc1PFjI++uvIGdecNLzr9w0BzvYFqyTrmbE1GMJsm/kVFk1 B+Hj5k4zX2+2rLLnUP5iS9l1LOe/FIipRxoTGnjgDkWfZV/A/eiCIIHjTh2tTYQmNiyb +Yusyozm1J6HJYqSfa1QlnkRktPSjdvDc1CNDw6XKLlIiwAGQ/wauRPNR3pJ7fJf/NG1 HU5vZeKee+LEkbzXvz4/vxVwo0MAWHckHtWfWycFq7A66Ol2w8NAJn8ttURlJl7wb8Bc 4UOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=W/dFrJg+fXaLNA1NRQF8JSAMMhXMcsmxtldejIHxlqQ=; b=hlReI6Px/TeL2KmqTUpIzF3J8hkg6V0Jywdbg3InAMU+/XiTXKejXSog/7vxeWCawO ER9tAVx3TcZh+mIB59ZjbdCYfE8v6vVKn3Ta+yLjUWjIpYSDv46x6tpFJ3KpkNE/Zof7 wdvwWbSzdpwFRqll6CXT9SyqCIxh8ORxFZLKGhdCJGFadXY5IDSaBORkvO6DjyE0wbRr 43w41siZ/cBOi6hQLYA2+CHaU0yGimnbPcuOgADeSytBWGF99OSgvh2Xl/Ay5Y/4lpmK au0jcxKy9XwiqrI3HBJm3dhN78w63xkWpyltdLkBtesLKJR3v+ZLE/HpJI3Ak/kWJ2ao XZTA== X-Gm-Message-State: AOAM531hnx82c49ZEmPHLkliEjehYdq7utw+Qs6IoqiP9nRX7XGjWnZW 1DG0TsKWvyhb5P1wVJ0vez71shok0IX/sQjuoHWnNY481v9pOQ== X-Received: by 2002:a5b:f10:0:b0:628:8420:d694 with SMTP id x16-20020a5b0f10000000b006288420d694mr1595447ybr.483.1646466147776; Fri, 04 Mar 2022 23:42:27 -0800 (PST) MIME-Version: 1.0 References: <20220215213519.v4.1.I2015b42d2d0a502334c9c3a2983438b89716d4f0@changeid> <9F696602-8BAC-479E-998D-118DDAE54445@holtmann.org> In-Reply-To: <9F696602-8BAC-479E-998D-118DDAE54445@holtmann.org> From: Joseph Hwang Date: Sat, 5 Mar 2022 15:42:16 +0800 Message-ID: Subject: Re: [PATCH v4 1/3] Bluetooth: aosp: surface AOSP quality report through mgmt To: Marcel Holtmann Cc: BlueZ , Luiz Augusto von Dentz , =?UTF-8?Q?Pali_Roh=C3=A1r?= , CrosBT Upstreaming , Archie Pusaka , "David S. Miller" , Jakub Kicinski , Johan Hedberg , LKML , netdev@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-18.1 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 Marcel, thank you for reviewing the patches! I have some questions and would like to confirm with you. Please read my replies in the lines below. Thanks! On Thu, Feb 17, 2022 at 8:41 PM Marcel Holtmann wrote= : > > Hi Joseph, > > > When receiving a HCI vendor event, the kernel checks if it is an > > AOSP bluetooth quality report. If yes, the event is sent to bluez > > user space through the mgmt socket. > > > > Signed-off-by: Joseph Hwang > > Reviewed-by: Archie Pusaka > > --- > > > > (no changes since v3) > > > > Changes in v3: > > - Rebase to resolve the code conflict. > > - Move aosp_quality_report_evt() from hci_event.c to aosp.c. > > - A new patch (3/3) is added to enable the quality report feature. > > > > Changes in v2: > > - Scrap the two structures defined in aosp.c and use constants for > > size check. > > - Do a basic size check about the quality report event. Do not pull > > data from the event in which the kernel has no interest. > > - Define vendor event prefixes with which vendor events of distinct > > vendor specifications can be clearly differentiated. > > - Use mgmt helpers to add the header and data to a mgmt skb. > > this unsolicited vendor event business is giving me a headache. I assume = it would be a lot simpler, but it doesn=E2=80=99t look like this. I need to= spent some rounds of thinking to give you good advice. Unfortunately since= we also want to support Intel vendor specific pieces, this is getting supe= r complicated. You have mentioned using hdev->hci_recv_quality_report to send the unsolicited events from the Intel driver in your comments in Patch 2/3. Just would like to confirm with you. Thanks. > > > include/net/bluetooth/hci_core.h | 5 ++ > > include/net/bluetooth/mgmt.h | 7 +++ > > net/bluetooth/aosp.c | 27 ++++++++++ > > net/bluetooth/aosp.h | 13 +++++ > > net/bluetooth/hci_event.c | 84 +++++++++++++++++++++++++++++++- > > net/bluetooth/mgmt.c | 20 ++++++++ > > net/bluetooth/msft.c | 14 ++++++ > > net/bluetooth/msft.h | 12 +++++ > > 8 files changed, 181 insertions(+), 1 deletion(-) > > > > diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/h= ci_core.h > > index f5caff1ddb29..ea83619ac4de 100644 > > --- a/include/net/bluetooth/hci_core.h > > +++ b/include/net/bluetooth/hci_core.h > > @@ -1864,6 +1864,8 @@ int mgmt_add_adv_patterns_monitor_complete(struct= hci_dev *hdev, u8 status); > > int mgmt_remove_adv_monitor_complete(struct hci_dev *hdev, u8 status); > > void mgmt_adv_monitor_device_lost(struct hci_dev *hdev, u16 handle, > > bdaddr_t *bdaddr, u8 addr_type); > > +int mgmt_quality_report(struct hci_dev *hdev, void *data, u32 data_len= , > > + u8 quality_spec); > > > > u8 hci_le_conn_update(struct hci_conn *conn, u16 min, u16 max, u16 late= ncy, > > u16 to_multiplier); > > @@ -1882,4 +1884,7 @@ void hci_copy_identity_address(struct hci_dev *hd= ev, bdaddr_t *bdaddr, > > > > #define TRANSPORT_TYPE_MAX 0x04 > > > > +#define QUALITY_SPEC_AOSP_BQR 0x0 > > +#define QUALITY_SPEC_INTEL_TELEMETRY 0x1 > > + > > #endif /* __HCI_CORE_H */ > > diff --git a/include/net/bluetooth/mgmt.h b/include/net/bluetooth/mgmt.= h > > index 3d26e6a3478b..83b602636262 100644 > > --- a/include/net/bluetooth/mgmt.h > > +++ b/include/net/bluetooth/mgmt.h > > @@ -1120,3 +1120,10 @@ struct mgmt_ev_adv_monitor_device_lost { > > __le16 monitor_handle; > > struct mgmt_addr_info addr; > > } __packed; > > + > > +#define MGMT_EV_QUALITY_REPORT 0x0031 > > +struct mgmt_ev_quality_report { > > + __u8 quality_spec; > > + __u32 data_len; > > + __u8 data[]; > > +} __packed; > > diff --git a/net/bluetooth/aosp.c b/net/bluetooth/aosp.c > > index 432ae3aac9e3..4a336433180d 100644 > > --- a/net/bluetooth/aosp.c > > +++ b/net/bluetooth/aosp.c > > @@ -199,3 +199,30 @@ int aosp_set_quality_report(struct hci_dev *hdev, = bool enable) > > else > > return disable_quality_report(hdev); > > } > > + > > +#define BLUETOOTH_QUALITY_REPORT_EV 0x58 > > + > > +/* The following LEN =3D 1-byte Sub-event code + 48-byte Sub-event Par= ameters */ > > +#define BLUETOOTH_QUALITY_REPORT_LEN 49 > > + > > +bool aosp_check_quality_report_len(struct sk_buff *skb) > > +{ > > + /* skb->len is allowed to be larger than BLUETOOTH_QUALITY_REPORT= _LEN > > + * to accommodate an additional Vendor Specific Parameter (vsp) f= ield. > > + */ > > + if (skb->len < BLUETOOTH_QUALITY_REPORT_LEN) { > > + BT_ERR("AOSP evt data len %d too short (%u expected)", > > + skb->len, BLUETOOTH_QUALITY_REPORT_LEN); > > + return false; > > + } > > + > > + return true; > > +} > > + > > +void aosp_quality_report_evt(struct hci_dev *hdev, void *data, > > + struct sk_buff *skb) > > +{ > > + if (aosp_has_quality_report(hdev) && aosp_check_quality_report_le= n(skb)) > > + mgmt_quality_report(hdev, skb->data, skb->len, > > + QUALITY_SPEC_AOSP_BQR); > > +} > > diff --git a/net/bluetooth/aosp.h b/net/bluetooth/aosp.h > > index 2fd8886d51b2..b21751e012de 100644 > > --- a/net/bluetooth/aosp.h > > +++ b/net/bluetooth/aosp.h > > @@ -10,6 +10,9 @@ void aosp_do_close(struct hci_dev *hdev); > > > > bool aosp_has_quality_report(struct hci_dev *hdev); > > int aosp_set_quality_report(struct hci_dev *hdev, bool enable); > > +bool aosp_check_quality_report_len(struct sk_buff *skb); > > +void aosp_quality_report_evt(struct hci_dev *hdev, void *data, > > + struct sk_buff *skb); > > > > #else > > > > @@ -26,4 +29,14 @@ static inline int aosp_set_quality_report(struct hci= _dev *hdev, bool enable) > > return -EOPNOTSUPP; > > } > > > > +static inline bool aosp_check_quality_report_len(struct sk_buff *skb) > > +{ > > + return false; > > +} > > + > > +static inline void aosp_quality_report_evt(struct hci_dev *hdev, void= *data, > > + struct sk_buff *skb) > > +{ > > +} > > + > > #endif > > diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c > > index 63b925921c87..6468ea0f71bd 100644 > > --- a/net/bluetooth/hci_event.c > > +++ b/net/bluetooth/hci_event.c > > @@ -37,6 +37,7 @@ > > #include "smp.h" > > #include "msft.h" > > #include "eir.h" > > +#include "aosp.h" > > > > #define ZERO_KEY "\x00\x00\x00\x00\x00\x00\x00\x00" \ > > "\x00\x00\x00\x00\x00\x00\x00\x00" > > @@ -4241,6 +4242,87 @@ static void hci_num_comp_blocks_evt(struct hci_d= ev *hdev, void *data, > > queue_work(hdev->workqueue, &hdev->tx_work); > > } > > > > +/* Define the fixed vendor event prefixes below. > > + * Note: AOSP HCI Requirements use 0x54 and up as sub-event codes with= out > > + * actually defining a vendor prefix. Refer to > > + * https://source.android.com/devices/bluetooth/hci_requirements > > + * Hence, the other vendor event prefixes should not use the sam= e > > + * space to avoid collision. > > + */ > > +static unsigned char AOSP_BQR_PREFIX[] =3D { 0x58 }; > > + > > +/* Some vendor prefixes are fixed values and lengths. */ > > +#define FIXED_EVT_PREFIX(_prefix, _vendor_func) = \ > > +{ \ > > + .prefix =3D _prefix, = \ > > + .prefix_len =3D sizeof(_prefix), = \ > > + .vendor_func =3D _vendor_func, = \ > > + .get_prefix =3D NULL, = \ > > + .get_prefix_len =3D NULL, = \ > > +} > > + > > +/* Some vendor prefixes are only available at run time. The > > + * values and lengths are variable. > > + */ > > +#define DYNAMIC_EVT_PREFIX(_prefix_func, _prefix_len_func, _vendor_fun= c)\ > > +{ \ > > + .prefix =3D NULL, = \ > > + .prefix_len =3D 0, = \ > > + .vendor_func =3D _vendor_func, = \ > > + .get_prefix =3D _prefix_func, = \ > > + .get_prefix_len =3D _prefix_len_func, = \ > > +} > > + > > +/* Every distinct vendor specification must have a well-defined vendor > > + * event prefix to determine if a vendor event meets the specification= . > > + * If an event prefix is fixed, it should be delcared with FIXED_EVT_P= REFIX. > > + * Otherwise, DYNAMIC_EVT_PREFIX should be used for variable prefixes. > > + */ > > +struct vendor_event_prefix { > > + __u8 *prefix; > > + __u8 prefix_len; > > + void (*vendor_func)(struct hci_dev *hdev, void *data, > > + struct sk_buff *skb); > > + __u8 *(*get_prefix)(struct hci_dev *hdev); > > + __u8 (*get_prefix_len)(struct hci_dev *hdev); > > +} evt_prefixes[] =3D { > > + FIXED_EVT_PREFIX(AOSP_BQR_PREFIX, aosp_quality_report_evt), > > + DYNAMIC_EVT_PREFIX(get_msft_evt_prefix, get_msft_evt_prefix_len, > > + msft_vendor_evt), > > + > > + /* end with a null entry */ > > + {}, > > +}; > > + > > +static void hci_vendor_evt(struct hci_dev *hdev, void *data, > > + struct sk_buff *skb) > > +{ > > + int i; > > + __u8 *prefix; > > + __u8 prefix_len; > > + > > + for (i =3D 0; evt_prefixes[i].vendor_func; i++) { > > + if (evt_prefixes[i].get_prefix) > > + prefix =3D evt_prefixes[i].get_prefix(hdev); > > + else > > + prefix =3D evt_prefixes[i].prefix; > > + > > + if (evt_prefixes[i].get_prefix_len) > > + prefix_len =3D evt_prefixes[i].get_prefix_len(hde= v); > > + else > > + prefix_len =3D evt_prefixes[i].prefix_len; > > + > > + if (!prefix || prefix_len =3D=3D 0) > > + continue; > > + > > + /* Compare the raw prefix data directly. */ > > + if (!memcmp(prefix, skb->data, prefix_len)) { > > + evt_prefixes[i].vendor_func(hdev, data, skb); > > + break; > > + } > > + } > > +} > > + > > static void hci_mode_change_evt(struct hci_dev *hdev, void *data, > > struct sk_buff *skb) > > { > > @@ -6844,7 +6926,7 @@ static const struct hci_ev { > > HCI_EV(HCI_EV_NUM_COMP_BLOCKS, hci_num_comp_blocks_evt, > > sizeof(struct hci_ev_num_comp_blocks)), > > /* [0xff =3D HCI_EV_VENDOR] */ > > - HCI_EV_VL(HCI_EV_VENDOR, msft_vendor_evt, 0, HCI_MAX_EVENT_SIZE), > > + HCI_EV_VL(HCI_EV_VENDOR, hci_vendor_evt, 0, HCI_MAX_EVENT_SIZE), > > }; > > I was thinking along the lines like this: > > HCI_EV_VND(evt_prefix, evt_prefix_len, callback), > > So that we in the end can do things like this: > > HCI_EV_VL({ 0x58 }, 1, aosp_quality_report_evt), > I wish I could use a macro as simple as HCI_EV_VND(evt_prefix, evt_prefix_len, callback). However, I do not have a clean method to handle the dynamic msft vendor prefix of which the value and length are not known until runtime. Do you have any suggestions here? > > > > > > static void hci_event_func(struct hci_dev *hdev, u8 event, struct sk_bu= ff *skb, > > diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c > > index 914e2f2d3586..5e48576041fb 100644 > > --- a/net/bluetooth/mgmt.c > > +++ b/net/bluetooth/mgmt.c > > @@ -4389,6 +4389,26 @@ static int set_exp_feature(struct sock *sk, stru= ct hci_dev *hdev, > > MGMT_STATUS_NOT_SUPPORTED); > > } > > > > +int mgmt_quality_report(struct hci_dev *hdev, void *data, u32 data_len= , > > + u8 quality_spec) > > +{ > > + struct mgmt_ev_quality_report *ev; > > + struct sk_buff *skb; > > + > > + skb =3D mgmt_alloc_skb(hdev, MGMT_EV_QUALITY_REPORT, > > + sizeof(*ev) + data_len); > > + if (!skb) > > + return -ENOMEM; > > + > > + ev =3D skb_put(skb, sizeof(*ev)); > > + ev->quality_spec =3D quality_spec; > > + ev->data_len =3D data_len; > > + skb_put_data(skb, data, data_len); > > + > > + return mgmt_event_skb(skb, NULL); > > +} > > +EXPORT_SYMBOL(mgmt_quality_report); > > + > > I know what you want to do, but I can not let you call mgmt_ function fro= m a driver. We need to make this cleaner and abstract so that the driver ha= s a proper path to report it to hci_core and that decides then to send the = report or not. Will set up hdev->hci_recv_quality_report as you mentioned in comments in Patch 2/3. > > > > static int get_device_flags(struct sock *sk, struct hci_dev *hdev, void= *data, > > u16 data_len) > > { > > diff --git a/net/bluetooth/msft.c b/net/bluetooth/msft.c > > index 9a3d77d3ca86..3edf64baf479 100644 > > --- a/net/bluetooth/msft.c > > +++ b/net/bluetooth/msft.c > > @@ -731,6 +731,20 @@ static void msft_monitor_device_evt(struct hci_dev= *hdev, struct sk_buff *skb) > > handle_data->mgmt_handle); > > } > > > > +__u8 *get_msft_evt_prefix(struct hci_dev *hdev) > > +{ > > + struct msft_data *msft =3D hdev->msft_data; > > + > > + return msft->evt_prefix; > > +} > > + > > +__u8 get_msft_evt_prefix_len(struct hci_dev *hdev) > > +{ > > + struct msft_data *msft =3D hdev->msft_data; > > + > > + return msft->evt_prefix_len; > > +} > > + > > So I wonder if this should be moved directly into hci_dev under CONFIG_BT= _MSFTEXT check. Luiz also needs to have a look at this. This is unfortunate= ly getting a bit nasty now. We need to find a clean solution, otherwise the= next vendor thing is blowing up in our face. My understanding is that static inline hci_set_msft_opcode() under CONFIG_BT_MSFTEXT is placed in hci_core.h because drivers need to call it. Here, get_msft_evt_prefix() and get_msft_evt_prefix_len() are not to be called by drivers. Do we still need to move them into hci_core.h? Please let me know if I have any misunderstanding. Thanks. > > > > void msft_vendor_evt(struct hci_dev *hdev, void *data, struct sk_buff *= skb) > > { > > struct msft_data *msft =3D hdev->msft_data; > > diff --git a/net/bluetooth/msft.h b/net/bluetooth/msft.h > > index afcaf7d3b1cb..a354ebf61fed 100644 > > --- a/net/bluetooth/msft.h > > +++ b/net/bluetooth/msft.h > > @@ -27,6 +27,8 @@ int msft_set_filter_enable(struct hci_dev *hdev, bool= enable); > > int msft_suspend_sync(struct hci_dev *hdev); > > int msft_resume_sync(struct hci_dev *hdev); > > bool msft_curve_validity(struct hci_dev *hdev); > > +__u8 *get_msft_evt_prefix(struct hci_dev *hdev); > > +__u8 get_msft_evt_prefix_len(struct hci_dev *hdev); > > > > #else > > > > @@ -77,4 +79,14 @@ static inline bool msft_curve_validity(struct hci_de= v *hdev) > > return false; > > } > > > > +static inline __u8 *get_msft_evt_prefix(struct hci_dev *hdev) > > +{ > > + return NULL; > > +} > > + > > +static inline __u8 get_msft_evt_prefix_len(struct hci_dev *hdev) > > +{ > > + return 0; > > +} > > + > > #endif > > Regards > > Marcel > Regards, --=20 Joseph Shyh-In Hwang Email: josephsih@google.com