Re: [PATCH] Bluetooth: TI_ST bluetooth driver

[Pavan Savoy]

On Mon, Oct 11, 2010 at 12:33 PM,  <pavan_savoy@xxxxxx> wrote:
> From: Pavan Savoy <pavan_savoy@xxxxxx>
>
> Gustavo, Marcel,
>
> I have taken care of most of the comments which you provided.
> Couple of them like usage of goto's, I didn't handle since
> I am not doing much error handling repeatedly there.
>
> I have also removed the 2 states like _REGISTERED, _RUNNING which
> were not required and the flags associated with it.
> I have taken care of other style comments.
>
> Please review and provide your comments,

Marcel,
I hope you find some time to provide comments.


Thanks,
Pavan

> -- patch description --
>
> This is the bluetooth protocol driver for the TI WiLink7 chipsets.
> Texas Instrument's WiLink chipsets combine wireless technologies
> like BT, FM, GPS and WLAN onto a single chip.
>
> This Bluetooth driver works on top of the TI_ST shared transport
> line discipline driver which also allows other drivers like
> FM V4L2 and GPS character driver to make use of the same UART interface.
>
> Kconfig and Makefile modifications to enable the Bluetooth
> driver for Texas Instrument's WiLink 7 chipset.
>
> Signed-off-by: Pavan Savoy <pavan_savoy@xxxxxx>
> ---
> Âdrivers/bluetooth/Kconfig  Â|  10 +
> Âdrivers/bluetooth/Makefile  |  Â1 +
> Âdrivers/bluetooth/btwilink.c | Â455 ++++++++++++++++++++++++++++++++++++++++++
> Â3 files changed, 466 insertions(+), 0 deletions(-)
> Âcreate mode 100644 drivers/bluetooth/btwilink.c
>
> diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
> index 02deef4..e0d67dd 100644
> --- a/drivers/bluetooth/Kconfig
> +++ b/drivers/bluetooth/Kconfig
> @@ -219,4 +219,14 @@ config BT_ATH3K
> Â Â Â Â ÂSay Y here to compile support for "Atheros firmware download driver"
> Â Â Â Â Âinto the kernel or say M to compile it as module (ath3k).
>
> +config BT_WILINK
> + Â Â Â tristate "BlueZ bluetooth driver for TI ST"
> + Â Â Â depends on TI_ST
> + Â Â Â help
> + Â Â Â Â This enables the Bluetooth driver for Texas Instrument's BT/FM/GPS
> + Â Â Â Â combo devices. This makes use of shared transport line discipline
> + Â Â Â Â core driver to communicate with the BT core of the combo chip.
> +
> + Â Â Â Â Say Y here to compile support for Texas Instrument's WiLink7 driver
> + Â Â Â Â into the kernel or say M to compile it as module.
> Âendmenu
> diff --git a/drivers/bluetooth/Makefile b/drivers/bluetooth/Makefile
> index 71bdf13..5351b62 100644
> --- a/drivers/bluetooth/Makefile
> +++ b/drivers/bluetooth/Makefile
> @@ -28,3 +28,4 @@ hci_uart-$(CONFIG_BT_HCIUART_BCSP) Â Â+= hci_bcsp.o
> Âhci_uart-$(CONFIG_BT_HCIUART_LL) Â Â Â += hci_ll.o
> Âhci_uart-$(CONFIG_BT_HCIUART_ATH3K) Â Â+= hci_ath.o
> Âhci_uart-objs             Â:= $(hci_uart-y)
> +obj-$(CONFIG_BT_WILINK) Â Â Â Â Â Â Â Â Â Â Â Â:= btwilink.o
> diff --git a/drivers/bluetooth/btwilink.c b/drivers/bluetooth/btwilink.c
> new file mode 100644
> index 0000000..e0bde79
> --- /dev/null
> +++ b/drivers/bluetooth/btwilink.c
> @@ -0,0 +1,455 @@
> +/*
> + * ÂTexas Instrument's Bluetooth Driver For Shared Transport.
> + *
> + * ÂBluetooth Driver acts as interface between HCI CORE and
> + * ÂTI Shared Transport Layer.
> + *
> + * ÂCopyright (C) 2009-2010 Texas Instruments
> + * ÂAuthor: Raja Mani <raja_mani@xxxxxx>
> + * Â Â Pavan Savoy <pavan_savoy@xxxxxx>
> + *
> + * ÂThis program is free software; you can redistribute it and/or modify
> + * Âit under the terms of the GNU General Public License version 2 as
> + * Âpublished by the Free Software Foundation.
> + *
> + * ÂThis program is distributed in the hope that it will be useful,
> + * Âbut WITHOUT ANY WARRANTY; without even the implied warranty of
> + * ÂMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ÂSee the
> + * ÂGNU General Public License for more details.
> + *
> + * ÂYou should have received a copy of the GNU General Public License
> + * Âalong with this program; if not, write to the Free Software
> + * ÂFoundation, Inc., 59 Temple Place, Suite 330, Boston, MA Â02111-1307 ÂUSA
> + *
> + */
> +
> +#include <linux/platform_device.h>
> +#include <net/bluetooth/bluetooth.h>
> +#include <net/bluetooth/hci_core.h>
> +
> +#include <linux/ti_wilink_st.h>
> +
> +/* Bluetooth Driver Version */
> +#define VERSION Â Â Â Â Â Â Â "1.0"
> +
> +/* Defines number of seconds to wait for reg completion
> + * callback getting called from ST (in case,registration
> + * with ST returns PENDING status)
> + */
> +#define BT_REGISTER_TIMEOUT Â 6000 Â Â /* 6 sec */
> +
> +/**
> + * struct ti_st - BT driver operation structure
> + * @hdev: hci device pointer which binds to bt driver
> + * @flags: used locally,to maintain various BT driver status
> + * @streg_cbdata: to hold ST registration callback status
> + * @st_write: write function pointer of ST driver
> + * @wait_for_btdrv_reg_completion - completion sync between ti_st_open
> + * Â Â and ti_st_registration_completion_cb.
> + */
> +struct ti_st {
> + Â Â Â struct hci_dev *hdev;
> + Â Â Â char streg_cbdata;
> + Â Â Â long (*st_write) (struct sk_buff *);
> + Â Â Â struct completion wait_for_btdrv_reg_completion;
> +};
> +
> +static int reset;
> +
> +/* Increments HCI counters based on pocket ID (cmd,acl,sco) */
> +static inline void ti_st_tx_complete(struct ti_st *hst, int pkt_type)
> +{
> + Â Â Â struct hci_dev *hdev;
> + Â Â Â hdev = hst->hdev;
> +
> + Â Â Â /* Update HCI stat counters */
> + Â Â Â switch (pkt_type) {
> + Â Â Â case HCI_COMMAND_PKT:
> + Â Â Â Â Â Â Â hdev->stat.cmd_tx++;
> + Â Â Â Â Â Â Â break;
> +
> + Â Â Â case HCI_ACLDATA_PKT:
> + Â Â Â Â Â Â Â hdev->stat.acl_tx++;
> + Â Â Â Â Â Â Â break;
> +
> + Â Â Â case HCI_SCODATA_PKT:
> + Â Â Â Â Â Â Â hdev->stat.sco_tx++;
> + Â Â Â Â Â Â Â break;
> + Â Â Â }
> +}
> +
> +/* ------- Interfaces to Shared Transport ------ */
> +
> +/* Called by ST layer to indicate protocol registration completion
> + * status.ti_st_open() function will wait for signal from this
> + * API when st_register() function returns ST_PENDING.
> + */
> +static void st_registration_completion_cb(void *priv_data, char data)
> +{
> + Â Â Â struct ti_st *lhst = (struct ti_st *)priv_data;
> + Â Â Â /* ti_st_open() function needs value of 'data' to know
> + Â Â Â Â* the registration status(success/fail),So have a back
> + Â Â Â Â* up of it.
> + Â Â Â Â*/
> + Â Â Â lhst->streg_cbdata = data;
> +
> + Â Â Â /* Got a feedback from ST for BT driver registration
> + Â Â Â Â* request.Wackup ti_st_open() function to continue
> + Â Â Â Â* it's open operation.
> + Â Â Â Â*/
> + Â Â Â complete(&lhst->wait_for_btdrv_reg_completion);
> +}
> +
> +/* Called by Shared Transport layer when receive data is
> + * available */
> +static long st_receive(void *priv_data, struct sk_buff *skb)
> +{
> + Â Â Â int err;
> + Â Â Â struct ti_st *lhst = (struct ti_st *)priv_data;
> +
> + Â Â Â if (skb == NULL) {
> + Â Â Â Â Â Â Â BT_ERR("Invalid SKB received from ST");
> + Â Â Â Â Â Â Â return -EFAULT;
> + Â Â Â }
> +
> + Â Â Â if (!lhst) {
> + Â Â Â Â Â Â Â kfree_skb(skb);
> + Â Â Â Â Â Â Â BT_ERR("Invalid ti_st memory,freeing SKB");
> + Â Â Â Â Â Â Â return -EFAULT;
> + Â Â Â }
> +
> + Â Â Â skb->dev = (struct net_device *)lhst->hdev;
> + Â Â Â /* Forward skb to HCI CORE layer */
> + Â Â Â err = hci_recv_frame(skb);
> + Â Â Â if (err) {
> + Â Â Â Â Â Â Â kfree_skb(skb);
> + Â Â Â Â Â Â Â BT_ERR("Unable to push skb to HCI CORE(%d),freeing SKB",
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â err);
> + Â Â Â Â Â Â Â return err;
> + Â Â Â }
> +
> + Â Â Â lhst->hdev->stat.byte_rx += skb->len;
> + Â Â Â return 0;
> +}
> +
> +/* ------- Interfaces to HCI layer ------ */
> +
> +/* Called from HCI core to initialize the device */
> +static int ti_st_open(struct hci_dev *hdev)
> +{
> + Â Â Â static struct st_proto_s ti_st_proto;
> + Â Â Â unsigned long timeleft;
> + Â Â Â struct ti_st *hst;
> + Â Â Â int err;
> + Â Â Â err = 0;
> +
> + Â Â Â BT_DBG("%s %p", hdev->name, hdev);
> + Â Â Â hst = hdev->driver_data;
> +
> + Â Â Â /* Populate BT driver info required by ST */
> + Â Â Â memset(&ti_st_proto, 0, sizeof(ti_st_proto));
> +
> + Â Â Â /* BT driver ID */
> + Â Â Â ti_st_proto.type = ST_BT;
> +
> + Â Â Â /* Receive function which called from ST */
> + Â Â Â ti_st_proto.recv = st_receive;
> +
> + Â Â Â /* Callback to be called when registration is pending */
> + Â Â Â ti_st_proto.reg_complete_cb = st_registration_completion_cb;
> +
> + Â Â Â /* send in the hst to be received at registration complete callback
> + Â Â Â Â* and during st's receive
> + Â Â Â Â*/
> + Â Â Â ti_st_proto.priv_data = hst;
> +
> + Â Â Â /* Register with ST layer */
> + Â Â Â err = st_register(&ti_st_proto);
> + Â Â Â if (err == -EINPROGRESS) {
> + Â Â Â Â Â Â Â /* Prepare wait-for-completion handler data structures.
> + Â Â Â Â Â Â Â Â* Needed to syncronize this and st_registration_completion_cb()
> + Â Â Â Â Â Â Â Â* functions.
> + Â Â Â Â Â Â Â Â*/
> + Â Â Â Â Â Â Â init_completion(&hst->wait_for_btdrv_reg_completion);
> +
> + Â Â Â Â Â Â Â /* Reset ST registration callback status flag , this value
> + Â Â Â Â Â Â Â Â* will be updated in ti_st_registration_completion_cb()
> + Â Â Â Â Â Â Â Â* function whenever it called from ST driver.
> + Â Â Â Â Â Â Â Â*/
> + Â Â Â Â Â Â Â hst->streg_cbdata = -EINPROGRESS;
> +
> + Â Â Â Â Â Â Â /* ST is busy with other protocol registration(may be busy with
> + Â Â Â Â Â Â Â Â* firmware download).So,Wait till the registration callback
> + Â Â Â Â Â Â Â Â* (passed as a argument to st_register() function) getting
> + Â Â Â Â Â Â Â Â* called from ST.
> + Â Â Â Â Â Â Â Â*/
> + Â Â Â Â Â Â Â BT_DBG(" %s waiting for reg completion signal from ST",
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â __func__);
> +
> + Â Â Â Â Â Â Â timeleft =
> + Â Â Â Â Â Â Â Â Â Â Â wait_for_completion_timeout
> + Â Â Â Â Â Â Â Â Â Â Â (&hst->wait_for_btdrv_reg_completion,
> + Â Â Â Â Â Â Â Â Â Â Â Âmsecs_to_jiffies(BT_REGISTER_TIMEOUT));
> + Â Â Â Â Â Â Â if (!timeleft) {
> + Â Â Â Â Â Â Â Â Â Â Â BT_ERR("Timeout(%d sec),didn't get reg"
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â "completion signal from ST",
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â BT_REGISTER_TIMEOUT / 1000);
> + Â Â Â Â Â Â Â Â Â Â Â return -ETIMEDOUT;
> + Â Â Â Â Â Â Â }
> +
> + Â Â Â Â Â Â Â /* Is ST registration callback called with ERROR value? */
> + Â Â Â Â Â Â Â if (hst->streg_cbdata != 0) {
> + Â Â Â Â Â Â Â Â Â Â Â BT_ERR("ST reg completion CB called with invalid"
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â "status %d", hst->streg_cbdata);
> + Â Â Â Â Â Â Â Â Â Â Â return -EAGAIN;
> + Â Â Â Â Â Â Â }
> + Â Â Â Â Â Â Â err = 0;
> + Â Â Â } else if (err == -1) {
> + Â Â Â Â Â Â Â BT_ERR("st_register failed %d", err);
> + Â Â Â Â Â Â Â return -EAGAIN;
> + Â Â Â }
> +
> + Â Â Â /* Do we have proper ST write function? */
> + Â Â Â if (ti_st_proto.write != NULL) {
> + Â Â Â Â Â Â Â /* We need this pointer for sending any Bluetooth pkts */
> + Â Â Â Â Â Â Â hst->st_write = ti_st_proto.write;
> + Â Â Â } else {
> + Â Â Â Â Â Â Â BT_ERR("failed to get ST write func pointer");
> +
> + Â Â Â Â Â Â Â /* Undo registration with ST */
> + Â Â Â Â Â Â Â err = st_unregister(ST_BT);
> + Â Â Â Â Â Â Â if (err < 0)
> + Â Â Â Â Â Â Â Â Â Â Â BT_ERR("st_unregister failed %d", err);
> +
> + Â Â Â Â Â Â Â hst->st_write = NULL;
> + Â Â Â Â Â Â Â return -EAGAIN;
> + Â Â Â }
> +
> + Â Â Â /* Registration with ST layer is completed successfully,
> + Â Â Â Â* now chip is ready to accept commands from HCI CORE.
> + Â Â Â Â* Mark HCI Device flag as RUNNING
> + Â Â Â Â*/
> + Â Â Â set_bit(HCI_RUNNING, &hdev->flags);
> + Â Â Â return err;
> +}
> +
> +/* Close device */
> +static int ti_st_close(struct hci_dev *hdev)
> +{
> + Â Â Â int err = 0;
> + Â Â Â struct ti_st *hst;
> +
> + Â Â Â hst = hdev->driver_data;
> +
> + Â Â Â /* Clear HCI device RUNNING flag */
> + Â Â Â if (!test_and_clear_bit(HCI_RUNNING, &hdev->flags))
> + Â Â Â Â Â Â Â BT_ERR("HCI not RUNNING?");
> +
> + Â Â Â /* continue to unregister from transport */
> + Â Â Â err = st_unregister(ST_BT);
> + Â Â Â if (err != 0) {
> + Â Â Â Â Â Â Â hst->st_write = NULL;
> + Â Â Â Â Â Â Â BT_ERR("st_unregister failed %d", err);
> + Â Â Â Â Â Â Â return -EBUSY;
> + Â Â Â }
> +
> + Â Â Â hst->st_write = NULL;
> + Â Â Â return err;
> +}
> +
> +/* Called from HCI CORE , Sends frames to Shared Transport */
> +static int ti_st_send_frame(struct sk_buff *skb)
> +{
> + Â Â Â struct hci_dev *hdev;
> + Â Â Â struct ti_st *hst;
> + Â Â Â long len;
> +
> + Â Â Â if (skb == NULL) {
> + Â Â Â Â Â Â Â BT_ERR("Invalid skb received from HCI CORE");
> + Â Â Â Â Â Â Â return -ENOMEM;
> + Â Â Â }
> +
> + Â Â Â hdev = (struct hci_dev *)skb->dev;
> + Â Â Â if (!hdev) {
> + Â Â Â Â Â Â Â BT_ERR("SKB received for invalid HCI Device (hdev=NULL)");
> + Â Â Â Â Â Â Â return -ENODEV;
> + Â Â Â }
> +
> + Â Â Â if (!test_bit(HCI_RUNNING, &hdev->flags)) {
> + Â Â Â Â Â Â Â BT_ERR("Device is not running");
> + Â Â Â Â Â Â Â return -EBUSY;
> + Â Â Â }
> +
> + Â Â Â hst = (struct ti_st *)hdev->driver_data;
> +
> + Â Â Â /* Prepend skb with frame type */
> + Â Â Â memcpy(skb_push(skb, 1), &bt_cb(skb)->pkt_type, 1);
> +
> + Â Â Â BT_DBG(" %s: type %d len %d", hdev->name, bt_cb(skb)->pkt_type,
> + Â Â Â Â Â Â Â Â Â Â Â skb->len);
> +
> + Â Â Â /* Insert skb to shared transport layer's transmit queue.
> + Â Â Â Â* Freeing skb memory is taken care in shared transport layer,
> + Â Â Â Â* so don't free skb memory here.
> + Â Â Â Â*/
> + Â Â Â if (!hst->st_write) {
> + Â Â Â Â Â Â Â kfree_skb(skb);
> + Â Â Â Â Â Â Â BT_ERR(" Can't write to ST, st_write null?");
> + Â Â Â Â Â Â Â return -EAGAIN;
> + Â Â Â }
> +
> + Â Â Â len = hst->st_write(skb);
> + Â Â Â if (len < 0) {
> + Â Â Â Â Â Â Â kfree_skb(skb);
> + Â Â Â Â Â Â Â BT_ERR(" ST write failed (%ld)", len);
> + Â Â Â Â Â Â Â return -EAGAIN;
> + Â Â Â }
> +
> + Â Â Â /* ST accepted our skb. So, Go ahead and do rest */
> + Â Â Â hdev->stat.byte_tx += len;
> + Â Â Â ti_st_tx_complete(hst, bt_cb(skb)->pkt_type);
> +
> + Â Â Â return 0;
> +}
> +
> +static void ti_st_destruct(struct hci_dev *hdev)
> +{
> + Â Â Â if (!hdev) {
> + Â Â Â Â Â Â Â BT_ERR("Destruct called with invalid HCI Device"
> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â "(hdev=NULL)");
> + Â Â Â Â Â Â Â return;
> + Â Â Â }
> +
> + Â Â Â BT_DBG("%s", hdev->name);
> +
> + Â Â Â /* free ti_st memory */
> + Â Â Â if (hdev->driver_data != NULL)
> + Â Â Â Â Â Â Â kfree(hdev->driver_data);
> +
> + Â Â Â return;
> +}
> +
> +/* Creates new HCI device */
> +static int ti_st_register_dev(struct ti_st *hst)
> +{
> + Â Â Â struct hci_dev *hdev;
> +
> + Â Â Â /* Initialize and register HCI device */
> + Â Â Â hdev = hci_alloc_dev();
> + Â Â Â if (!hdev) {
> + Â Â Â Â Â Â Â BT_ERR("Can't allocate HCI device");
> + Â Â Â Â Â Â Â return -ENOMEM;
> + Â Â Â }
> + Â Â Â BT_DBG(" HCI device allocated. hdev= %p", hdev);
> +
> + Â Â Â hst->hdev = hdev;
> + Â Â Â hdev->bus = HCI_UART;
> + Â Â Â hdev->driver_data = hst;
> + Â Â Â hdev->open = ti_st_open;
> + Â Â Â hdev->close = ti_st_close;
> + Â Â Â hdev->flush = NULL;
> + Â Â Â hdev->send = ti_st_send_frame;
> + Â Â Â hdev->destruct = ti_st_destruct;
> + Â Â Â hdev->owner = THIS_MODULE;
> +
> + Â Â Â if (reset)
> + Â Â Â Â Â Â Â set_bit(HCI_QUIRK_NO_RESET, &hdev->quirks);
> +
> + Â Â Â if (hci_register_dev(hdev) < 0) {
> + Â Â Â Â Â Â Â BT_ERR("Can't register HCI device");
> + Â Â Â Â Â Â Â hci_free_dev(hdev);
> + Â Â Â Â Â Â Â return -ENODEV;
> + Â Â Â }
> +
> + Â Â Â BT_DBG(" HCI device registered. hdev= %p", hdev);
> + Â Â Â return 0;
> +}
> +
> +
> +static int bt_ti_probe(struct platform_device *pdev)
> +{
> + Â Â Â int err;
> + Â Â Â static struct ti_st *hst;
> + Â Â Â err = 0;
> +
> + Â Â Â BT_DBG(" Bluetooth Driver Version %s", VERSION);
> +
> + Â Â Â /* Allocate local resource memory */
> + Â Â Â hst = kzalloc(sizeof(struct ti_st), GFP_KERNEL);
> + Â Â Â if (!hst) {
> + Â Â Â Â Â Â Â BT_ERR("Can't allocate control structure");
> + Â Â Â Â Â Â Â return -ENFILE;
> + Â Â Â }
> +
> + Â Â Â /* Expose "hciX" device to user space */
> + Â Â Â err = ti_st_register_dev(hst);
> + Â Â Â if (err) {
> + Â Â Â Â Â Â Â /* Release local resource memory */
> + Â Â Â Â Â Â Â kfree(hst);
> +
> + Â Â Â Â Â Â Â BT_ERR("Unable to expose hci0 device(%d)", err);
> + Â Â Â Â Â Â Â return err;
> + Â Â Â }
> +
> + Â Â Â dev_set_drvdata(&pdev->dev, hst);
> + Â Â Â return err;
> +}
> +
> +static int bt_ti_remove(struct platform_device *pdev)
> +{
> + Â Â Â struct ti_st *hst;
> +
> + Â Â Â hst = dev_get_drvdata(&pdev->dev);
> + Â Â Â /* Deallocate local resource's memory Â*/
> + Â Â Â if (hst) {
> + Â Â Â Â Â Â Â struct hci_dev *hdev = hst->hdev;
> + Â Â Â Â Â Â Â if (hdev == NULL) {
> + Â Â Â Â Â Â Â Â Â Â Â BT_ERR("Invalid hdev memory");
> + Â Â Â Â Â Â Â Â Â Â Â kfree(hst);
> + Â Â Â Â Â Â Â } else {
> + Â Â Â Â Â Â Â Â Â Â Â ti_st_close(hdev);
> + Â Â Â Â Â Â Â Â Â Â Â hci_unregister_dev(hdev);
> + Â Â Â Â Â Â Â Â Â Â Â /* Free HCI device memory */
> + Â Â Â Â Â Â Â Â Â Â Â hci_free_dev(hdev);
> + Â Â Â Â Â Â Â }
> + Â Â Â }
> + Â Â Â return 0;
> +}
> +
> +static struct platform_driver bt_ti_driver = {
> + Â Â Â .probe = bt_ti_probe,
> + Â Â Â .remove = bt_ti_remove,
> + Â Â Â .driver = {
> + Â Â Â Â Â Â Â .name = "ti_st_bluetooth",
> + Â Â Â Â Â Â Â .owner = THIS_MODULE,
> + Â Â Â },
> +};
> +
> +/* ------- Module Init/Exit interfaces ------ */
> +static int __init bt_drv_init(void)
> +{
> + Â Â Â long ret = 0;
> + Â Â Â ret = platform_driver_register(&bt_ti_driver);
> + Â Â Â if (ret != 0) {
> + Â Â Â Â Â Â Â BT_ERR("bt_ti platform drv registration failed");
> + Â Â Â Â Â Â Â return -1;
> + Â Â Â }
> + Â Â Â return 0;
> +}
> +
> +static void __exit bt_drv_exit(void)
> +{
> + Â Â Â platform_driver_unregister(&bt_ti_driver);
> +}
> +
> +module_init(bt_drv_init);
> +module_exit(bt_drv_exit);
> +
> +/* ------ Module Info ------ */
> +
> +module_param(reset, bool, 0644);
> +MODULE_PARM_DESC(reset, "Send HCI reset command on initialization");
> +MODULE_AUTHOR("Raja Mani <raja_mani@xxxxxx>");
> +MODULE_DESCRIPTION("Bluetooth Driver for TI Shared Transport" VERSION);
> +MODULE_VERSION(VERSION);
> +MODULE_LICENSE("GPL");
> --
> 1.6.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/