aboutsummaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2011-11-17 16:41:45 -0500
committerGreg Kroah-Hartman <gregkh@suse.de>2012-01-12 11:35:38 -0800
commit06752b6cc142845a2c21196fa86a0cba7d72d325 (patch)
treedadc785fc2094aea358fdaabd2f629c13518e3bf /net
parent9f3657ac7841b871c5d2dc8ab51fb08080ae67b1 (diff)
downloadkernel_samsung_crespo-06752b6cc142845a2c21196fa86a0cba7d72d325.zip
kernel_samsung_crespo-06752b6cc142845a2c21196fa86a0cba7d72d325.tar.gz
kernel_samsung_crespo-06752b6cc142845a2c21196fa86a0cba7d72d325.tar.bz2
OHCI: final fix for NVIDIA problems (I hope)
commit c61875977458637226ab093a35d200f2d5789787 upstream. Problems with NVIDIA's OHCI host controllers persist. After looking carefully through the spec, I finally realized that when a controller is reset it then automatically goes into a SUSPEND state in which it is completely quiescent (no DMA and no IRQs) and from which it will not awaken until the system puts it into the OPERATIONAL state. Therefore there's no need to worry about controllers being in the RESET state for extended periods, or remaining in the OPERATIONAL state during system shutdown. The proper action for device initialization is to put the controller into the RESET state (if it's not there already) and then to issue a software reset. Similarly, the proper action for device shutdown is simply to do a software reset. This patch (as1499) implements such an approach. It simplifies initialization and shutdown, and allows the NVIDIA shutdown-quirk code to be removed. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Tested-by: Andre "Osku" Schmidt <andre.osku.schmidt@googlemail.com> Tested-by: Arno Augustin <Arno.Augustin@web.de> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions