Commit a0cc2f3b authored by Pavan Savoy's avatar Pavan Savoy Committed by Greg Kroah-Hartman

staging: ti-st: move TI_ST from staging to misc/

move the 3 source files st_core.c, st_kim.c and st_ll.c
from staging to drivers/misc/.

Texas Instrument's WiLink 7 chipset packs wireless technologies like
Bluetooth, FM, GPS and WLAN into a single die.
Among these the Bluetooth, FM Rx/Tx and GPS are interfaced to a apps processor
over a single UART.

This line discipline driver allows various protocol drivers such as Bluetooth
BlueZ driver, FM V4L2 driver and GPS simple character device driver
to communicate with its relevant core in the chip.

Each protocol or technologies use a logical channel to communicate with chip.
Bluetooth uses the HCI-H4 [channels 1-4], FM uses a CH-8 and
GPS a CH-9 protocol. The driver also constitutes the TI HCI-LL Power
Management protocol which use channels 30-33.
Signed-off-by: default avatarPavan Savoy <pavan_savoy@ti.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent aecac191
/* /*
* Shared Transport Line discipline driver Core * Shared Transport Line discipline driver Core
* This hooks up ST KIM driver and ST LL driver * This hooks up ST KIM driver and ST LL driver
* Copyright (C) 2009 Texas Instruments * Copyright (C) 2009-2010 Texas Instruments
* Author: Pavan Savoy <pavan_savoy@ti.com>
* *
* This program is free software; you can redistribute it and/or modify * 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 * it under the terms of the GNU General Public License version 2 as
......
...@@ -2,7 +2,8 @@ ...@@ -2,7 +2,8 @@
* Shared Transport Line discipline driver Core * Shared Transport Line discipline driver Core
* Init Manager module responsible for GPIO control * Init Manager module responsible for GPIO control
* and firmware download * and firmware download
* Copyright (C) 2009 Texas Instruments * Copyright (C) 2009-2010 Texas Instruments
* Author: Pavan Savoy <pavan_savoy@ti.com>
* *
* This program is free software; you can redistribute it and/or modify * 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 * it under the terms of the GNU General Public License version 2 as
......
/* /*
* Shared Transport driver * Shared Transport driver
* HCI-LL module responsible for TI proprietary HCI_LL protocol * HCI-LL module responsible for TI proprietary HCI_LL protocol
* Copyright (C) 2009 Texas Instruments * Copyright (C) 2009-2010 Texas Instruments
* Author: Pavan Savoy <pavan_savoy@ti.com>
* *
* This program is free software; you can redistribute it and/or modify * 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 * it under the terms of the GNU General Public License version 2 as
......
...@@ -3,17 +3,6 @@ ...@@ -3,17 +3,6 @@
# drivers (BT, FM and GPS) # drivers (BT, FM and GPS)
# #
menu "Texas Instruments shared transport line discipline" menu "Texas Instruments shared transport line discipline"
config TI_ST
tristate "Shared transport core driver"
depends on RFKILL
select FW_LOADER
help
This enables the shared transport core driver for TI
BT / FM and GPS combo chips. This enables protocol drivers
to register themselves with core and send data, the responses
are returned to relevant protocol drivers based on their
packet types.
config ST_BT config ST_BT
tristate "BlueZ bluetooth driver for ST" tristate "BlueZ bluetooth driver for ST"
depends on BT && RFKILL depends on BT && RFKILL
......
...@@ -2,6 +2,4 @@ ...@@ -2,6 +2,4 @@
# Makefile for TI's shared transport line discipline # Makefile for TI's shared transport line discipline
# and its protocol drivers (BT, FM, GPS) # and its protocol drivers (BT, FM, GPS)
# #
obj-$(CONFIG_TI_ST) += st_drv.o
st_drv-objs := st_core.o st_kim.o st_ll.o
obj-$(CONFIG_ST_BT) += bt_drv.o obj-$(CONFIG_ST_BT) += bt_drv.o
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment