13 Mar, 2012
40 commits
-
commit 1bd612a25855f4cc9345052b53d7da697dba6358 upstream.
Also update IDT datasheet locations.
Signed-off-by: Guenter Roeck
Acked-by: Jean Delvare
Signed-off-by: Greg Kroah-Hartman -
commit 4de86126a712ba83fa038d277c8282f7ed466a4b upstream.
These are fully compatible with Jedec JC 42.4 as far as I can see.
Signed-off-by: Jean Delvare
Cc: Guenter Roeck
Signed-off-by: Guenter Roeck
Signed-off-by: Greg Kroah-Hartman -
commit 7cb3c44fb1f7999e4c53b6a52de6bc25da6de079 upstream.
There are up to three POUT alarm attributes, not two, since cap_alarm was added.
Reported-by: Michele Petracca
Signed-off-by: Guenter Roeck
Signed-off-by: Greg Kroah-Hartman -
commit 99c90ab31fad855b9da9dee3a5aa6c27f263e9d6 upstream.
ALPS touchpad detection fails if some buttons of ALPS are pressed.
The reason is that the "E6" query response byte is different from
what is expected.This was tested on a Toshiba Portege R500.
Signed-off-by: Akio Idehara
Tested-by: Seth Forshee
Signed-off-by: Dmitry Torokhov
Signed-off-by: Greg Kroah-Hartman -
commit affc9a0d59ac49bd304e2137bd5e4ffdd6fdfa52 upstream.
lirc_serial_probe() must fail if request_irq() returns an error, even if
it isn't EBUSY or EINVAL,Signed-off-by: Ben Hutchings
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Jonathan Nieder
Signed-off-by: Greg Kroah-Hartman -
commit 1ff1d88e862948ae5bfe490248c023ff8ac2855d upstream.
A resume function cannot remove the device it is resuming!
Signed-off-by: Ben Hutchings
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Jonathan Nieder
Signed-off-by: Greg Kroah-Hartman -
commit c8e57e1b766c2321aa76ee5e6878c69bd2313d62 upstream.
Failure to allocate the I/O region leaves the IRQ allocated.
A later failure leaves them both allocated.Reported-by: Torsten Crass
Signed-off-by: Ben Hutchings
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Jonathan Nieder
Signed-off-by: Greg Kroah-Hartman -
commit 9105b8b200410383d0854bbe237ee385d7d33ba6 upstream.
Currently the module init function registers a platform_device and
only then allocates its IRQ and I/O region. This allows allocation to
race with the device's suspend() function. Instead, allocate
resources in the platform driver's probe() function and free them in
the remove() function.The module exit function removes the platform device before the
character device that provides access to it. Change it to reverse the
order of initialisation.Signed-off-by: Ben Hutchings
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Jonathan Nieder
Signed-off-by: Greg Kroah-Hartman -
commit 3f31ae121348afd9ed39700ea2a63c17cd7eeed1 upstream.
xscale2 PMUs indicate overflow not via the PMU control register, but by
a separate overflow FLAG register instead.This patch fixes the xscale2 PMU code to use this register to detect
to overflow and ensures that we clear any pending overflow when
disabling a counter.Signed-off-by: Will Deacon
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman -
commit f6f5a30c834135c9f2fa10400c59ebbdd9188567 upstream.
The PMU IRQ handlers in perf assume that if a counter has overflowed
then perf must be responsible. In the paranoid world of crazy hardware,
this could be false, so check that we do have a valid event before
attempting to dereference NULL in the interrupt path.Signed-off-by: Ming Lei
Signed-off-by: Will Deacon
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman -
commit 99c1745b9c76910e195889044f914b4898b7c9a5 upstream.
When disabling a counter on an ARMv7 PMU, we should also clear the
overflow flag in case an overflow occurred whilst stopping the counter.
This prevents a spurious overflow being picked up later and leading to
either false accounting or a NULL dereference.Reported-by: Ming Lei
Signed-off-by: Will Deacon
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman -
commit 5727347180ebc6b4a866fcbe00dcb39cc03acb37 upstream.
On ARM, the PMU does not stop counting after an overflow and therefore
IRQ latency affects the new counter value read by the kernel. This is
significant for non-sampling runs where it is possible for the new value
to overtake the previous one, causing the delta to be out by up to
max_period events.Commit a737823d ("ARM: 6835/1: perf: ensure overflows aren't missed due
to IRQ latency") attempted to fix this problem by allowing interrupt
handlers to pass an overflow flag to the event update function, causing
the overflow calculation to assume that the counter passed through zero
when going from prev to new. Unfortunately, this doesn't work when
overflow occurs on the perf_task_tick path because we have the flag
cleared and end up computing a large negative delta.This patch removes the overflow flag from armpmu_event_update and
instead limits the sample_period to half of the max_period for
non-sampling profiling runs.Signed-off-by: Ming Lei
Signed-off-by: Will Deacon
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman -
commit efbc74ace95338484f8d732037b99c7c77098fce upstream.
Erratum #743622 affects all r2 variants of the Cortex-A9 processor, so
ensure that the workaround is applied regardless of the revision.Reported-by: Russell King
Signed-off-by: Will Deacon
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman -
commit ca888a7958b3d808e4efd08ceff88913f4212c69 upstream.
The "OMAPDSS: HDMI: PHY burnout fix" commit switched the HDMI driver
over to using a GPIO for plug detect. Unfortunately the ->detect()
method was not also updated, causing HDMI to no longer work for the
omapdrm driver (because it would actually check if a connection was
detected before attempting to enable display).Signed-off-by: Rob Clark
Signed-off-by: Tomi Valkeinen
Signed-off-by: Greg Kroah-Hartman -
commit c49d005b6cc8491fad5b24f82805be2d6bcbd3dd upstream.
A hardware bug in the OMAP4 HDMI PHY causes physical damage to the board
if the HDMI PHY is kept powered on when the cable is not connected.This patch solves the problem by adding hot-plug-detection into the HDMI
IP driver. This is not a real HPD support in the sense that nobody else
than the IP driver gets to know about the HPD events, but is only meant
to fix the HW bug.The strategy is simple: If the display device is turned off by the user,
the PHY power is set to OFF. When the display device is turned on by the
user, the PHY power is set either to LDOON or TXON, depending on whether
the HDMI cable is connected.The reason to avoid PHY OFF when the display device is on, but the cable
is disconnected, is that when the PHY is turned OFF, the HDMI IP is not
"ticking" and thus the DISPC does not receive pixel clock from the HDMI
IP. This would, for example, prevent any VSYNCs from happening, and
would thus affect the users of omapdss. By using LDOON when the cable is
disconnected we'll avoid the HW bug, but keep the HDMI working as usual
from the user's point of view.Signed-off-by: Tomi Valkeinen
Signed-off-by: Greg Kroah-Hartman -
commit aa74274b464d4aa24703963ac89a0ee942d5d267 upstream.
Both Panda and 4430SDP use GPIO 63 as HDMI hot-plug-detect. Configure
this GPIO in the board files.Signed-off-by: Tomi Valkeinen
Acked-by: Tony Lindgren
Signed-off-by: Greg Kroah-Hartman -
commit 78a1ad8f12db70b8b0a4548b90704de08ee216ce upstream.
The HDMI GPIO pins LS_OE and CT_CP_HPD are not currently configured.
This patch configures them as output pins.Signed-off-by: Tomi Valkeinen
Acked-by: Tony Lindgren
Signed-off-by: Greg Kroah-Hartman -
commit 7bb122d155f742fe2d79849090c825be7b4a247e upstream.
"hdmi_hpd" pin is muxed to INPUT and PULLUP, but the pin is not
currently used, and in the future when it is used, the pin is used as a
GPIO and is board specific, not an OMAP4 wide thing.So remove the muxing for now.
Signed-off-by: Tomi Valkeinen
Acked-by: Tony Lindgren
Signed-off-by: Greg Kroah-Hartman -
commit 3932a32fcf5393f8be70ac99dc718ad7ad0a415b upstream.
The GPIO 60 on 4430sdp and Panda is not HPD GPIO, as currently marked in
the board files, but CT_CP_HPD, which is used to enable/disable HPD
functionality.This patch renames the GPIO.
Signed-off-by: Tomi Valkeinen
Acked-by: Tony Lindgren
Signed-off-by: Greg Kroah-Hartman -
commit 575753e3bea3b67eef8e454fb87f719e3f7da599 upstream.
Instead of freeing the GPIOs individually, use gpio_free_array().
Signed-off-by: Tomi Valkeinen
Acked-by: Tony Lindgren
Signed-off-by: Greg Kroah-Hartman -
commit b06540371063f0f07aafc1d1ac5e974da85c973c upstream.
Patchset "ARM: orion: Refactor the MPP code common in the orion
platform" broke at least Orion5x based platforms. These platforms have
pins configured as GPIO when the selector is not 0x0. However the
common code assumes the selector is always 0x0 for a GPIO lines. It
then ignores the GPIO bits in the MPP definitions, resulting in that
Orion5x machines cannot correctly configure there GPIO lines.The Fix removes the assumption that the selector is always 0x0.
In order that none GPIO configurations are correctly blocked,
Kirkwood and mv78xx0 MPP definitions are corrected to only set the
GPIO bits for GPIO configurations.This third version, which does not contain any whitespace changes,
and is rebased on v3.3-rc2.Signed-off-by: Andrew Lunn
Acked-by: Nicolas Pitre
Signed-off-by: Olof Johansson -
commit 72053353583230952c4b187e110e9da00dfc3afb upstream.
The patch "ARM: orion: Consolidate USB platform setup code.", commit
4fcd3f374a928081d391cd9a570afe3b2c692fdc broke USB on TS-7800 and
other orion5x boards, because the wrong type of PHY was being passed
to the EHCI driver in the platform data. Orion5x needs EHCI_PHY_ORION
and all the others want EHCI_PHY_NA.Allow the mach- code to tell the generic plat-orion code which USB PHY
enum to place into the platform data.Version 2: Rebase to v3.3-rc2.
Reported-by: Ambroz Bizjak
Signed-off-by: Andrew Lunn
Tested-by: Ambroz Bizjak
Acked-by: Nicolas Pitre
Signed-off-by: Olof Johansson
Signed-off-by: Greg Kroah-Hartman -
commit b3f33cbf7ace8fc149993ee35e0d0fd57f41d6d8 upstream.
SandyBridge should be using the same register addresses as IvyBridge.
Signed-off-by: Wu Fengguang
Signed-off-by: Keith Packard
Signed-off-by: Eugeni Dodonov
Signed-off-by: Greg Kroah-Hartman -
commit d71de14ddf423ccc9a2e3f7e37553c99ead20d7c upstream.
The BSpec Workarounds page states that bits 10 and 26 must be set to
avoid 3D ring hangs.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41353
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44610
Tested-by: Eugeni Dodonov
Signed-off-by: Kenneth Graunke
Signed-off-by: Jesse Barnes
Signed-off-by: Greg Kroah-Hartman -
commit db099c8f963fe656108e0a068274c5580a17f69b upstream.
This adds the workaround for WaCatErrorRejectionIssue which could result
in a system hang.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41353
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44610
Tested-by: Eugeni Dodonov
Reviewed-by: Kenneth Graunke
Signed-off-by: Eugeni Dodonov
Signed-off-by: Jesse Barnes
Signed-off-by: Greg Kroah-Hartman -
commit e4e0c058a19c41150d12ad2d3023b3cf09c5de67 upstream.
This adds two cache-related workarounds for Ivy Bridge which can lead to
3D ring hangs and corruptions.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41353
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44610
Tested-by: Eugeni Dodonov
Signed-off-by: Eugeni Dodonov
Signed-off-by: Kenneth Graunke
Signed-off-by: Jesse Barnes
Signed-off-by: Greg Kroah-Hartman -
commit eae66b50c760233fad526edf4a0d327be17a055d upstream.
This is yet another workaround related to clock gating which we need on
Ivy Bridge.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41353
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44610
Tested-by: Eugeni Dodonov
Signed-off-by: Eugeni Dodonov
Signed-off-by: Kenneth Graunke
Signed-off-by: Jesse Barnes
Signed-off-by: Greg Kroah-Hartman -
commit 6cddafab54e9a17b2efefe982547865955a5ff3a upstream.
The latest vendor (non-mac80211) driver of 9/22/2011 shows some new
device IDs for rtl8192cu. In addition, some typos in the table are
fixed and one duplicate is removed.Signed-off-by: Larry Finger
Signed-off-by: John W. Linville
Signed-off-by: Greg Kroah-Hartman -
commit 5a50a7c32d630d6cdb13d69afabb0cc81b2f379c upstream.
The models do not resume correctly without acpi_sleep=nonvs.
Signed-off-by: Keng-Yu Lin
Signed-off-by: Rafael J. Wysocki
Cc: Tim Gardner
Signed-off-by: Greg Kroah-Hartman -
commit 31e0017e6f6fb5cfdfaf932c1f98c9bef8d57688 upstream.
Enable use of the generic atomic64 implementation on AVR32 platforms.
Without this the kernel fails to build as the architecture does not
provide its version.Signed-off-by: Fabio Baltieri
Acked-by: Hans-Christian Egtvedt
Cc: Haavard Skinnemoen
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
Cc: Jean-Christophe PLAGNIOL-VILLARD
Signed-off-by: Greg Kroah-Hartman -
commit 37b40adf2d1b4a5e51323be73ccf8ddcf3f15dd3 upstream.
We create "bsg" link if q->kobj.sd is not NULL, so remove it only
when the same condition is true.Fixes:
WARNING: at fs/sysfs/inode.c:323 sysfs_hash_and_remove+0x2b/0x77()
sysfs: can not remove 'bsg', no directory
Call Trace:
[] warn_slowpath_common+0x6a/0x7f
[] ? sysfs_hash_and_remove+0x2b/0x77
[] warn_slowpath_fmt+0x2b/0x2f
[] sysfs_hash_and_remove+0x2b/0x77
[] sysfs_remove_link+0x20/0x23
[] bsg_unregister_queue+0x40/0x6d
[] __scsi_remove_device+0x31/0x9d
[] scsi_forget_host+0x41/0x52
[] scsi_remove_host+0x71/0xe0
[] quiesce_and_remove_host+0x51/0x83 [usb_storage]
[] usb_stor_disconnect+0x18/0x22 [usb_storage]
[] usb_unbind_interface+0x4e/0x109
[] __device_release_driver+0x6b/0xa6
[] device_release_driver+0x17/0x22
[] bus_remove_device+0xd6/0xe6
[] device_del+0xf2/0x137
[] usb_disable_device+0x94/0x1a0Signed-off-by: Stanislaw Gruszka
Signed-off-by: Jens Axboe
Signed-off-by: Tim Gardner
Signed-off-by: Greg Kroah-Hartman -
commit 5ed80a75b248bfaf840ea6b38f941edcf6ee7dc7 upstream.
According to i.MX27 Reference Manual (p 1593) TXBIT0 bit selects
whether the most significant or the less significant part of the
data word written to the FIFO is transmitted.As DSP_A is the same as DSP_B with a data offset of 1 bit, it
doesn't make any sense to remove TXBIT0 bit here.Signed-off-by: Javier Martin
Acked-by: Sascha Hauer
Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman -
commit 7679e42ec833ed70aa34790a5f39dcb7e5bda4fe upstream.
Recent enhancements in the bias management means that we might not be
in standby when the CODEC is idle and can have active widgets without
being in full power mode but the shutdown functionality assumes these
things. Add checks for the bias level at each stage so that we don't
do transitions other than the ON->PREPARE->STANDBY->OFF ones that the
drivers are expecting.Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman -
commit e29206381a1436e0f47c0f5b9a23159a03c57715 upstream.
Even if the documentation calls this bit "Reserved" it has to be set
to 0 for correct modesetting on IGA1.Signed-off-by: Florian Tobias Schandinat
Signed-off-by: Greg Kroah-Hartman -
commit 050f0e02c8dc38b2b4f2df345ac760d22ca5c7ba upstream.
VX900 can do hardware scaling for both IGAs in contrast to previous
hardware which could do it only for IGA2. This patch ensures that
we set the parameter for IGA2 and not for IGA1. This fixes hardware
scaling on VX900 until we have the infrastructure to support it for
both IGAs.Signed-off-by: Florian Tobias Schandinat
Signed-off-by: Greg Kroah-Hartman -
commit 41f8ad76362e7aefe3a03949c43e23102dae6e0b upstream.
It used to be that minors where 8 bit. But now they
are actually 20 bit. So the fix is simplicity itself.I've tested with 300 devices and all user-mode utils
work just fine. I have also mechanically added 10,000
to the ida (so devices are /dev/osd10000, /dev/osd10001 ...)
and was able to mkfs an exofs filesystem and access osds
from user-mode.All the open-osd user-mode code uses the same library
to access devices through their symbolic names in
/dev/osdX so I'd say it's pretty safe. (Well tested)This patch is very important because some of the systems
that will be deploying the 3.2 pnfs-objects code are larger
than 64 OSDs and will stop to work properly when reaching
that number.Signed-off-by: Boaz Harrosh
Signed-off-by: James Bottomley
Signed-off-by: Greg Kroah-Hartman -
commit f8f54e190ddb4ed697036b60f5e2ae6dd45b801c upstream.
Broken by commit 6ef84509f3d439ed2d43ea40080643efec37f54f for users
passing a request with non-zero 'nbytes' field, like e.g. testmgr.Signed-off-by: Phil Sutter
Signed-off-by: Herbert Xu
Signed-off-by: Greg Kroah-Hartman -
commit 37891abc8464637964a26ae4b61d307fef831f80 upstream.
This patch (as1531) adds a NOGET quirk for the Slim+ keyboard marketed
by AIREN. This keyboard seems to have a lot of bugs; NOGET works
around only one of them.Signed-off-by: Alan Stern
Reported-by: okias
Signed-off-by: Jiri Kosina
Signed-off-by: Greg Kroah-Hartman -
commit b24823e61bfd93d0e72088e4f5245287582ed289 upstream.
Fix a bug that causes a kernel panic when the number of received doorbells
is larger than number of entries in the inbound doorbell queue (current
default value = 512).Another possible indication for this bug is large number of spurious
doorbells reported by tsi721 driver after reaching the queue size maximum.Signed-off-by: Alexandre Bounine
Cc: Chul Kim
Cc: Matt Porter
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
Signed-off-by: Greg Kroah-Hartman -
commit 7b3cc67d4445995a025a4b55a7dc687b6829b4ca upstream.
Git commit 25f269f17316549e "[S390] qdio: EQBS retry after CCQ 96"
introduced a regression in regard to the zfcp data router.
Revoke the incorrect simplification of the function call arguments
for the qdio handler to make the zfcp hardware data router working
again.This is applicable to 3.2+ kernels.
Signed-off-by: Steffen Maier
Reviewed-by: Jan Glauber
Signed-off-by: Martin Schwidefsky
Signed-off-by: Greg Kroah-Hartman