From: <sean.wang@mediatek.com> To: <marcel@holtmann.org>, <johan.hedberg@gmail.com> Cc: <linux-bluetooth@vger.kernel.org>, <linux-mediatek@lists.infradead.org>, <linux-kernel@vger.kernel.org>, Sean Wang <sean.wang@mediatek.com> Subject: [PATCH v6 0/2] Bluetooth: btusb: Add protocol support for MediaTek USB devices Date: Fri, 25 Jan 2019 07:26:46 +0800 [thread overview] Message-ID: <cover.1548371338.git.sean.wang@mediatek.com> (raw) From: Sean Wang <sean.wang@mediatek.com> v6: * fix drivers/bluetooth/btusb.c:2683:2-3: Unneeded semicolon based reported by [1] * update power-on sequence with adding neccesary tci sleep comand to set up low-power environmnet and a delay to wait the device to be stable. * sort variables declarations in reverse xmas order. [1] http://lists.infradead.org/pipermail/linux-mediatek/2019-January/017017.html v5: * rebase to latest code base. * change the subject prefix. * change the place the firmware located at. v4: * use new BTUSB_TX_WAIT_VND_EVT instead of BTMTKUSB_TX_WAIT_VND_EVT to avoid definition conflict and to fix bulk data transfer fails. * use the bluetooth-next as the base v3: add fixes and enhancements based on [1] * reuse flags and evt_skb btusb already had * add ctrl_anchor and the corresponding handling * apply mtk specific recv function * add more comments explaining wmt ctrl urbs behavior. [1] http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014724.html v2: add fixes and enhancements based on [1] * include /sys/kernel/debug/usb/devices portion in the commit message. * turn default into n for config BT_HCIBTUSB_MTK in Kconfig * only add MediaTek support to btusb.c * drop cmd_sync callback usage * use __hci_cmd_send to send WMT commands * add wait event handling similar to what is being done in btmtkuart.c * submit a control IN URB similar to interrupt IN URB on demand for the WMT commands during setup * add cosmetic changes [1] http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014650.html http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014656.html v1: This adds the support of enabling MT7668U and MT7663U Bluetooth function running on the top of btusb driver. The patch also adds a newly created file mtkbt.c able to be reused independently from the transport type such as UART, USB and SDIO. Sean Wang (2): Bluetooth: btusb: Add protocol support for MediaTek MT7668U USB devices Bluetooth: btusb: Add protocol support for MediaTek MT7663U USB devices drivers/bluetooth/Kconfig | 11 + drivers/bluetooth/btusb.c | 581 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 592 insertions(+) -- 2.18.0
WARNING: multiple messages have this Message-ID (diff)
From: <sean.wang@mediatek.com> To: marcel@holtmann.org, johan.hedberg@gmail.com Cc: linux-bluetooth@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, Sean Wang <sean.wang@mediatek.com> Subject: [PATCH v6 0/2] Bluetooth: btusb: Add protocol support for MediaTek USB devices Date: Fri, 25 Jan 2019 07:26:46 +0800 [thread overview] Message-ID: <cover.1548371338.git.sean.wang@mediatek.com> (raw) From: Sean Wang <sean.wang@mediatek.com> v6: * fix drivers/bluetooth/btusb.c:2683:2-3: Unneeded semicolon based reported by [1] * update power-on sequence with adding neccesary tci sleep comand to set up low-power environmnet and a delay to wait the device to be stable. * sort variables declarations in reverse xmas order. [1] http://lists.infradead.org/pipermail/linux-mediatek/2019-January/017017.html v5: * rebase to latest code base. * change the subject prefix. * change the place the firmware located at. v4: * use new BTUSB_TX_WAIT_VND_EVT instead of BTMTKUSB_TX_WAIT_VND_EVT to avoid definition conflict and to fix bulk data transfer fails. * use the bluetooth-next as the base v3: add fixes and enhancements based on [1] * reuse flags and evt_skb btusb already had * add ctrl_anchor and the corresponding handling * apply mtk specific recv function * add more comments explaining wmt ctrl urbs behavior. [1] http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014724.html v2: add fixes and enhancements based on [1] * include /sys/kernel/debug/usb/devices portion in the commit message. * turn default into n for config BT_HCIBTUSB_MTK in Kconfig * only add MediaTek support to btusb.c * drop cmd_sync callback usage * use __hci_cmd_send to send WMT commands * add wait event handling similar to what is being done in btmtkuart.c * submit a control IN URB similar to interrupt IN URB on demand for the WMT commands during setup * add cosmetic changes [1] http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014650.html http://lists.infradead.org/pipermail/linux-mediatek/2018-August/014656.html v1: This adds the support of enabling MT7668U and MT7663U Bluetooth function running on the top of btusb driver. The patch also adds a newly created file mtkbt.c able to be reused independently from the transport type such as UART, USB and SDIO. Sean Wang (2): Bluetooth: btusb: Add protocol support for MediaTek MT7668U USB devices Bluetooth: btusb: Add protocol support for MediaTek MT7663U USB devices drivers/bluetooth/Kconfig | 11 + drivers/bluetooth/btusb.c | 581 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 592 insertions(+) -- 2.18.0
next reply other threads:[~2019-01-24 23:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-24 23:26 sean.wang [this message] 2019-01-24 23:26 ` [PATCH v6 0/2] Bluetooth: btusb: Add protocol support for MediaTek USB devices sean.wang 2019-01-24 23:26 ` [PATCH v6 1/2] Bluetooth: btusb: Add protocol support for MediaTek MT7668U " sean.wang 2019-01-24 23:26 ` sean.wang 2019-01-24 23:26 ` [PATCH v6 2/2] Bluetooth: btusb: Add protocol support for MediaTek MT7663U " sean.wang 2019-01-24 23:26 ` sean.wang 2019-03-18 18:14 ` [PATCH v6 0/2] Bluetooth: btusb: Add protocol support for MediaTek " Sean Wang 2019-03-18 18:14 ` Sean Wang
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=cover.1548371338.git.sean.wang@mediatek.com \ --to=sean.wang@mediatek.com \ --cc=johan.hedberg@gmail.com \ --cc=linux-bluetooth@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=marcel@holtmann.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: linkBe 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.