aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/ti-st
Commit message (Collapse)AuthorAgeFilesLines
* staging: ti-st: move TI_ST from staging to misc/Pavan Savoy2010-10-065-1989/+0
| | | | | | | | | | | | | | | | | | | | | | 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: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: mv ti_wilink_st headerPavan Savoy2010-10-055-406/+4
| | | | | | | | | | | | | Move the header to a standard linux device driver location. This should pave the way for other drivers to be moved into the relevant directories. ti_wilink_st.h is a common header file used by the TI's shared transport device driver for WiLink chipsets. Each individual protocol drivers like bluetooth driver, FM V4L2 driver and GPS drivers will make use of this header. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: drop the __KERNEL__Pavan Savoy2010-10-051-2/+0
| | | | | | | | | | | | | ti_wilink_st.h had the line discipline number which the user-space daemon refers to, to install and un-install the line discipline upon request from the shared transport driver via rfkill device. On moving this line discipline number to standard location of tty.h drop the __KERNEL__ flag in the header, since the header file would no longer be used by user-space. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* tty.h: new ldisc for TI WiLink STPavan Savoy2010-10-051-5/+0
| | | | | | | | | | | | | Texas Instrument's WiLink7 connectivity devices pack wireless connectivity technologies like Bluetooth, FM Radio Receiver and Transmitter, GPS and WLAN into a single die. The BT, FM and GPS core on the chip are interfaced to application processors via a single UART. This line discipline driver allows such different technologies to be used simultaneous and independent of each other. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: mv headers to ti_wilink_stPavan Savoy2010-09-2010-486/+417
| | | | | | | | | | | move all the header information to ti_wilink_st.h. This header would then not only serve the local modules like the st_core.c, st_kim.c and st_ll.c but also the external modules/protocol drivers that are dependent on the shared transport driver. Modify the source files to include the new header ti_wilink_st.h, Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: set right the data typesPavan Savoy2010-09-202-21/+21
| | | | | | | | | replace uint and family by a much more proper u8/u16 types. This is required specifically for data members of structures coming in from the chip and data members parsed from the binary firmware file. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: fix kim platform device idPavan Savoy2010-09-161-1/+8
| | | | | | | | | | | Platform devices tend to have id as -1 when only 1 device exist and a value >=0 when multiple devices exist, since we plan to store all these platform devices if multiple exist, there was a requirement to have id to be >=0. The patch fixes this problem. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ST_BT depends on RFKILLRandy Dunlap2010-09-161-1/+1
| | | | | | | | | Fix kconfig unmet dependency warning: warning: (ST_BT && STAGING && !STAGING_EXCLUDE_BUILD && BT) selects TI_ST which has unmet direct dependencies (RFKILL) Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: remove st_get_plat_devicePavan Savoy2010-08-314-10/+24
| | | | | | | | | | | | | | | | | In order to support multiple ST platform devices, a new symbol 'st_get_plat_device' earlier needed to be exported by the arch/XX/brd-XX.c file which intends to add the ST platform device. On removing this dependency, now inside ST driver maintain the array of ST platform devices that would be registered. As of now let id=0, as and when we end up having such platforms where mutliple ST devices can exist, id would come from protocol drivers (BT, FM and GPS) as to on which platform device they want to register to. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Acked-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: writing past end of arrayDan Carpenter2010-08-311-3/+2
| | | | | | | | In the original source it would write past the end of the array before returning the error code. Signed-off-by: Dan Carpenter <error27@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: update TODOPavan Savoy2010-08-021-17/+1
| | | | | | | | | | | | | | | | | | | | | | Removed TODO item 2 : Current UIM/KIM communicate via the rfkill device and identified by the unique idx assisgned by the rfkill sub-system to each of these rfkill entries. Removed TODO item 1 : Since there is no way we can test existance of multiple connectivity devices on platform. However the basic infrastructure as in providing a context to ST driver exist. If multiple devices have to exist on a given platform, multiple ST platform devices need to be registered and each of the protocol drivers have to mention which platform device they want to bind to/make use of. Removed TODO item 3: Locking have been reviewed and commit 36b5aee46b5e4788758409829926c631de0a64a3 documents locking. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: update ABI and TODOPavan Savoy2010-07-282-7/+15
| | | | | | | | update TODO to reflect the items taken care of, update ABI to reflect the new debugfs entries exposed. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: mv sysfs entries to debugfsPavan Savoy2010-07-283-92/+51
| | | | | | | | | | | | When the chip is in use, information like the chip's ROM version and the protocols currently making use of the chip needs to be made known to user-space. Earlier the version and the protocol-list were exposed as sysfs entries now cleanup by making them as debugfs entries, also in process remove any unwanted/previously unused sysfs entries. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: give proto drivers contextPavan Savoy2010-07-223-12/+27
| | | | | | | | | | | | protocol drivers such as BT, FM and GPS when registering to ST now provide their own private data which they expect when their functions namely registration completed & receive are called. Also upon tty_close, set protos_registered count to 0, although all protocols are marked un-registered. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: cleanup code commentsPavan Savoy2010-07-226-117/+193
| | | | | | | | cleanup the code commenting in the headers/structures, also cleanup few inline commenting in the function Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: smarten, reduce logsPavan Savoy2010-07-223-46/+35
| | | | | | | | | | Replace looping on the data buffers and printk-ing by print_hex_dump. Also replace most of the pr_info by pr_debug to reduce logging at default loglevels (7 in our case..) Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: make use of linux err codesPavan Savoy2010-07-225-56/+47
| | | | | | | | remove custom error code definitions from the header and make use of the agreed upon linux error codes. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: remove global referencesPavan Savoy2010-07-085-33/+65
| | | | | | | | | | | | | Providing a context which can be passed around the driver, the KIM's platform driver's struct device to be used to dev_set_drvdata and dev_get_drvdata. The ST core's data is passed around using tty's disc_data and in other cases the ST KIM's platform device is exposed from the board-XX.c which adds KIM platform device whose dev is used. Thereby remove the need for the global reference struct kim_data_s *kim_gdata; Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: Update TODOPavan Savoy2010-07-081-1/+3
| | | | | | | | | | An important TODO was to remove global references in TI-ST driver, thereby providing a context to the driver. This should also serve as a small step in removal of the single device limit. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: Fix a typo in the Kconfig fileAndrea Gelmini2010-06-231-1/+1
| | | | | Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: fix protocol countingNaveen Jain2010-06-181-5/+8
| | | | | | | | | | | | | | | Older mechanism of counting the number of protocols registered with ST was slow, in-efficient. It used to check the protocol data for NULL for each registration/unregistration. With this change, counting protocols in maintained by a single counter protos_registered. Counting protocols is not just for debug purposes Signed-off-by: Naveen Jain <naveen_jain@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: add version info to sysfsNaveen Jain2010-06-182-5/+46
| | | | | | | | Add version information to be available under the sysfs group for kim. Signed-off-by: Naveen Jain <naveen_jain@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: ti-st: cleanup sysfs codeNaveen Jain2010-06-182-47/+6
| | | | | | | | | | | | | | | | Remove the older way of communicating with user-space daemon UIM. The older way involved creating of a new kobj and pid sysfs file under it, and sending signal using that pid. Now we communicate via rfkill to user-space UIM. Background: UIM is the user-space daemon which upon notification from ldisc driver, opens the tty, sets default baud and then installs (tiocsetd) the ldisc. Signed-off-by: Naveen Jain <naveen_jain@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: Update TI-ST's TODOPavan Savoy2010-06-181-2/+9
| | | | | | | | | Update the TODO of TI-ST to make sure it reflects current list of activities that need to be done. Also point it out to the user-space app code relevant to it. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* staging: ti-st: depends on RFKILLRandy Dunlap2010-05-111-0/+1
| | | | | | | | | | | | | | | | | | Fix build errors. st_kim.c uses rfkill*() interfaces, so it should depend on RFKILL. st_kim.c:(.text+0x291b21): undefined reference to `rfkill_unregister' st_kim.c:(.text+0x291b31): undefined reference to `rfkill_destroy' st_kim.c:(.text+0x291d8a): undefined reference to `rfkill_alloc' st_kim.c:(.text+0x291db9): undefined reference to `rfkill_init_sw_state' st_kim.c:(.text+0x291dc9): undefined reference to `rfkill_register' st_kim.c:(.text+0x291e07): undefined reference to `rfkill_unregister' (.text+0x291e85): undefined reference to `rfkill_set_hw_state' (.text+0x292072): undefined reference to `rfkill_set_hw_state' (.text+0x2920e1): undefined reference to `rfkill_set_hw_state Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: Kconfig, Makefile for TI's ST ldiscPavan Savoy2010-05-112-0/+31
| | | | | | | | This change adds the Kconfig and Make file for TI's ST line discipline driver and the BlueZ driver for BT core of the TI BT/FM/GPS combo chip. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
* Staging: bluetooth: BT driver using ST for TI combo devicesPavan Savoy2010-05-112-0/+563
| | | | | | | | This is BlueZ driver making use of Shared Transport line discipline to communicate with the chip. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: add TODO and ABI to ti-stPavan Savoy2010-05-112-0/+35
| | | | | | | | A TODO file and a ABI to list the things to be done, and user-space/kernel-space interface for this ldisc. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: sources for ST header filePavan Savoy2010-05-112-0/+103
| | | | | | | | | | | Texas Instruments BT, FM and GPS combo chips/drivers make use of a single TTY to communicate with the chip. This is the common header file for both the ST driver and the protocol drivers which intend to use ST as their mode of transport. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: sources for HCI LL PM protocolPavan Savoy2010-05-112-0/+209
| | | | | | | | | | Texas Instruments BT, FM and GPS combo chips/drivers make use of a single TTY to communicate with the chip. This module constitutes the proprietary power management protocol from TI for the BT/FM/GPS combo chips Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: sources for Init manager modulePavan Savoy2010-05-112-0/+904
| | | | | | | | | | | | | | | | Kernel Space Init-Manager works along with User-Mode Init Manager daemon running to maintain the UART state. Communication between user-space daemon and this module can be 1. Via the pid written onto sysfs entry 2. Via the rfkill subsystem It also is a platform driver with a relevant platform device in the board-*.c along with the list of BT/FM/GPS chip enable gpio configuration Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
* Staging: sources for ST corePavan Savoy2010-05-112-0/+1160
Texas Instruments BT, FM and GPS combo chips/drivers make use of a single TTY to communicate with the chip. This module constitutes the core logic, TTY ldisc driver and the exported symbols for registering/unregistering of the protocol drivers such as BT/FM/GPS. Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
generated by cgit v1.1 at 2024-09-10 15:47:02 +0000