From: Bin Meng <bmeng.cn@gmail.com>
Date: Tue, 2 Feb 2016 13:58:02 +0000 (-0800)
Subject: x86: quark: Use Quark's own PCI config APIs
X-Git-Tag: v2016.03-rc2~101
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=5a257df702e5702f46fca548d0899c65e90df947;p=oweals%2Fu-boot.git

x86: quark: Use Quark's own PCI config APIs

There are still two places in Quark's MRC codes that use the generic
legacy PCI APIs, but as we are phasing out these legacy APIs, switch
to use Quark's own PCI config routines.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
---

diff --git a/arch/x86/cpu/quark/mrc_util.c b/arch/x86/cpu/quark/mrc_util.c
index 49d803d794..fac2d72e0d 100644
--- a/arch/x86/cpu/quark/mrc_util.c
+++ b/arch/x86/cpu/quark/mrc_util.c
@@ -12,6 +12,7 @@
 #include <asm/arch/device.h>
 #include <asm/arch/mrc.h>
 #include <asm/arch/msg_port.h>
+#include <asm/arch/quark.h>
 #include "mrc_util.h"
 #include "hte.h"
 #include "smc.h"
@@ -106,8 +107,8 @@ void select_hte(void)
  */
 void dram_init_command(uint32_t data)
 {
-	pci_write_config_dword(QUARK_HOST_BRIDGE, MSG_DATA_REG, data);
-	pci_write_config_dword(QUARK_HOST_BRIDGE, MSG_CTRL_EXT_REG, 0);
+	qrk_pci_write_config_dword(QUARK_HOST_BRIDGE, MSG_DATA_REG, data);
+	qrk_pci_write_config_dword(QUARK_HOST_BRIDGE, MSG_CTRL_EXT_REG, 0);
 	msg_port_setup(MSG_OP_DRAM_INIT, MEM_CTLR, 0);
 
 	DPF(D_REGWR, "WR32 %03X %08X %08X\n", MEM_CTLR, 0, data);