kernel_goldelico_gta04.git - kernel/goldelico/gta04

	Commit message (Collapse)	Author	Age	Files	Lines
*	Bluetooth: Add delayed init sequence support for UART controllers	Johan Hedberg	2012-07-17	1	-0/+5
\| \| \| \| \| \| \| \| \| \|	This patch makes it possible to have UART drivers perform an internal initialization before calling hci_register_dev. This allows moving a lot of init code from user space (hciattach) to the kernel side, thereby creating a more controlled/robust initialization process. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
*	Bluetooth: Initial skeleton for Three-wire UART (H5) support	Johan Hedberg	2012-07-17	1	-0/+5
\| \| \| \| \| \| \| \|	This patch adds the initial skeleton for Three-wire UART (H5) support and hooks it up to the HCI UART framework. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
*	Bluetooth: Add support for creating HCI UART based AMP controllers	Marcel Holtmann	2012-02-24	1	-0/+1
\| \| \| \| \| \| \| \|	In reality this might never be used for real hardware, but it is a nice feature for emulating AMP controllers within a virtual machine. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
*	Bluetooth: Allow HCI UART reset parameter via flags ioctl	Marcel Holtmann	2012-02-24	1	-0/+1
\| \| \| \| \| \| \| \| \|	The flags ioctl for HCI UART drivers already allows setting of certain Bluetooth core quirks. The reset parameter fits right in here. So allow this as well. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
*	Bluetooth: Support for Atheros AR300x serial chip	Suraj Sumangala	2010-07-21	1	-1/+7
\| \| \| \| \| \| \| \| \| \|	Implements Atheros AR300x serial HCI protocol. This protocol extends H4 serial protocol to implement enhanced power management features supported by Atheros AR300x serial Bluetooth chipsets. Signed-off-by: Suraj Sumangala <suraj@atheros.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
*	Bluetooth: Add HCIUARTSETFLAGS and HCIUARTGETFLAGS ioctls	Johan Hedberg	2010-07-21	1	-1/+6
\| \| \| \| \| \| \| \| \| \| \|	This patch introduces two new ioctls: HCIUARTSETFLAGS and HCIUARTGETFLAGS. The only flag available for now is HCI_UART_RAW_DEVICE which allows to initialize a UART device into RAW mode from userspace. This is particularly useful for experimenting with Bluetooth controllers that don't yet have proper support in BlueZ. Signed-off-by: Johan Hedberg <johan.hedberg@nokia.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
*	[Bluetooth] Add UART driver for Texas Instruments' BRF63xx chips	Ohad Ben-Cohen	2007-10-22	1	-1/+7
\| \| \| \| \| \| \| \| \|	Add support for Texas Instruments' HCI Low Level (HCILL) Bluetooth protocol, which is a power management extension to H4. The HCILL is widely used by TI's BRF63xx Bluetooth chips. Signed-off-by: Ohad Ben-Cohen <ohad@bencohen.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
*	[Bluetooth] Add HCIUARTGETDEVICE support for HCI line discipline	Marcel Holtmann	2007-05-10	1	-2/+3
\| \| \| \| \| \| \| \| \|	Adding HCIUARTGETDEVICE makes it possible to get the HCI device number that is attached to a given serial device. This is required during the initialization process of some Bluetooth chips. Signed-off-by: Ohad Ben-Cohen <ohad@bencohen.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
*	[Bluetooth] Cleanup of the HCI UART driver	Marcel Holtmann	2005-10-28	1	-40/+44
\| \| \| \| \| \| \| \|	This patch contains the big cleanup of the HCI UART driver. The uneeded header files are removed and their structure declarations are moved into the protocol implementations. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+82
	Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!