aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-orion5x/ts78xx-setup.c
diff options
context:
space:
mode:
authorNicolas Pitre <nico@fluxnic.net>2010-10-21 15:48:33 -0400
committerNicolas Pitre <nico@fluxnic.net>2010-10-21 15:52:03 -0400
commit3924996bab2845bdf9a9d16ff7c20445de1ab55d (patch)
tree8d70c64909df1a8d29f7405eea63ccf4adf5385d /arch/arm/mach-orion5x/ts78xx-setup.c
parentd3491820e8a65c4a51c8e2a165c6a13f864101ba (diff)
downloadkernel_samsung_smdk4412-3924996bab2845bdf9a9d16ff7c20445de1ab55d.zip
kernel_samsung_smdk4412-3924996bab2845bdf9a9d16ff7c20445de1ab55d.tar.gz
kernel_samsung_smdk4412-3924996bab2845bdf9a9d16ff7c20445de1ab55d.tar.bz2
[ARM] Kirkwood: restrict the scope of the PCIe reset workaround
Commit 21f0ba90a447 "orion/kirkwood: reset PCIe unit on boot" made the reset of the PCIe unit unconditional. While this may fix problems on some targets, this also causes problems on other targets. Saeed Bishara <saeed@marvell.com> said about the original problem: "We couln't pinpoint the root cause of this issue, actually we failed to reproduce that issue." So let's restrict the reset of the PCIe unit only to the target where the original problem was observed. Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Diffstat (limited to 'arch/arm/mach-orion5x/ts78xx-setup.c')
0 files changed, 0 insertions, 0 deletions