- 08 11月, 2011 2 次提交
-
-
由 Paul Fertser 提交于
This makes it much easier for the users to understand why the driver refuses to load when the firmware is unavailable. Signed-off-by: NPaul Fertser <fercerpav@gmail.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 David Herrmann 提交于
Make all bluetooth drivers ignore the return value of hci_unregister_dev as it always returns 0. In the next step, hci_unregister_dev can be modified to return void. Some of the drivers already ignore the return value (including btusb), hence, this will increase consitency in the bluetooth drivers. Signed-off-by: NDavid Herrmann <dh.herrmann@googlemail.com> Acked-by: NMarcel Holtmann <marcel@holtmann.org> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 11 10月, 2011 2 次提交
-
-
由 Paul Bolle 提交于
There are still three calls of usb_submit_urb() that will print errors if those calls return -EPERM or -ENODEV. I have never triggered these, so I'm not sure when these return values might be seen. It still makes sense to be silent if these occur (since "urb is being killed" and "device got disconnected" aren't things to worry about). Signed-off-by: NPaul Bolle <pebolle@tiscali.nl> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Paul Bolle 提交于
usb_submit_urb() returns -ENODEV when a usb device is disconnected. In commit 4935f1c1 ("Bluetooth: btusb: be quiet on device disconnect") I stopped treating that return as an error in the three btusb_*_complete() functions. It turns out btusb_send_frame() generates a similar error if the system is suspended while the bluetooth usb device is enabled. The sensible thing to do here seems to be to treat -ENODEV (and -EPERM) just like the btusb_*_complete() functions now do. Signed-off-by: NPaul Bolle <pebolle@tiscali.nl> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 30 9月, 2011 1 次提交
-
-
由 Oliver Neukum 提交于
From 0cea73465cd22373c5cd43a3edd25fbd4bb532ef Mon Sep 17 00:00:00 2001 From: Oliver Neukum <oliver@neukum.org> Date: Wed, 21 Sep 2011 11:37:15 +0200 Subject: [PATCH] btusb: add device entry for Broadcom SoftSailing This device declares itself to be vendor specific It therefore needs to be added to the device table to make btusb bind. Signed-off-by: NOliver Neukum <oneukum@suse.de> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 28 9月, 2011 1 次提交
-
-
由 Peter Hurley 提交于
Removed tests which prevent transmission of ACL packets when the device is in HCI_RAW mode. These tests verified that there are ACL or LE links currently tracked by the HCI connection manager. However, a HCI_RAW mode device does not use the connection manager. In these circumstances, the connection counts will be zero, and thus, transmitted ACL packets dropped. The acl_num test is actually a vestige of a previous bulk URB scheme that is no longer used by this driver (bulk URBs were not started until at least one ACL connection was created). This was incompatible with some endpoint implementations and was dropped - see commit 43c2e57f. The utility of these tests is marginal - currently, the hci tx scheduler cannot send an ACL or LE packet for an untracked connection (except if the device is in HCI_RAW mode). Lastly, no other transport layer driver enforces these same tests. Signed-off-by: NPeter Hurley <peter@hurleysoftware.com> Acked-by: NAcked-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 18 9月, 2011 3 次提交
-
-
由 Jurgen Kramer 提交于
Today I noticed that the usb bluetooth adapter (BCM2046B1) on my 2011 mac mini was not working. I've created a patch to get it going. Signed-off-by: NJurgen Kramer <gtmkramer@xs4all.nl> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
This patch against current git adds the hardware ID for the Apple MacBookAir4,1, released in July 2011. The device features a BCM2046 USB chip. The patch was inspired by the previous modifications adding support for the MacBookAir3,x. Signed-off-by: NPieter-Augustijn Van Malleghem <p-a@scarlet.be> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Chen Ganir 提交于
Reordered the BT ST channel registration, to make sure that the event channel is registered before all others. This prevents a situation where incoming events may cause kernel panic in the ST driver if the event channel is not yet registered to handle incoming events.In addition, the deregistration of the channels was also modified, to be in the reversed order of the registration, to allow the event channel to be the last one unregistered. Signed-off-by: NChen Ganir <chen.ganir@ti.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 12 8月, 2011 2 次提交
-
-
由 Ricardo Mendoza 提交于
Blacklist Toshiba-branded AR3011 based AR5B195 [0930:0215] and add to ath3k.c for firmware loading. Signed-off-by: NRicardo Mendoza <ricmm@gentoo.org> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Paul Bolle 提交于
Disabling the bluetooth usb device embedded in (some) ThinkPads tends to lead to errors like these: btusb_bulk_complete: hci0 urb ffff88011b9bfd68 failed to resubmit (19) btusb_intr_complete: hci0 urb ffff88011b46a318 failed to resubmit (19) btusb_bulk_complete: hci0 urb ffff88011b46a000 failed to resubmit (19) That is because usb_disconnect() doesn't "quiesces" pending urbs. Disconnecting a device is a normal thing to happen so it's no big deal that usb_submit_urb() returns -ENODEV. The simplest way to get rid of these errors is to stop treating that return as an error. Trivial, actually. While we're at it, add comments to be explicit about the reasons we're not complaining about -EPERM and -ENODEV. Signed-off-by: NPaul Bolle <pebolle@tiscali.nl> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 02 7月, 2011 1 次提交
-
-
由 Steven.Li 提交于
The new Ath3k needs to download patch and radio table, and it keeps same PID/VID even after downloading the patch and radio table. This patch is to use the bcdDevice (Device Release Number) to judge whether the chip has been patched or not. The init bcdDevice value of the chip is 0x0001, this value increases after patch and radio table downloading. Signed-off-by: NSteven.Li <yongli@qca.qualcomm.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 11 6月, 2011 1 次提交
-
-
由 David Miller 提交于
Signed-off-by: NDavid S. Miller <davem@davemloft.net> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 10 6月, 2011 1 次提交
-
-
由 David Miller 提交于
Signed-off-by: NDavid S. Miller <davem@davemloft.net> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 04 6月, 2011 1 次提交
-
-
由 Linus Torvalds 提交于
This reverts commit b1c43f82. It was broken in so many ways, and results in random odd pty issues. It re-introduced the buggy schedule_work() in flush_to_ldisc() that can cause endless work-loops (see commit a5660b41: "tty: fix endless work loop when the buffer fills up"). It also used an "unsigned int" return value fo the ->receive_buf() function, but then made multiple functions return a negative error code, and didn't actually check for the error in the caller. And it didn't actually work at all. BenH bisected down odd tty behavior to it: "It looks like the patch is causing some major malfunctions of the X server for me, possibly related to PTYs. For example, cat'ing a large file in a gnome terminal hangs the kernel for -minutes- in a loop of what looks like flush_to_ldisc/workqueue code, (some ftrace data in the quoted bits further down). ... Some more data: It -looks- like what happens is that the flush_to_ldisc work queue entry constantly re-queues itself (because the PTY is full ?) and the workqueue thread will basically loop forver calling it without ever scheduling, thus starving the consumer process that could have emptied the PTY." which is pretty much exactly the problem we fixed in a5660b41. Milton Miller pointed out the 'unsigned int' issue. Reported-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org> Reported-by: NMilton Miller <miltonm@bga.com> Cc: Stefan Bigler <stefan.bigler@keymile.com> Cc: Toby Gray <toby.gray@realvnc.com> Cc: Felipe Balbi <balbi@ti.com> Cc: Greg Kroah-Hartman <gregkh@suse.de> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk> Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
-
- 12 5月, 2011 1 次提交
-
-
由 Andy Ross 提交于
New ath3k device IDs used on the Pegatron Lucid (ExoPC and WeTab) units. Signed-off-by: NAndy Ross <andy.ross@windriver.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 06 5月, 2011 1 次提交
-
-
由 Joe Perches 提交于
Saves about 50KB of data. Old/new size of all objects: text data bss dec hex filename 563015 80096 130684 773795 bcea3 (TOTALS) 610916 32256 130632 773804 bceac (TOTALS) Signed-off-by: NJoe Perches <joe@perches.com> Acked-by: Kurt Van Dijck <kurt.van.dijck@eia.be> (for drivers/net/can/softing/softing_cs.c) Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 23 4月, 2011 1 次提交
-
-
由 Felipe Balbi 提交于
it makes it simpler to keep track of the amount of bytes received and simplifies how flush_to_ldisc counts the remaining bytes. It also fixes a bug of lost bytes on n_tty when flushing too many bytes via the USB serial gadget driver. Tested-by: NStefan Bigler <stefan.bigler@keymile.com> Tested-by: NToby Gray <toby.gray@realvnc.com> Signed-off-by: NFelipe Balbi <balbi@ti.com> Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
-
- 13 4月, 2011 4 次提交
-
-
由 Kevin Gan 提交于
The SD8787 firmware image is shared with mwifiex driver. Whoever gets loaded first will be responsible for firmware downloading. Signed-off-by: NKevin Gan <ganhy@marvell.com> Signed-off-by: NTristan Xu <xurf@marvell.com> Signed-off-by: NBing Zhao <bzhao@marvell.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Gustavo F. Padovan 提交于
It may return error and in this case we do add to the stats. Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi> -
由 Jiejing Zhang 提交于
Check the return value of hu->proto->recv() in hci_uart_tty_receive() the recv() may return error, check it, not add this to statistics. Signed-off-by: NJiejing Zhang <jiejing.zhang@freescale.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Gustavo F. Padovan 提交于
Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 01 4月, 2011 2 次提交
-
-
由 Vinicius Costa Gomes 提交于
Now that we have support for LE connections, before discarding a frame we must check if there's a LE connection over that transport. Signed-off-by: NVinicius Costa Gomes <vinicius.gomes@openbossa.org> Acked-by: NVille Tervo <ville.tervo@nokia.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Marc-Antoine Perennou 提交于
Just adding the vendor details makes it work fine. Signed-off-by: NMarc-Antoine Perennou <Marc-Antoine@Perennou.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 31 3月, 2011 1 次提交
-
-
由 Lucas De Marchi 提交于
Fixes generated by 'codespell' and manually reviewed. Signed-off-by: NLucas De Marchi <lucas.demarchi@profusion.mobi>
-
- 25 3月, 2011 2 次提交
-
-
由 Vinicius Costa Gomes 提交于
Now that we have support for LE connections, before discarding a frame we must check if there's a LE connection over that transport. Signed-off-by: NVinicius Costa Gomes <vinicius.gomes@openbossa.org> Acked-by: NVille Tervo <ville.tervo@nokia.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Marc-Antoine Perennou 提交于
Just adding the vendor details makes it work fine. Signed-off-by: NMarc-Antoine Perennou <Marc-Antoine@Perennou.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 24 2月, 2011 2 次提交
-
-
由 Linus Torvalds 提交于
This reverts commit 556ea928. Jeff Chua reports that it can cause some bluetooth devices (he mentions an Bluetooth Intermec scanner) to just stop responding after a while with messages like [ 4533.361959] btusb 8-1:1.0: no reset_resume for driver btusb? [ 4533.361964] btusb 8-1:1.1: no reset_resume for driver btusb? from the kernel. See also https://bugzilla.kernel.org/show_bug.cgi?id=26182 for other reports. Reported-by: NJeff Chua <jeff.chua.linux@gmail.com> Reported-by: NAndrew Meakovski <meako@bigmir.net> Reported-by: NJim Faulkner <jfaulkne@ccs.neu.edu> Acked-by: NGreg KH <gregkh@suse.de> Acked-by: NMatthew Garrett <mjg@redhat.com> Acked-by: NGustavo F. Padovan <padovan@profusion.mobi> Cc: stable@kernel.org (for 2.6.37) Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
-
由 Pavan Savoy 提交于
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: NPavan Savoy <pavan_savoy@ti.com> Acked-by: NGustavo F. Padovan <padovan@profusion.mobi> Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
-
- 18 2月, 2011 1 次提交
-
-
由 Alan Cox 提交于
Was this exploitable - who knows, but it was certainly totally broken Signed-of-by: NAlan Cox <alan@linux.intel.com> Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
-
- 17 2月, 2011 4 次提交
-
-
由 Andrei Warkentin 提交于
Make /sys/class/bluetooth/hciX a symlink to path under corresponding tty. Signed-off-by: NAndrei Warkentin <andreiw@motorola.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Gustavo F. Padovan 提交于
Instead set urb structure directly we call usb_fill_int_urb() to set the values to us. Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi> -
由 Cho, Yu-Chen 提交于
Add the btusb.c blacklist [0489:e02c] for Atheros AR5BBU12 BT and add to ath3k.c supported this device. Signed-off-by: NCho, Yu-Chen <acho@novell.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
由 Oliver Neukum 提交于
Quirky dongles sometimes do not use the iso interface which causes a crash with runtime PM Signed-off-by: NOliver Neukum <oneukum@suse.de> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 12 2月, 2011 1 次提交
-
-
由 Bala Shanmugam 提交于
Blacklisted AR3012 PID in btusb and added the same in ath3k to load patch and sysconfig files. Signed-off-by: NBala Shanmugam <sbalashanmugam@atheros.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 08 2月, 2011 1 次提交
-
-
由 Rogério Brito 提交于
In commit 86e09287, to reduce memory usage, the functions of the ath3k module were rewritten to release the firmware blob after it has been loaded (successfully or not). The resuting code has some redundancy and the compiler can potentially produce better code if we omit a function call that is unconditionally executed in ,---- | if (ath3k_load_firmware(udev, firmware)) { | release_firmware(firmware); | return -EIO; | } | release_firmware(firmware); | | return 0; | } `---- It may also be argued that the rewritten code becomes easier to read, and also to see the code coverage of the snippet in question. Signed-off-by: NRogério Brito <rbrito@ime.usp.br> Cc: Alexander Holler <holler@ahsoftware.de> Cc: "Gustavo F. Padovan" <padovan@profusion.mobi> Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 27 1月, 2011 1 次提交
-
-
由 Cho, Yu-Chen 提交于
Add the btusb.c blacklist [03f0:311d] for Atheros AR9285 Malbec BT and add to ath3k.c ath3-1.fw (md5:1211fa34c09e10ba48381586b7c3883d) supported this device. Signed-off-by: NCho, Yu-Chen <acho@novell.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 20 1月, 2011 1 次提交
-
-
由 Alexander Holler 提交于
There is no need to hold the firmware in memory. Signed-off-by: NAlexander Holler <holler@ahsoftware.de> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-
- 19 1月, 2011 1 次提交
-
-
由 Jesper Juhl 提交于
Fix a bunch of warning: ‘inline’ is not at beginning of declaration messages when building a 'make allyesconfig' kernel with -Wextra. These warnings are trivial to kill, yet rather annoying when building with -Wextra. The more we can cut down on pointless crap like this the better (IMHO). A previous patch to do this for a 'allnoconfig' build has already been merged. This just takes the cleanup a little further. Signed-off-by: NJesper Juhl <jj@chaosbits.net> Signed-off-by: NJiri Kosina <jkosina@suse.cz>
-
- 08 12月, 2010 1 次提交
-
-
由 Jun Nie 提交于
If we fail to find a hci device pointer in hci_uart, don't try to deref the NULL one we do have. Signed-off-by: NJun Nie <njun@marvell.com> Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
-