linux-toradex.git, branch v3.2.5

Linux 3.2.5

2012-02-06T17:47:00+00:00

PCI: Rework ASPM disable code

2012-02-06T17:41:06+00:00

commit 3c076351c4027a56d5005a39a0b518a4ba393ce2 upstream.

Right now we forcibly clear ASPM state on all devices if the BIOS indicates
that the feature isn't supported. Based on the Microsoft presentation
"PCI Express In Depth for Windows Vista and Beyond", I'm starting to think
that this may be an error. The implication is that unless the platform
grants full control via _OSC, Windows will not touch any PCIe features -
including ASPM. In that case clearing ASPM state would be an error unless
the platform has granted us that control.

This patch reworks the ASPM disabling code such that the actual clearing
of state is triggered by a successful handoff of PCIe control to the OS.
The general ASPM code undergoes some changes in order to ensure that the
ability to clear the bits isn't overridden by ASPM having already been
disabled. Further, this theoretically now allows for situations where
only a subset of PCIe roots hand over control, leaving the others in the
BIOS state.

It's difficult to know for sure that this is the right thing to do -
there's zero public documentation on the interaction between all of these
components. But enough vendors enable ASPM on platforms and then set this
bit that it seems likely that they're expecting the OS to leave them alone.

Measured to save around 5W on an idle Thinkpad X220.

Signed-off-by: Matthew Garrett 
Signed-off-by: Jesse Barnes 
Signed-off-by: Greg Kroah-Hartman

Linux 3.2.4

2012-02-03T20:39:51+00:00

Revert "ASoC: Don't go through cache when applying WM5100 rev A updates"

2012-02-03T20:27:49+00:00

This reverts commit 78fd75340768980ce6ca646106762a6928289e0c (upstream
commit 495174a8ffbaa0d15153d855cf206cdc46d51cf4) as it breaks the build.

Reported-by: Tim Gardner 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

Revert "ASoC: Mark WM5100 register map cache only when going into BIAS_OFF"

2012-02-03T20:26:40+00:00

This reverts commit 11a17e56ac9c607c6eaecf64b618cd17c828ade0
(e53e417331c57b9b97e3f8be870214a02c99265c upstream) as it breaks the
build.

Reported-by: Tim Gardner 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

Linux 3.2.3

2012-02-03T17:23:33+00:00

mach-ux500: no MMC_CAP_SD_HIGHSPEED on Snowball

2012-02-03T17:22:27+00:00

commit 2ab1159e80e8f416071e9f51e4f77b9173948296 upstream.

MMC_CAP_SD_HIGHSPEED is not supported on Snowball board resulting on
initialization errors.

Signed-off-by: Mathieu Poirier 
Signed-off-by: Fredrik Soderstedt 
Signed-off-by: Philippe Langlais 
Signed-off-by: Linus Walleij

USB: cp210x: allow more baud rates above 1Mbaud

2012-02-03T17:22:27+00:00

commit d1620ca9e7bb0030068c3b45b653defde8839dac upstream.

Allow more baud rates to be set in [1M,2M] baud.

Signed-off-by: Johan Hovold 
Cc: Preston Fick 
Signed-off-by: Greg Kroah-Hartman

USB: cp210x: initialise baud rate at open

2012-02-03T17:22:26+00:00

commit cdc32fd6f7b2b2580d7f1b74563f888e4dd9eb8a upstream.

The newer cp2104 devices require the baud rate to be initialised after
power on. Make sure it is set when port is opened.

Signed-off-by: Johan Hovold 
Cc: Preston Fick 
Signed-off-by: Greg Kroah-Hartman

USB: cp210x: clean up, refactor and document speed handling

2012-02-03T17:22:25+00:00

commit e5990874e511d5bbca23b3396419480cb2ca0ee7 upstream.

Clean up and refactor speed handling.
Document baud rate handling for CP210{1,2,4,5,10}.

Signed-off-by: Johan Hovold 
Cc: Preston Fick 
Signed-off-by: Greg Kroah-Hartman