linux-toradex.git/drivers, branch v3.2.19

i2c: davinci: Free requested IRQ in remove

2012-05-30T23:44:07+00:00

commit 9868a060ccf769c08ec378a9829137e272e9a92c upstream.

The freed IRQ is not necessary the one requested in probe.
Even if it was, with two or more i2c-controllers it will fails anyway.

Signed-off-by: Marcus Folkesson 
Signed-off-by: Wolfram Sang 
Signed-off-by: Ben Hutchings

i2c: tegra: notify transfer-complete after clearing status.

2012-05-30T23:44:07+00:00

commit c889e91d2cc22123f20f40dde0c0a91856a20eea upstream.

The notification of the transfer complete by calling complete()
should be done after clearing all interrupt status.
This avoids the race condition of misconfigure the i2c controller
in multi-core environment.

Signed-off-by: Laxman Dewangan 
Acked-by: Stephen Warren 
Signed-off-by: Wolfram Sang 
Signed-off-by: Ben Hutchings

rtlwifi: Preallocate USB read buffers and eliminate kalloc in read routine

2012-05-30T23:44:05+00:00

commit a7959c1394d4126a70a53b914ce4105f5173d0aa upstream.

The current version of rtlwifi for USB operations uses kmalloc to
acquire a 32-bit buffer for each read of the device. When
_usb_read_sync() is called with the rcu_lock held, the result is
a "sleeping function called from invalid context" BUG. This is
reported for two cases in https://bugzilla.kernel.org/show_bug.cgi?id=42775.
The first case has the lock originating from within rtlwifi and could
be fixed by rearranging the locking; however, the second originates from
within mac80211. The kmalloc() call is removed from _usb_read_sync()
by creating a ring buffer pointer in the private area and
allocating the buffer data in the probe routine.

Signed-off-by: Larry Finger 
Signed-off-by: John W. Linville 
[This version will apply to 3.2 and earlier. - Larry]
Signed-off-by: Ben Hutchings

drivers/rtc/rtc-pl031.c: configure correct wday for 2000-01-01

2012-05-30T23:44:04+00:00

commit c0a5f4a05af588a0f9951f8d24e2564b09501918 upstream.

The reset date of the ST Micro version of PL031 is 2000-01-01.  The
correct weekday for 2000-01-01 is saturday, but pl031 is initialized to
sunday.  This may lead to alarm malfunction, so configure the correct
wday if RTC_DR indicates reset.

Signed-off-by: Rajkumar Kasirajan 
Signed-off-by: Linus Walleij 
Cc: Mattias Wallin 
Cc: Alessandro Zummo 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: Ben Hutchings

ethtool: Null-terminate filename passed to ethtool_ops::flash_device

2012-05-30T23:44:03+00:00

commit 786f528119722f564a22ad953411374e06116333 upstream.

The parameters for ETHTOOL_FLASHDEV include a filename, which ought to
be null-terminated.  Currently the only driver that implements
ethtool_ops::flash_device attempts to add a null terminator if
necessary, but does it wrongly.  Do it in the ethtool core instead.

Signed-off-by: Ben Hutchings 
Signed-off-by: David S. Miller 
Signed-off-by: Ben Hutchings

intel-iommu: Add device info into list before doing context mapping

2012-05-30T23:44:03+00:00

commit e2ad23d04c1304431ab5176c89b7b476ded2d995 upstream.

Add device info into list before doing context mapping, because device
info will be used by iommu_enable_dev_iotlb(). Without it, ATS won't get
enabled as it should be.

ATS, while a dubious decision from a security point of view, can be very
important for performance.

Signed-off-by: Xudong Hao 
Signed-off-by: Xiantao Zhang 
Acked-by: Chris Wright 
Signed-off-by: David Woodhouse 
Signed-off-by: Linus Torvalds 
Signed-off-by: Ben Hutchings

nouveau: nouveau_set_bo_placement takes TTM flags

2012-05-30T23:44:01+00:00

commit c284815debba2f14ee2fd07b1b4cc972ab116110 upstream.

This seems to be wrong to me, spotted while thinking about dma-buf.

Reviewed-by: Ben Skeggs 
Signed-off-by: Dave Airlie 
Signed-off-by: Ben Hutchings

xen: do not map the same GSI twice in PVHVM guests.

2012-05-30T23:44:01+00:00

commit 68c2c39a76b094e9b2773e5846424ea674bf2c46 upstream.

PV on HVM guests map GSIs into event channels. At restore time the
event channels are resumed by restore_pirqs.

Device drivers might try to register the same GSI again through ACPI at
restore time, but the GSI has already been mapped and bound by
restore_pirqs. This patch detects these situations and avoids
 mapping the same GSI multiple times.

Without this patch we get:
(XEN) irq.c:2235: dom4: pirq 23 or emuirq 28 already mapped
and waste a pirq.

Signed-off-by: Stefano Stabellini 
Signed-off-by: Konrad Rzeszutek Wilk 
Signed-off-by: Ben Hutchings

spi/spi-fsl-spi: reference correct pdata in fsl_spi_cs_control

2012-05-30T23:44:00+00:00

commit 067aa4815a9bc12a569d8a06afef50ba5773afbf upstream.

Commit 178db7d3, "spi: Fix device unregistration when unregistering
the bus master", changed spi device initialization of dev.parent pointer
to be the master's device pointer instead of his parent.

This introduced a bug in spi-fsl-spi, since its usage of spi device
pointer was not updated accordingly. This was later fixed by commit
5039a86, "spi/mpc83xx: fix NULL pdata dereference bug", but it missed
another spot on fsl_spi_cs_control function where we also need to update
usage of spi device pointer. This change address that.

Signed-off-by: Herton Ronaldo Krzesinski 
Acked-by: Joakim Tjernlund 
Signed-off-by: Grant Likely 
Signed-off-by: Ben Hutchings

drm/i915: don't clobber the pipe param in sanitize_modesetting

2012-05-30T23:44:00+00:00

commit a9dcf84b14ef4e9a609910367576995e6f32f3dc upstream.

... we need it later on in the function to clean up pipe <-> plane
associations. This regression has been introduced in

commit f47166d2b0001fcb752b40c5a2d4db986dfbea68
Author: Chris Wilson 
Date:   Thu Mar 22 15:00:50 2012 +0000

    drm/i915: Sanitize BIOS debugging bits from PIPECONF

Spotted by staring at debug output of an (as it turns out) totally
unrelated bug.

v2: I've totally failed to do the s/pipe/i/ correctly, spotted by
Chris Wilson.

Reviewed-by: Chris Wilson 
Reviewed-by: Eugeni Dodonov 
Signed-Off-by: Daniel Vetter 
Signed-off-by: Ben Hutchings