spi-bcm2708: add 9-bit support using LoSSI mode
dwc_otg: implement tasklet for returning URBs to usbcore hcd layer

The dwc_otg driver interrupt handler for transfer completion will spend
a very long time with interrupts disabled when a URB is completed -
this is because usb_hcd_giveback_urb is called from within the handler
which for a USB device driver with complicated processing (e.g. webcam)
will take an exorbitant amount of time to complete. This results in
missed completion interrupts for other USB packets which lead to them
being dropped due to microframe overruns.

This patch splits returning the URB to the usb hcd layer into a
high-priority tasklet. This will have most benefit for isochronous IN
transfers but will also have incidental benefit where multiple periodic
devices are active at once.
Added Device IDs for August DVB-T 205
Merge pull request #202 from notro/LoSSI

spi-bcm2708: add 9-bit support using LoSSI mode
Merge pull request #258 from abzieher/rpi-3.6.y

Added Device IDs for August DVB-T 205
Merge pull request #255 from P33M/rpi-3.6.y

dwc_otg: implement tasklet for returning URBs to usbcore hcd layer
Revert "ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations"

This reverts commit 690c641b4aeefa1df72ae783613afcb6b8ae7347.

There have been various reports of FAT partition corruption following this commit. Reverting for now to see if things improve.
Move definition of fiq_fix_enable to bcm2708.c to allow building without dwc_otg
Revert back to smaller alsa buffer
w1: fix oops when w1_search is called from netlink connector

On Sat, Mar 02, 2013 at 10:45:10AM +0100, Sven Geggus wrote:
> This is the bad commit I found doing git bisect:
> 04f482faf50535229a5a5c8d629cf963899f857c is the first bad commit
> commit 04f482faf50535229a5a5c8d629cf963899f857c
> Author: Patrick McHardy <kaber@trash.net>
> Date:   Mon Mar 28 08:39:36 2011 +0000

Good job. I was too lazy to bisect for bad commit;)

Reading the code I found problematic kthread_should_stop call from netlink
connector which causes the oops. After applying a patch, I've been testing
owfs+w1 setup for nearly two days and it seems to work very reliable (no
hangs, no memleaks etc).
More detailed description and possible fix is given below:

Function w1_search can be called from either kthread or netlink callback.
While the former works fine, the latter causes oops due to kthread_should_stop
invocation.

This patch adds a check if w1_search is serving netlink command, skipping
kthread_should_stop invocation if so.

Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com>
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Josh Boyer <jwboyer@gmail.com>
Tested-by: Sven Geggus <lists@fuchsschwanzdomain.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org> # 3.0+
Update rtl8192cu driver to 3.4.4_4749
Add IP_VS modules to kernel
defconfig: Add CRYPTO_NULL, CRYPTO_USER, CRYPTO_CRYPTD modules
dwc_otg: fix NAK holdoff and allow on split transactions only

This corrects a bug where if a single active non-periodic endpoint
had at least one transaction in its qh, on frnum == MAX_FRNUM the qh
would get skipped and never get queued again. This would result in
a silent device until error detection (automatic or otherwise) would
either reset the device or flush and requeue the URBs.

Additionally the NAK holdoff was enabled for all transactions - this
would potentially stall a HS endpoint for 1ms if a previous error state
enabled this interrupt and the next response was a NAK. Fix so that
only split transactions get held off.
Merge pull request #279 from P33M/rpi-3.6.y

dwc_otg: fix NAK holdoff and allow on split transactions only