Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
Subsystems (2)
PATCH v7 1/3 Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
From: Sean Wang <[email protected]>
Use readx_poll_timeout instead of open coding to poll the hardware reset status until it is done.
---
v2: use 20ms as the unit to poll according to the requirement of
readx_poll_timeout
v3: refine btusb_mtk_reset_done and drop the necessary error check
in btusb_mtk_cmd_timeout
v4, v5, v6 and v7: rebase onto the latest codebase
--- drivers/bluetooth/btusb.c | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-)
drivers/bluetooth/btusb.c +15 -15
@@ -2654,8 +2654,6 @@ static int btusb_recv_event_realtek(struct hci_dev *hdev, struct sk_buff *skb)#define MTK_EP_RST_OPT 0x74011890#define MTK_EP_RST_IN_OUT_OPT 0x00010001#define MTK_BT_RST_DONE 0x00000100 -#define MTK_BT_RESET_WAIT_MS 100 -#define MTK_BT_RESET_NUM_TRIES 10#define MTK_BT_RESET_REG_CONNV3 0x70028610#define MTK_BT_READ_DEV_ID 0x70010200
@@ -3029,6 +3027,16 @@ static int btusb_mtk_id_get(struct btusb_data *data, u32 reg, u32 *id)return btusb_mtk_reg_read (data, reg, id); } +static u32 btusb_mtk_reset_done (struct hci_dev *hdev) +{ +struct btusb_data *data =hci_get_drvdata (hdev); +u32 val =0 ; + +btusb_mtk_uhw_reg_read (data,MTK_BT_MISC , &val); + +return val &MTK_BT_RST_DONE ; +} +static int btusb_mtk_setup (struct hci_dev *hdev) {struct btusb_data *data =hci_get_drvdata (hdev);
@@ -3229,7 +3237,7 @@ static void btusb_mtk_cmd_timeout(struct hci_dev *hdev) {struct btusb_data *data =hci_get_drvdata (hdev);u32 val; -int err, retry =0 ; +int err;struct btmediatek_data *mediatek;/* It's MediaTek specific bluetooth reset mechanism via USB */
@@ -3281,18 +3289,10 @@ static void btusb_mtk_cmd_timeout(struct hci_dev *hdev)btusb_mtk_uhw_reg_read (data,MTK_BT_SUBSYS_RST , &val); } -/* Poll the register until reset is completed */ -do { -btusb_mtk_uhw_reg_read (data,MTK_BT_MISC , &val); -if (val &MTK_BT_RST_DONE ) { -bt_dev_dbg (hdev,"Bluetooth Reset Successfully" ); -break ; - } - -bt_dev_dbg (hdev,"Polling Bluetooth Reset CR" ); - retry++; -msleep (MTK_BT_RESET_WAIT_MS ); - }while (retry <MTK_BT_RESET_NUM_TRIES ); + err =readx_poll_timeout (btusb_mtk_reset_done, hdev, val, + val &MTK_BT_RST_DONE ,20000 ,1000000 ); +if (err <0 ) +bt_dev_err (hdev,"Reset timeout" );btusb_mtk_id_get (data,0x70010200 , &val);if (!val)
Signature · 1 line
2.25.1
PATCH v7 2/3 Bluetooth: btmtk: introduce btmtk reset work
From: Jing Cai <[email protected]>
Introduce btmtk_reset_work which can be called whenever the firmware abort, HCI command timeout, other fatal error happen.
---
v2, v3, v4: rebase onto the latest codebase
v5: reset the device on hdev basis and use hci_cmd_sync_queue to
schedule reset work
v6 and v7: rebase onto the latest codebase
--- drivers/bluetooth/btmtk.c | 15 ++++ drivers/bluetooth/btmtk.h | 8 +++ drivers/bluetooth/btusb.c | 145 +++++++++++++++++++------------------- 3 files changed, 97 insertions(+), 71 deletions(-)
drivers/bluetooth/btmtk.c +15 -0
@@ -280,6 +280,21 @@ int btmtk_set_bdaddr(struct hci_dev *hdev, const bdaddr_t *bdaddr) }EXPORT_SYMBOL_GPL (btmtk_set_bdaddr); +void btmtk_reset_sync (struct hci_dev *hdev) +{ +struct btmediatek_data *reset_work =hci_get_priv (hdev); +int err; + +hci_dev_lock (hdev); + + err =hci_cmd_sync_queue (hdev, reset_work->reset_sync,NULL ,NULL ); +if (err) +bt_dev_err (hdev,"failed to reset (%d)" , err); + +hci_dev_unlock (hdev); +} +EXPORT_SYMBOL_GPL (btmtk_reset_sync); +MODULE_AUTHOR ("Sean Wang <[email protected]>" );MODULE_AUTHOR ("Mark Chen <[email protected]>" );MODULE_DESCRIPTION ("Bluetooth support for MediaTek devices ver " VERSION );
drivers/bluetooth/btmtk.h +8 -0
@@ -120,8 +120,11 @@ struct btmtk_hci_wmt_params {u32 *status; }; +typedef int (*btmtk_reset_sync_func_t )(struct hci_dev *,void *); +struct btmediatek_data {u32 dev_id; +btmtk_reset_sync_func_t reset_sync; }; typedef int (*wmt_cmd_sync_func_t)(struct hci_dev *,
@@ -136,6 +139,8 @@ int btmtk_setup_firmware_79xx(struct hci_dev *hdev, const char *fwname,int btmtk_setup_firmware (struct hci_dev *hdev,const char *fwname,wmt_cmd_sync_func_t wmt_cmd_sync); + +void btmtk_reset_sync (struct hci_dev *hdev);#else static inline int btmtk_set_bdaddr(struct hci_dev *hdev,
@@ -156,4 +161,7 @@ static int btmtk_setup_firmware(struct hci_dev *hdev, const char *fwname, return -EOPNOTSUPP; } +static void btmtk_reset_sync (struct hci_dev *hdev) +{ +}#endif
drivers/bluetooth/btusb.c +74 -71
169 lines not on this page · raw message
Signature · 1 line
2.25.1
Luiz Augusto von Dentz
maintainerRe: [PATCH v7 2/3] Bluetooth: btmtk: introduce btmtk reset work
Hi Sean,
Quoted 86 lines · On Mon, Jun 26, 2023 at 1:41 PM <[email protected]> wrote:
From: Jing Cai <[email protected]>
Introduce
btmtk_reset_workwhich can be called whenever the firmware abort, HCI command timeout, other fatal error happen.Co-developed-by Chris Lu <[email protected]>Signed-off-by Chris Lu <[email protected]>Co-developed-by Sean Wang <[email protected]>Signed-off-by Sean Wang <[email protected]>Signed-off-by Jing Cai <[email protected]>---
v2, v3, v4: rebase onto the latest codebase
v5: reset the device on hdev basis and usehci_cmd_sync_queueto
schedule reset work
v6 and v7: rebase onto the latest codebase--- drivers/bluetooth/btmtk.c | 15 ++++ drivers/bluetooth/btmtk.h | 8 +++ drivers/bluetooth/btusb.c | 145 +++++++++++++++++++------------------- 3 files changed, 97 insertions(+), 71 deletions(-)drivers/bluetooth/btmtk.c +15
-0@@ -280,6 +280,21 @@ int btmtk_set_bdaddr(struct hci_dev *hdev, const bdaddr_t *bdaddr) }EXPORT_SYMBOL_GPL (btmtk_set_bdaddr); +void btmtk_reset_sync (struct hci_dev *hdev) +{ +struct btmediatek_data *reset_work =hci_get_priv (hdev); +int err; + +hci_dev_lock (hdev); + + err =hci_cmd_sync_queue (hdev, reset_work->reset_sync,NULL ,NULL ); +if (err) +bt_dev_err (hdev,"failed to reset (%d)" , err); + +hci_dev_unlock (hdev); +} +EXPORT_SYMBOL_GPL (btmtk_reset_sync); +MODULE_AUTHOR ("Sean Wang <[email protected]>" );MODULE_AUTHOR ("Mark Chen <[email protected]>" );MODULE_DESCRIPTION ("Bluetooth support for MediaTek devices ver " VERSION );drivers/bluetooth/btmtk.h +8
-0@@ -120,8 +120,11 @@ struct btmtk_hci_wmt_params {u32 *status; }; +typedef int (*btmtk_reset_sync_func_t )(struct hci_dev *,void *); +struct btmediatek_data {u32 dev_id; +btmtk_reset_sync_func_t reset_sync; }; typedef int (*wmt_cmd_sync_func_t)(struct hci_dev *,@@ -136,6 +139,8 @@ int btmtk_setup_firmware_79xx(struct hci_dev *hdev, const char *fwname,int btmtk_setup_firmware (struct hci_dev *hdev,const char *fwname,wmt_cmd_sync_func_t wmt_cmd_sync); + +void btmtk_reset_sync (struct hci_dev *hdev);#else static inline int btmtk_set_bdaddr(struct hci_dev *hdev,@@ -156,4 +161,7 @@ static int btmtk_setup_firmware(struct hci_dev *hdev, const char *fwname, return -EOPNOTSUPP; } +static void btmtk_reset_sync (struct hci_dev *hdev) +{ +}#endif drivers/bluetooth/btusb.c +0
-0
drivers/bluetooth/btusb.c static u32 btusb_mtk_reset_done(struct hci_dev *hdev) · line 3040
Quoted 4 lines
drivers/bluetooth/btusb.c +1
-0@@ -3037,6 +3037,78 @@ static u32 btusb_mtk_reset_done(struct hci_dev *hdev)return val &MTK_BT_RST_DONE ; } +static int btusb_mtk_reset_work (struct hci_dev *hdev,void *rst_data)
You can probably drop _work suffix since it no longer runs on its own dedicated work.
Quoted 171 lines
drivers/bluetooth/btusb.c +73
-72+{ +struct btusb_data *data =hci_get_drvdata (hdev); +struct btmediatek_data *mediatek; +u32 val; +int err; + +/* It's MediaTek specific bluetooth reset mechanism via USB */ +if (test_and_set_bit (BTUSB_HW_RESET_ACTIVE , &data->flags)) { +bt_dev_err (hdev,"last reset failed? Not resetting again" ); +return -EBUSY ; + } + + err =usb_autopm_get_interface (data->intf); +if (err <0 ) +return err; + +btusb_stop_traffic (data); +usb_kill_anchored_urbs (&data->tx_anchor); + mediatek =hci_get_priv (hdev); + +if (mediatek->dev_id ==0x7925 ) { +btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); + val |= (1 <<5 ); +btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); +btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); + val &=0xFFFF00FF ; + val |= (1 <<13 ); +btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); +btusb_mtk_uhw_reg_write (data,MTK_EP_RST_OPT ,0x00010001 ); +btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); + val |= (1 <<0 ); +btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); +btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT ,0x000000FF ); +btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT , &val); +btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT1 ,0x000000FF ); +btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT1 , &val); +msleep (100 ); + }else { +/* It's Device EndPoint Reset Option Register */ +bt_dev_dbg (hdev,"Initiating reset mechanism via uhw" ); +btusb_mtk_uhw_reg_write (data,MTK_EP_RST_OPT ,MTK_EP_RST_IN_OUT_OPT ); +btusb_mtk_uhw_reg_read (data,MTK_BT_WDT_STATUS , &val); + +/* Reset the bluetooth chip via USB interface. */ +btusb_mtk_uhw_reg_write (data,MTK_BT_SUBSYS_RST ,1 ); +btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT ,0x000000FF ); +btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT , &val); +btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT1 ,0x000000FF ); +btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT1 , &val); +/* MT7921 need to delay 20ms between toggle reset bit */ +msleep (20 ); +btusb_mtk_uhw_reg_write (data,MTK_BT_SUBSYS_RST ,0 ); +btusb_mtk_uhw_reg_read (data,MTK_BT_SUBSYS_RST , &val); + } + + err =readx_poll_timeout (btusb_mtk_reset_done, hdev, val, + val &MTK_BT_RST_DONE ,20000 ,1000000 ); +if (err <0 ) +bt_dev_err (hdev,"Reset timeout" ); + +btusb_mtk_id_get (data,0x70010200 , &val); +if (!val) +bt_dev_err (hdev,"Can't get device id, subsys reset fail." ); + +usb_queue_reset_device (data->intf); + +clear_bit (BTUSB_HW_RESET_ACTIVE , &data->flags); + +return err; +} +static int btusb_mtk_setup (struct hci_dev *hdev) {struct btusb_data *data =hci_get_drvdata (hdev);@@ -3076,6 +3148,7 @@ static int btusb_mtk_setup(struct hci_dev *hdev) mediatek =hci_get_priv (hdev); mediatek->dev_id = dev_id; + mediatek->reset_sync = btusb_mtk_reset_work;switch (dev_id) {case 0x7663 :@@ -3233,76 +3306,6 @@ static int btusb_mtk_shutdown(struct hci_dev *hdev)return 0 ; } -static void btusb_mtk_cmd_timeout (struct hci_dev *hdev) -{ -struct btusb_data *data =hci_get_drvdata (hdev); -u32 val; -int err; -struct btmediatek_data *mediatek; - -/* It's MediaTek specific bluetooth reset mechanism via USB */ -if (test_and_set_bit (BTUSB_HW_RESET_ACTIVE , &data->flags)) { -bt_dev_err (hdev,"last reset failed? Not resetting again" ); -return ; - } - - err =usb_autopm_get_interface (data->intf); -if (err <0 ) -return ; - -btusb_stop_traffic (data); -usb_kill_anchored_urbs (&data->tx_anchor); - mediatek =hci_get_priv (hdev); - -if (mediatek->dev_id ==0x7925 ) { -btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); - val |= (1 <<5 ); -btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); -btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); - val &=0xFFFF00FF ; - val |= (1 <<13 ); -btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); -btusb_mtk_uhw_reg_write (data,MTK_EP_RST_OPT ,0x00010001 ); -btusb_mtk_uhw_reg_read (data,MTK_BT_RESET_REG_CONNV3 , &val); - val |= (1 <<0 ); -btusb_mtk_uhw_reg_write (data,MTK_BT_RESET_REG_CONNV3 , val); -btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT ,0x000000FF ); -btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT , &val); -btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT1 ,0x000000FF ); -btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT1 , &val); -msleep (100 ); - }else { -/* It's Device EndPoint Reset Option Register */ -bt_dev_dbg (hdev,"Initiating reset mechanism via uhw" ); -btusb_mtk_uhw_reg_write (data,MTK_EP_RST_OPT ,MTK_EP_RST_IN_OUT_OPT ); -btusb_mtk_uhw_reg_read (data,MTK_BT_WDT_STATUS , &val); - -/* Reset the bluetooth chip via USB interface. */ -btusb_mtk_uhw_reg_write (data,MTK_BT_SUBSYS_RST ,1 ); -btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT ,0x000000FF ); -btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT , &val); -btusb_mtk_uhw_reg_write (data,MTK_UDMA_INT_STA_BT1 ,0x000000FF ); -btusb_mtk_uhw_reg_read (data,MTK_UDMA_INT_STA_BT1 , &val); -/* MT7921 need to delay 20ms between toggle reset bit */ -msleep (20 ); -btusb_mtk_uhw_reg_write (data,MTK_BT_SUBSYS_RST ,0 ); -btusb_mtk_uhw_reg_read (data,MTK_BT_SUBSYS_RST , &val); - } - - err =readx_poll_timeout (btusb_mtk_reset_done, hdev, val, - val &MTK_BT_RST_DONE ,20000 ,1000000 ); -if (err <0 ) -bt_dev_err (hdev,"Reset timeout" ); - -btusb_mtk_id_get (data,0x70010200 , &val); -if (!val) -bt_dev_err (hdev,"Can't get device id, subsys reset fail." ); - -usb_queue_reset_device (data->intf); - -clear_bit (BTUSB_HW_RESET_ACTIVE , &data->flags); -} -static int btusb_recv_acl_mtk (struct hci_dev *hdev,struct sk_buff *skb) {struct btusb_data *data =hci_get_drvdata (hdev);@@ -4429,7 +4432,7 @@ static int btusb_probe(struct usb_interface *intf, hdev->setup = btusb_mtk_setup; hdev->shutdown = btusb_mtk_shutdown; hdev->manufacturer =70 ; - hdev->cmd_timeout = btusb_mtk_cmd_timeout; + hdev->cmd_timeout = btmtk_reset_sync; hdev->set_bdaddr = btmtk_set_bdaddr;set_bit (HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN , &hdev->quirks);set_bit (HCI_QUIRK_NON_PERSISTENT_SETUP , &hdev->quirks); --2.25.1
Signature · 1 line
Luiz Augusto von Dentz
PATCH v7 3/3 Bluetooth: btusb: mediatek: add MediaTek devcoredump support
In reply to [email protected]From: Jing Cai <[email protected]>
This patch implement function .coredump() and dmp_hdr() in btusb driver for MediaTek controller. FW core dump was triggered by FW specific event to show something unexpected happened in the controller.
The driver would be responsible for collecting and uploading the device core dump pieces in hci driver using core dump API. Once we finished the whole process, the driver would reset the controller to recover the kind of fatal error.
---
v2, v3: rebase onto the latest codebase
v4: update the newest API usage for the coredump which was already
into the upstream
v5: support devcoredump on hdev basis
v6: reuse the coredump state HCI_DEVCOREDUMP_* in driver
and drop the driver name copying
v7: rebase ontto the latest codebase and refine the check if
we are reaching the end of the coredump
--- drivers/bluetooth/btmtk.c | 112 ++++++++++++++++++++++++++++++++++++++ drivers/bluetooth/btmtk.h | 28 ++++++++++ drivers/bluetooth/btusb.c | 14 +++++ 3 files changed, 154 insertions(+)
drivers/bluetooth/btmtk.c +112 -0
@@ -53,6 +53,56 @@ struct btmtk_section_map { }; } __packed; +static void btmtk_coredump (struct hci_dev *hdev) +{ +int err; + + err =__hci_cmd_send (hdev,0xfd5b ,0 ,NULL ); +if (err <0 ) +bt_dev_err (hdev,"Coredump failed (%d)" , err); +} + +static void btmtk_coredump_hdr (struct hci_dev *hdev,struct sk_buff *skb) +{ +struct btmediatek_data *data =hci_get_priv (hdev); +char buf[80 ]; + +snprintf (buf,sizeof (buf),"Controller Name: 0x%X\n" , + data->dev_id); +skb_put_data (skb, buf,strlen (buf)); + +snprintf (buf,sizeof (buf),"Firmware Version: 0x%X\n" , + data->cd_info.fw_version); +skb_put_data (skb, buf,strlen (buf)); + +snprintf (buf,sizeof (buf),"Driver: %s\n" , + data->cd_info.driver_name); +skb_put_data (skb, buf,strlen (buf)); + +snprintf (buf,sizeof (buf),"Vendor: MediaTek\n" ); +skb_put_data (skb, buf,strlen (buf)); +} + +static void btmtk_coredump_notify (struct hci_dev *hdev,int state) +{ +struct btmediatek_data *data =hci_get_priv (hdev); + +switch (state) { +case HCI_DEVCOREDUMP_IDLE : + data->cd_info.state =HCI_DEVCOREDUMP_IDLE ; +break ; +case HCI_DEVCOREDUMP_ACTIVE : + data->cd_info.state =HCI_DEVCOREDUMP_ACTIVE ; +break ; +case HCI_DEVCOREDUMP_TIMEOUT : +case HCI_DEVCOREDUMP_ABORT : +case HCI_DEVCOREDUMP_DONE : + data->cd_info.state =HCI_DEVCOREDUMP_IDLE ; +btmtk_reset_sync (hdev); +break ; + } +} +int btmtk_setup_firmware_79xx (struct hci_dev *hdev,const char *fwname,wmt_cmd_sync_func_t wmt_cmd_sync) {
@@ -295,6 +345,68 @@ void btmtk_reset_sync(struct hci_dev *hdev) }EXPORT_SYMBOL_GPL (btmtk_reset_sync); +int btmtk_register_coredump (struct hci_dev *hdev,const char *name, +u32 fw_version) +{ +struct btmediatek_data *data =hci_get_priv (hdev); + +if (!IS_ENABLED (CONFIG_DEV_COREDUMP )) +return -EOPNOTSUPP ; + + data->cd_info.fw_version = fw_version; + data->cd_info.state =HCI_DEVCOREDUMP_IDLE ; + data->cd_info.driver_name = name; + +return hci_devcd_register (hdev, btmtk_coredump, btmtk_coredump_hdr, + btmtk_coredump_notify); +} +EXPORT_SYMBOL_GPL (btmtk_register_coredump); + +int btmtk_process_coredump (struct hci_dev *hdev,struct sk_buff *skb) +{ +struct btmediatek_data *data =hci_get_priv (hdev); +int err; + +if (!IS_ENABLED (CONFIG_DEV_COREDUMP )) +return 0 ; + +switch (data->cd_info.state) { +case HCI_DEVCOREDUMP_IDLE : + err =hci_devcd_init (hdev,MTK_COREDUMP_SIZE ); +if (err <0 ) +break ; + data->cd_info.cnt =0 ; + +/* It is supposed coredump can be done within 5 seconds */ +schedule_delayed_work (&hdev->dump.dump_timeout, +msecs_to_jiffies (5000 )); + fallthrough; +case HCI_DEVCOREDUMP_ACTIVE : +default : + err =hci_devcd_append (hdev, skb); +if (err <0 ) +break ; + data->cd_info.cnt++; + +/* Mediatek coredump data would be more than MTK_COREDUMP_NUM */ +if (data->cd_info.cnt >MTK_COREDUMP_NUM && + skb->len >sizeof (MTK_COREDUMP_END ) && + !memcmp ((char *)&skb->data[skb->len -sizeof (MTK_COREDUMP_END )], +MTK_COREDUMP_END ,sizeof (MTK_COREDUMP_END ) -1 )) { +bt_dev_info (hdev,"Mediatek coredump end" ); +hci_devcd_complete (hdev); + } + +break ; + } + +if (err <0 ) +kfree_skb (skb); + +return err; +} +EXPORT_SYMBOL_GPL (btmtk_process_coredump); +MODULE_AUTHOR ("Sean Wang <[email protected]>" );MODULE_AUTHOR ("Mark Chen <[email protected]>" );MODULE_DESCRIPTION ("Bluetooth support for MediaTek devices ver " VERSION );
drivers/bluetooth/btmtk.h +28 -0
@@ -22,6 +22,10 @@#define MT7921_DLSTATUS 0x7c053c10#define BT_DL_STATE BIT(1) +#define MTK_COREDUMP_SIZE (1024 * 1000) +#define MTK_COREDUMP_END "coredump end" +#define MTK_COREDUMP_NUM 255 +enum {BTMTK_WMT_PATCH_DWNLD =0x1 ,BTMTK_WMT_TEST =0x2 ,
@@ -122,9 +126,17 @@ struct btmtk_hci_wmt_params {typedef int (*btmtk_reset_sync_func_t )(struct hci_dev *,void *); +struct btmtk_coredump_info { +const char *driver_name; +u32 fw_version; +u16 cnt; +int state; +}; +struct btmediatek_data {u32 dev_id;btmtk_reset_sync_func_t reset_sync; +struct btmtk_coredump_info cd_info; }; typedef int (*wmt_cmd_sync_func_t)(struct hci_dev *,
@@ -141,6 +153,11 @@ int btmtk_setup_firmware(struct hci_dev *hdev, const char *fwname, wmt_cmd_sync_func_t wmt_cmd_sync);void btmtk_reset_sync (struct hci_dev *hdev); + +int btmtk_register_coredump (struct hci_dev *hdev,const char *name, +u32 fw_version); + +int btmtk_process_coredump (struct hci_dev *hdev,struct sk_buff *skb);#else static inline int btmtk_set_bdaddr(struct hci_dev *hdev,
@@ -164,4 +181,15 @@ static int btmtk_setup_firmware(struct hci_dev *hdev, const char *fwname,static void btmtk_reset_sync (struct hci_dev *hdev) { } + +static int btmtk_register_coredump (struct hci_dev *hdev,const char *name, +u32 fw_version) +{ +return -EOPNOTSUPP ; +} + +static int btmtk_process_coredump (struct hci_dev *hdev,struct sk_buff *skb) +{ +return -EOPNOTSUPP ; +}#endif
drivers/bluetooth/btusb.c +14 -0
@@ -3150,6 +3150,10 @@ static int btusb_mtk_setup(struct hci_dev *hdev) mediatek->dev_id = dev_id; mediatek->reset_sync = btusb_mtk_reset_work; + err =btmtk_register_coredump (hdev, btusb_driver.name, fw_version); +if (err <0 ) +bt_dev_err (hdev,"Failed to register coredump (%d)" , err); +switch (dev_id) {case 0x7663 : fwname =FIRMWARE_MT7663 ;
@@ -3310,6 +3314,7 @@ static int btusb_recv_acl_mtk(struct hci_dev *hdev, struct sk_buff *skb) {struct btusb_data *data =hci_get_drvdata (hdev);u16 handle =le16_to_cpu (hci_acl_hdr (skb)->handle); +struct sk_buff *skb_cd;switch (handle) {case 0xfc6f :/* Firmware dump from device */
@@ -3317,6 +3322,15 @@ static int btusb_recv_acl_mtk(struct hci_dev *hdev, struct sk_buff *skb)* suspend and thus disable auto-suspend. */ usb_disable_autosuspend (data->udev); + +/* We need to forward the diagnostic packet to userspace daemon +* for backward compatibility, so we have to clone the packet +* extraly for the in-kernel coredump support. +*/ + skb_cd =skb_clone (skb,GFP_ATOMIC ); +if (skb_cd) +btmtk_process_coredump (hdev, skb_cd); + fallthrough;case 0x05ff :/* Firmware debug logging 1 */ case 0x05fe :/* Firmware debug logging 2 */
Signature · 1 line
2.25.1
kernel test robot
build botRe: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
kernel test robot noticed the following build errors:
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on next-20230623]
[cannot apply to bluetooth/master wireless/main wireless-next/main linus/master v6.4-rc7] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/sean-wang-mediatek-com/Bluetooth-btmtk-introduce-btmtk-reset-work/20230624-100756 base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master patch link: https://lore.kernel.org/r/ed1d0e9fe7758dac8a05dcff97c7dcb8e9b0be39.1687565769.git.objelf%40gmail.com patch subject: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support config: x86_64-buildonly-randconfig-r002-20230622 (https://download.01.org/0day-ci/archive/20230624/[email protected]/config) compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a) reproduce: (https://download.01.org/0day-ci/archive/20230624/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
>> drivers/bluetooth/btmtk.c:381:32: error: no member named 'dump' in 'struct hci_dev'
schedule_delayed_work(&hdev->dump.dump_timeout,
~~~~ ^1 error generated.
vim +381 drivers/bluetooth/btmtk.c
364
365 int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
366 {
367 struct btmediatek_data *data = hci_get_priv(hdev);
368 int err;
369
370 if (!IS_ENABLED(CONFIG_DEV_COREDUMP))
371 return 0;
372
373 switch (data->cd_info.state) {
374 case HCI_DEVCOREDUMP_IDLE:
375 err = hci_devcd_init(hdev, MTK_COREDUMP_SIZE);
376 if (err < 0)
377 break;
378 data->cd_info.cnt = 0;
379
380 /* It is supposed coredump can be done within 5 seconds */
> 381 schedule_delayed_work(&hdev->dump.dump_timeout,
382 msecs_to_jiffies(5000));
383 fallthrough;
384 case HCI_DEVCOREDUMP_ACTIVE:
385 default:
386 err = hci_devcd_append(hdev, skb);
387 if (err < 0)
388 break;
389 data->cd_info.cnt++;
390
391 /* Mediatek coredump data would be more than MTK_COREDUMP_NUM */
392 if (data->cd_info.cnt > MTK_COREDUMP_NUM &&
393 skb->len > sizeof(MTK_COREDUMP_END) &&
394 !memcmp((char *)&skb->data[skb->len - sizeof(MTK_COREDUMP_END)],
395 MTK_COREDUMP_END, sizeof(MTK_COREDUMP_END) - 1)) {
396 bt_dev_info(hdev, "Mediatek coredump end");
397 hci_devcd_complete(hdev);
398 }
399
400 break;
401 }
402
403 if (err < 0)
404 kfree_skb(skb);
405
406 return err;
407 }
408 EXPORT_SYMBOL_GPL(btmtk_process_coredump);
409
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
In reply to [email protected]kernel test robot noticed the following build errors:
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on next-20230623]
[cannot apply to bluetooth/master wireless/main wireless-next/main linus/master v6.4-rc7] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/sean-wang-mediatek-com/Bluetooth-btmtk-introduce-btmtk-reset-work/20230624-100756 base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master patch link: https://lore.kernel.org/r/ed1d0e9fe7758dac8a05dcff97c7dcb8e9b0be39.1687565769.git.objelf%40gmail.com patch subject: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support config: x86_64-randconfig-a002-20230621 (https://download.01.org/0day-ci/archive/20230624/[email protected]/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce: (https://download.01.org/0day-ci/archive/20230624/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
drivers/bluetooth/btmtk.c: In function 'btmtk_process_coredump':
>> drivers/bluetooth/btmtk.c:381:44: error: 'struct hci_dev' has no member named 'dump'
381 | schedule_delayed_work(&hdev->dump.dump_timeout,
| ^~vim +381 drivers/bluetooth/btmtk.c
364
365 int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
366 {
367 struct btmediatek_data *data = hci_get_priv(hdev);
368 int err;
369
370 if (!IS_ENABLED(CONFIG_DEV_COREDUMP))
371 return 0;
372
373 switch (data->cd_info.state) {
374 case HCI_DEVCOREDUMP_IDLE:
375 err = hci_devcd_init(hdev, MTK_COREDUMP_SIZE);
376 if (err < 0)
377 break;
378 data->cd_info.cnt = 0;
379
380 /* It is supposed coredump can be done within 5 seconds */
> 381 schedule_delayed_work(&hdev->dump.dump_timeout,
382 msecs_to_jiffies(5000));
383 fallthrough;
384 case HCI_DEVCOREDUMP_ACTIVE:
385 default:
386 err = hci_devcd_append(hdev, skb);
387 if (err < 0)
388 break;
389 data->cd_info.cnt++;
390
391 /* Mediatek coredump data would be more than MTK_COREDUMP_NUM */
392 if (data->cd_info.cnt > MTK_COREDUMP_NUM &&
393 skb->len > sizeof(MTK_COREDUMP_END) &&
394 !memcmp((char *)&skb->data[skb->len - sizeof(MTK_COREDUMP_END)],
395 MTK_COREDUMP_END, sizeof(MTK_COREDUMP_END) - 1)) {
396 bt_dev_info(hdev, "Mediatek coredump end");
397 hci_devcd_complete(hdev);
398 }
399
400 break;
401 }
402
403 if (err < 0)
404 kfree_skb(skb);
405
406 return err;
407 }
408 EXPORT_SYMBOL_GPL(btmtk_process_coredump);
409
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=760403
---Test result---
Test Summary:
CheckPatch PASS 2.54 seconds GitLint FAIL 1.07 seconds SubjectPrefix PASS 0.25 seconds BuildKernel PASS 32.25 seconds CheckAllWarning PASS 35.44 seconds CheckSparse PASS 40.36 seconds CheckSmatch PASS 111.91 seconds BuildKernel32 PASS 30.99 seconds TestRunnerSetup PASS 444.24 seconds TestRunner_l2cap-tester PASS 16.60 seconds TestRunner_iso-tester PASS 22.56 seconds TestRunner_bnep-tester PASS 5.30 seconds TestRunner_mgmt-tester PASS 128.29 seconds TestRunner_rfcomm-tester PASS 8.51 seconds TestRunner_sco-tester PASS 7.84 seconds TestRunner_ioctl-tester PASS 9.07 seconds TestRunner_mesh-tester PASS 6.71 seconds TestRunner_smp-tester PASS 7.87 seconds TestRunner_userchan-tester PASS 5.51 seconds IncrementalBuild PASS 41.53 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v7,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (82>80): "[v7,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding"
---
Regards,
Linux Bluetooth
This series was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Hello:
This series was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Quoted 8 lines · On Tue, 27 Jun 2023 04:41:37 +0800 you wrote:
From: Sean Wang <[email protected]>
Use
readx_poll_timeoutinstead of open coding to poll the hardware reset status until it is done.Signed-off-by Sean Wang <[email protected]>[...]
Here is the summary with links:
- [v7,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
https://git.kernel.org/bluetooth/bluetooth-next/c/c56e5f834e13
- [v7,2/3] Bluetooth: btmtk: introduce btmtk reset work
(no matching commit)
- [v7,3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support (no matching commit)
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html