summaryrefslogtreecommitdiffstats
path: root/arch/arm/configs/mvebu_defconfig
diff options
context:
space:
mode:
authorGregory CLEMENT <gregory.clement@free-electrons.com>2012-12-04 18:04:59 +0100
committerJason Cooper <jason@lakedaemon.net>2013-01-06 17:41:14 +0000
commitb24212fbfba25102cab7b4b1fd2919a58e02ae31 (patch)
tree397100d27e14ebd59c30d29da93f4e76b1624aa3 /arch/arm/configs/mvebu_defconfig
parentd1c3ed669a2d452cacfb48c2d171a1f364dae2ed (diff)
downloadtalos-obmc-linux-b24212fbfba25102cab7b4b1fd2919a58e02ae31.tar.gz
talos-obmc-linux-b24212fbfba25102cab7b4b1fd2919a58e02ae31.zip
arm: mvebu: Use dw-apb-uart instead of ns16650 as UART driver
The UART controller used in the Armada 370 and Armada XP SoCs is the Synopsys DesignWare 8250 (aka Synopsys DesignWare ABP UART). The improper use of the ns16550 can lead to a kernel oops during boot if a character is sent to the UART before the initialization of the driver. The DW APB has an extra interrupt that gets raised when writing to the LCR when busy. This explains why we need to use dw-apb-uart driver to handle this. Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/configs/mvebu_defconfig')
-rw-r--r--arch/arm/configs/mvebu_defconfig4
1 files changed, 1 insertions, 3 deletions
diff --git a/arch/arm/configs/mvebu_defconfig b/arch/arm/configs/mvebu_defconfig
index a702fb345c01..b5bc96cb65a7 100644
--- a/arch/arm/configs/mvebu_defconfig
+++ b/arch/arm/configs/mvebu_defconfig
@@ -33,9 +33,7 @@ CONFIG_MVNETA=y
CONFIG_MARVELL_PHY=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
-CONFIG_SERIAL_OF_PLATFORM=y
-CONFIG_I2C=y
-CONFIG_I2C_MV64XXX=y
+CONFIG_SERIAL_8250_DW=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_SYSFS=y
# CONFIG_USB_SUPPORT is not set
OpenPOWER on IntegriCloud