MTD: devices: Add support for serial flash Micron N25Q032
Updated CuBox init spi flash name: w25q32 to n25q032.
This removes the kernel warning: "m25p80 spi0.0: found n25q032, expected w25q32".
tty vt: Fix line garbage in virtual console on command line edition

On some machines using a specific hardware for console screen output,
the update of the pixel frame buffer does not work correctly when
using command line edition. This may be due to a memory cache bug
in the machine on which the problem has been found, but an other
solution is possible.

This patch proposes to avoid touching directly the pixel frame buffer
and to rebuild each character using the standard putc() function
on command line edition.

The resulting code is smaller and not obviously slower (no read
access to the pixel frame buffer).

Tested on a Cubox (ARM Marvell Dove 88AP510 SoC).

Signed-off-by: Jean-François Moine <moinejf@free.fr>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net: remove skb recycling

Over time, skb recycling infrastructure got litle interest and
many bugs. Generic rx path skb allocation is now using page
fragments for efficient GRO / TCP coalescing, and recyling
a tx skb for rx path is not worth the pain.

Last identified bug is that fat skbs can be recycled
and it can endup using high order pages after few iterations.

With help from Maxime Bizon, who pointed out that commit
87151b8689d (net: allow pskb_expand_head() to get maximum tailroom)
introduced this regression for recycled skbs.

Instead of fixing this bug, lets remove skb recycling.

Drivers wanting really hot skbs should use build_skb() anyway,
to allocate/populate sk_buff right before netif_receive_skb()

Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Maxime Bizon <mbizon@freebox.fr>
Signed-off-by: David S. Miller <davem@davemloft.net>

Conflicts:
	drivers/net/ethernet/calxeda/xgmac.c
	drivers/net/ethernet/freescale/gianfar.c
Wrong usage of BMM cache flushing

Wrong usage of flushing API.
Instead of using the dmac_map_area, dmac_flush_range must be used since the first is restricted to kernel space only and the latter can accept both kernel and user area.
The reason is the BMM allocates and maps buffers into a user area where the addresses that can be used are not kernel.

This fixes an issue that cache flushing BMM buffers allocated to vmeta makes a kernel panic

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
Enable PCM format S24_LE
Enforce PCM mode when not sending a bitstream
Disable I2S on channel 1 and SPDIF on channel 0
Always set SPDIF channel status bits
Return error code when CEC device in bad state
Don't set HDMI audio rate when not plugged
Merge branch 'thirsty-patched' into v3.5.7-patched