Skip to contentSkip to conversation

x86: ivybridge: Add Intel FSP support

PATCH New Bin Meng 1 participant 11 messages Feb 17, 2016 – Feb 21, 2016

Subsystems (2)
lore
Share & tools
lore

Bin Meng

author
#0 lore raw

v3 cover x86: ivybridge: Add Intel FSP support

This series adds Intel FSP support to IvyBridge processor and Panther Point chipset (aka Chief River platform), and is validated on Intel Cougar Canyon 2 board.

This only adds basic features like serial, keyboard, RTC, timer, SPI, GPIO, PCI, SATA, USB. Other features will be enabled in future patch set.

Changes in v3:
- Update README.x86 to include intructions for this board

Changes in v2:
- Drop patches which were already applied
- Rebase on top of u-boot-x86/master
- Change fsp files license from Intel to GPL-2.0+
- Introduce a Kconfig option to wrap these codes
- Change include order - <asm/...> go after the normal includes
- Use PCH uclass driver and change to use dm pci config APIs

Bin Meng (5):
x86: ivybridge: Add FSP support
superio: Add SMSC SIO1007 driver
x86: fsp: Make sure HOB list is not overwritten by U-Boot
x86: ivybridge: bd82x6x: Support FSP enabled configuration
x86: Add Intel Cougar Canyon 2 board

 arch/x86/Kconfig                                   |  10 ++
 arch/x86/cpu/ivybridge/Kconfig                     |  12 ++
 arch/x86/cpu/ivybridge/Makefile                    |   6 +-
 arch/x86/cpu/ivybridge/bd82x6x.c                   |   4 +
 arch/x86/cpu/ivybridge/fsp_configs.c               |  45 ++++++++
 arch/x86/cpu/ivybridge/ivybridge.c                 |  22 ++++
 arch/x86/dts/Makefile                              |   1 +
 arch/x86/dts/cougarcanyon2.dts                     | 104 +++++++++++++++++
 .../include/asm/arch-ivybridge/fsp/fsp_configs.h   |  40 +++++++
 arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h  |  12 ++
 arch/x86/lib/fsp/fsp_support.c                     |  33 ++++++
 board/intel/Kconfig                                |   9 ++
 board/intel/cougarcanyon2/Kconfig                  |  25 ++++
 board/intel/cougarcanyon2/MAINTAINERS              |   6 +
 board/intel/cougarcanyon2/Makefile                 |   7 ++
 board/intel/cougarcanyon2/cougarcanyon2.c          |  58 ++++++++++
 board/intel/cougarcanyon2/start.S                  |   9 ++
 configs/cougarcanyon2_defconfig                    |  20 ++++
 doc/README.x86                                     |  21 ++++
 drivers/misc/Makefile                              |   1 +
 drivers/misc/smsc_sio1007.c                        | 126 +++++++++++++++++++++
 include/configs/cougarcanyon2.h                    |  34 ++++++
 include/smsc_sio1007.h                             | 115 +++++++++++++++++++
 23 files changed, 719 insertions(+), 1 deletion(-)
 create mode 100644 arch/x86/cpu/ivybridge/fsp_configs.c
 create mode 100644 arch/x86/cpu/ivybridge/ivybridge.c
 create mode 100644 arch/x86/dts/cougarcanyon2.dts
 create mode 100644 arch/x86/include/asm/arch-ivybridge/fsp/fsp_configs.h
 create mode 100644 arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h
 create mode 100644 board/intel/cougarcanyon2/Kconfig
 create mode 100644 board/intel/cougarcanyon2/MAINTAINERS
 create mode 100644 board/intel/cougarcanyon2/Makefile
 create mode 100644 board/intel/cougarcanyon2/cougarcanyon2.c
 create mode 100644 board/intel/cougarcanyon2/start.S
 create mode 100644 configs/cougarcanyon2_defconfig
 create mode 100644 drivers/misc/smsc_sio1007.c
 create mode 100644 include/configs/cougarcanyon2.h
 create mode 100644 include/smsc_sio1007.h
Signature · 1 line
1.8.2.1
author
#1 lore raw

PATCH v3 1/5 x86: ivybridge: Add FSP support

IvyBridge FSP package is built with a base address at 0xfff80000, and does not use UPD data region. This adds basic FSP support.

Tested on link (ivybridge non-FSP)

---

Changes in v3: None
Changes in v2:
- Drop patches which were already applied
- Rebase on top of u-boot-x86/master
- Change fsp files license from Intel to GPL-2.0+

 arch/x86/cpu/ivybridge/Kconfig                     |  8 ++++
 arch/x86/cpu/ivybridge/Makefile                    |  4 ++
 arch/x86/cpu/ivybridge/fsp_configs.c               | 45 ++++++++++++++++++++++
 arch/x86/cpu/ivybridge/ivybridge.c                 | 22 +++++++++++
 .../include/asm/arch-ivybridge/fsp/fsp_configs.h   | 40 +++++++++++++++++++
 arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h  | 12 ++++++
 6 files changed, 131 insertions(+)
 create mode 100644 arch/x86/cpu/ivybridge/fsp_configs.c
 create mode 100644 arch/x86/cpu/ivybridge/ivybridge.c
 create mode 100644 arch/x86/include/asm/arch-ivybridge/fsp/fsp_configs.h
 create mode 100644 arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h
arch/x86/cpu/ivybridge/Kconfig +8 -0
index 1768a26..b9f290a 100644
@@ -71,4 +71,12 @@ config ENABLE_VMX
 	  will be unable to support virtualisation, or it will run very
 	  slowly.
 
+config FSP_ADDR
+	hex
+	default 0xfff80000
+
+config FSP_USE_UPD
+	bool
+	default n
+
 endif
arch/x86/cpu/ivybridge/Makefile +4 -0
index 45ef141..d7332ff 100644
@@ -4,6 +4,9 @@
 # SPDX-License-Identifier:	GPL-2.0+
 #
 
+ifdef CONFIG_HAVE_FSP
+obj-y += fsp_configs.o ivybridge.o
+else
 obj-y += bd82x6x.o
 obj-y += car.o
 obj-y += cpu.o
@@ -17,3 +20,4 @@ obj-y += northbridge.o
 obj-y += report_platform.o
 obj-y += sata.o
 obj-y += sdram.o
+endif
arch/x86/cpu/ivybridge/fsp_configs.c new file +45 -0

45 lines not on this page · raw message

arch/x86/cpu/ivybridge/ivybridge.c new file +22 -0
new file mode 100644
index 0000000..c770b53
@@ -0,0 +1,22 @@
+/*
+ * Copyright (C) 2016, Bin Meng <[email protected]>
+ *
+ * SPDX-License-Identifier:	GPL-2.0+
+ */
+
+#include <common.h>
+#include <asm/post.h>
+#include <asm/processor.h>
+
+int arch_cpu_init(void)
+{
+	int ret;
+
+	post_code(POST_CPU_INIT);
+
+	ret = x86_cpu_init_f();
+	if (ret)
+		return ret;
+
+	return 0;
+}
arch/x86/include/asm/arch-ivybridge/fsp/fsp_configs.h new file +40 -0
new file mode 100644
index 0000000..9b0613d
@@ -0,0 +1,40 @@
+/*
+ * Copyright (C) 2016, Bin Meng <[email protected]>
+ *
+ * SPDX-License-Identifier:	GPL-2.0+
+ */
+
+#ifndef __FSP_CONFIGS_H__
+#define __FSP_CONFIGS_H__
+
+struct platform_config {
+	u8 enable_ht;
+	u8 enable_turbo;
+	u8 enable_memory_down;
+	u8 enable_fast_boot;
+};
+
+/*
+ * Dummy structure for now as currently only SPD is verified in U-Boot.
+ *
+ * We can add the missing parameters when adding support on a board with
+ * memory down configuration.
+ */
+struct memory_config {
+	u8 dummy;
+};
+
+struct fsp_config_data {
+	struct fsp_cfg_common common;
+	struct platform_config plat_config;
+	struct memory_config mem_config;
+};
+
+struct fspinit_rtbuf {
+	u32 stack_top;
+	u32 boot_mode;
+	struct platform_config *plat_config;
+	struct memory_config *mem_config;
+};
+
+#endif /* __FSP_CONFIGS_H__ */
arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h new file +12 -0
new file mode 100644
index 0000000..3b255cc
@@ -0,0 +1,12 @@
+/*
+ * Copyright (C) 2016, Bin Meng <[email protected]>
+ *
+ * SPDX-License-Identifier:	GPL-2.0+
+ */
+
+#ifndef __FSP_VPD_H__
+#define __FSP_VPD_H__
+
+/* IvyBridge FSP does not support VPD/UPD */
+
+#endif
Signature · 1 line
1.8.2.1
author
#3 lore raw

PATCH v3 2/5 superio: Add SMSC SIO1007 driver

In reply to Bin Meng

The SMSC SIO1007 superio chipset integrates two ns16550 compatible serial ports for legacy applications, 16 GPIO pins and some other functionalities like power management.

This adds a simple driver to enable serial port and handle GPIO.

---

Changes in v3: None
Changes in v2: None

 drivers/misc/Makefile       |   1 +
 drivers/misc/smsc_sio1007.c | 126 ++++++++++++++++++++++++++++++++++++++++++++
 include/smsc_sio1007.h      | 115 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 242 insertions(+)
 create mode 100644 drivers/misc/smsc_sio1007.c
 create mode 100644 include/smsc_sio1007.h
drivers/misc/Makefile +1 -0
index e1e3c6b..f2b08ab 100644
@@ -32,6 +32,7 @@ ifdef CONFIG_DM_I2C
 obj-$(CONFIG_SANDBOX) += i2c_eeprom_emul.o
 endif
 obj-$(CONFIG_SMSC_LPC47M) += smsc_lpc47m.o
+obj-$(CONFIG_SMSC_SIO1007) += smsc_sio1007.o
 obj-$(CONFIG_STATUS_LED) += status_led.o
 obj-$(CONFIG_SANDBOX) += swap_case.o
 obj-$(CONFIG_SANDBOX) += syscon_sandbox.o
drivers/misc/smsc_sio1007.c new file +126 -0

126 lines not on this page · raw message

include/smsc_sio1007.h new file +115 -0

115 lines not on this page · raw message

Signature · 1 line
1.8.2.1
author
#4 lore raw

PATCH v3 2/5 superio: Add SMSC SIO1007 driver

Quoted 9 lines · Bin Meng

The SMSC SIO1007 superio chipset integrates two ns16550 compatible serial ports for legacy applications, 16 GPIO pins and some other functionalities like power management.

This adds a simple driver to enable serial port and handle GPIO.

---

applied to u-boot-x86/master, thanks!

author
#5 lore raw

PATCH v3 3/5 x86: fsp: Make sure HOB list is not overwritten by U-Boot

In reply to Bin Meng

Intel IvyBridge FSP seems to be buggy that it does not report memory used by FSP itself as reserved in the resource descriptor HOB. The FSP specification does not describe how resource descriptor HOBs are generated by the FSP to describe what memory regions. It looks newer FSPs like Queensbay and BayTrail do not have such issue. This causes U-Boot relocation overwrites the important boot service data which is used by FSP, and the subsequent call to fsp_notify() will fail.

To resolve this, we find out the lowest memory base address allocated by FSP for the boot service data when walking through the HOB list in fsp_get_usable_lowmem_top(). Check whether the memory top address is below the FSP HOB list, and if not, use the lowest memory base address allocated by FSP as the memory top address.

Tested on link (ivybridge non-FSP)

---

Changes in v3: None
Changes in v2:
- Introduce a Kconfig option to wrap these codes

 arch/x86/Kconfig               | 10 ++++++++++
 arch/x86/lib/fsp/fsp_support.c | 33 +++++++++++++++++++++++++++++++++
 2 files changed, 43 insertions(+)
arch/x86/Kconfig +10 -0
index 49e173c..a0bd344 100644
@@ -248,6 +248,16 @@ config FSP_USE_UPD
 	  are still some FSPs that might not even have UPD. For such FSPs,
 	  override this to n in their platform Kconfig files.
 
+config FSP_BROKEN_HOB
+	bool
+	depends on HAVE_FSP
+	help
+	  Indicate some buggy FSPs that does not report memory used by FSP
+	  itself as reserved in the resource descriptor HOB. Select this to
+	  tell U-Boot to do some additional work to ensure U-Boot relocation
+	  do not overwrite the important boot service data which is used by
+	  FSP, otherwise the subsequent call to fsp_notify() will fail.
+
 config ENABLE_MRC_CACHE
 	bool "Enable MRC cache"
 	depends on !EFI && !SYS_COREBOOT
arch/x86/lib/fsp/fsp_support.c +33 -0
index 29fa060..b05dced 100644
@@ -225,6 +225,10 @@ u32 fsp_get_usable_lowmem_top(const void *hob_list)
 	struct hob_res_desc *res_desc;
 	phys_addr_t phys_start;
 	u32 top;
+#ifdef CONFIG_FSP_BROKEN_HOB
+	struct hob_mem_alloc *res_mem;
+	phys_addr_t mem_base = 0;
+#endif
 
 	/* Get the HOB list for processing */
 	hdr = hob_list;
@@ -242,9 +246,38 @@ u32 fsp_get_usable_lowmem_top(const void *hob_list)
 					top += (u32)(res_desc->len);
 			}
 		}
+
+#ifdef CONFIG_FSP_BROKEN_HOB
+		/*
+		 * Find out the lowest memory base address allocated by FSP
+		 * for the boot service data
+		 */
+		if (hdr->type == HOB_TYPE_MEM_ALLOC) {
+			res_mem = (struct hob_mem_alloc *)hdr;
+			if (!mem_base)
+				mem_base = res_mem->mem_base;
+			if (res_mem->mem_base < mem_base)
+				mem_base = res_mem->mem_base;
+		}
+#endif
+
 		hdr = get_next_hob(hdr);
 	}
 
+#ifdef CONFIG_FSP_BROKEN_HOB
+	/*
+	 * Check whether the memory top address is below the FSP HOB list.
+	 * If not, use the lowest memory base address allocated by FSP as
+	 * the memory top address. This is to prevent U-Boot relocation
+	 * overwrites the important boot service data which is used by FSP,
+	 * otherwise the subsequent call to fsp_notify() will fail.
+	 */
+	if (top > (u32)hob_list) {
+		debug("Adjust memory top address due to a buggy FSP\n");
+		top = (u32)mem_base;
+	}
+#endif
+
 	return top;
 }
 
Signature · 1 line
1.8.2.1
author
#6 lore raw

PATCH v3 3/5 x86: fsp: Make sure HOB list is not overwritten by U-Boot

Quoted 14 lines · Bin Meng

Intel IvyBridge FSP seems to be buggy that it does not report memory used by FSP itself as reserved in the resource descriptor HOB. The FSP specification does not describe how resource descriptor HOBs are generated by the FSP to describe what memory regions. It looks newer FSPs like Queensbay and BayTrail do not have such issue. This causes U-Boot relocation overwrites the important boot service data which is used by FSP, and the subsequent call to fsp_notify() will fail.

To resolve this, we find out the lowest memory base address allocated by FSP for the boot service data when walking through the HOB list in fsp_get_usable_lowmem_top(). Check whether the memory top address is below the FSP HOB list, and if not, use the lowest memory base address allocated by FSP as the memory top address.

Quoted 6 lines

Tested on link (ivybridge non-FSP)

---

applied to u-boot-x86/master, thanks!

author
#7 lore raw

PATCH v3 4/5 x86: ivybridge: bd82x6x: Support FSP enabled configuration

In reply to Bin Meng

Wrap initialization codes with #ifndef CONFIG_HAVE_FSP #endif, and enable the build for both FSP and non-FSP configurations.

---

Changes in v3: None
Changes in v2: None

 arch/x86/cpu/ivybridge/Makefile  | 2 +-
 arch/x86/cpu/ivybridge/bd82x6x.c | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)
arch/x86/cpu/ivybridge/Makefile +1 -1
index d7332ff..9203219 100644
@@ -7,7 +7,6 @@
 ifdef CONFIG_HAVE_FSP
 obj-y += fsp_configs.o ivybridge.o
 else
-obj-y += bd82x6x.o
 obj-y += car.o
 obj-y += cpu.o
 obj-y += early_me.o
@@ -21,3 +20,4 @@ obj-y += report_platform.o
 obj-y += sata.o
 obj-y += sdram.o
 endif
+obj-y += bd82x6x.o
arch/x86/cpu/ivybridge/bd82x6x.c +4 -0
index 996707b..9972b0a 100644
@@ -22,6 +22,7 @@
 #define GPIO_BASE	0x48
 #define BIOS_CTRL	0xdc
 
+#ifndef CONFIG_HAVE_FSP
 static int pch_revision_id = -1;
 static int pch_type = -1;
 
@@ -170,6 +171,7 @@ static int bd82x6x_probe(struct udevice *dev)
 
 	return 0;
 }
+#endif /* CONFIG_HAVE_FSP */
 
 static int bd82x6x_pch_get_spi_base(struct udevice *dev, ulong *sbasep)
 {
@@ -247,6 +249,8 @@ U_BOOT_DRIVER(bd82x6x_drv) = {
 	.name		= "bd82x6x",
 	.id		= UCLASS_PCH,
 	.of_match	= bd82x6x_ids,
+#ifndef CONFIG_HAVE_FSP
 	.probe		= bd82x6x_probe,
+#endif
 	.ops		= &bd82x6x_pch_ops,
 };
Signature · 1 line
1.8.2.1
author
#8 lore raw

PATCH v3 4/5 x86: ivybridge: bd82x6x: Support FSP enabled configuration

Quoted 6 lines · Bin Meng

Wrap initialization codes with #ifndef CONFIG_HAVE_FSP #endif, and enable the build for both FSP and non-FSP configurations.

---

applied to u-boot-x86/master, thanks!

author
#9 lore raw

PATCH v3 5/5 x86: Add Intel Cougar Canyon 2 board

In reply to Bin Meng

This adds basic support to Intel Cougar Canyon 2 board, a board based on Chief River platform with an Ivy Bridge processor and a Panther Point chipset.

---

Changes in v3:
- Update README.x86 to include intructions for this board

Changes in v2:
- Change include order - <asm/...> go after the normal includes
- Use PCH uclass driver and change to use dm pci config APIs

 arch/x86/cpu/ivybridge/Kconfig            |   4 ++
 arch/x86/dts/Makefile                     |   1 +
 arch/x86/dts/cougarcanyon2.dts            | 104 ++++++++++++++++++++++++++++++
 board/intel/Kconfig                       |   9 +++
 board/intel/cougarcanyon2/Kconfig         |  25 +++++++
 board/intel/cougarcanyon2/MAINTAINERS     |   6 ++
 board/intel/cougarcanyon2/Makefile        |   7 ++
 board/intel/cougarcanyon2/cougarcanyon2.c |  58 +++++++++++++++++
 board/intel/cougarcanyon2/start.S         |   9 +++
 configs/cougarcanyon2_defconfig           |  20 ++++++
 doc/README.x86                            |  21 ++++++
 include/configs/cougarcanyon2.h           |  34 ++++++++++
 12 files changed, 298 insertions(+)
 create mode 100644 arch/x86/dts/cougarcanyon2.dts
 create mode 100644 board/intel/cougarcanyon2/Kconfig
 create mode 100644 board/intel/cougarcanyon2/MAINTAINERS
 create mode 100644 board/intel/cougarcanyon2/Makefile
 create mode 100644 board/intel/cougarcanyon2/cougarcanyon2.c
 create mode 100644 board/intel/cougarcanyon2/start.S
 create mode 100644 configs/cougarcanyon2_defconfig
 create mode 100644 include/configs/cougarcanyon2.h
arch/x86/cpu/ivybridge/Kconfig +4 -0
index b9f290a..0819347 100644
@@ -79,4 +79,8 @@ config FSP_USE_UPD
 	bool
 	default n
 
+config FSP_BROKEN_HOB
+	bool
+	default y
+
 endif
arch/x86/dts/Makefile +1 -0
index 64e5694..84feb19 100644
@@ -5,6 +5,7 @@
 dtb-y += bayleybay.dtb \
 	chromebook_link.dtb \
 	chromebox_panther.dtb \
+	cougarcanyon2.dtb \
 	crownbay.dtb \
 	efi.dtb \
 	galileo.dtb \
arch/x86/dts/cougarcanyon2.dts new file +104 -0

104 lines not on this page · raw message

board/intel/Kconfig +9 -0
index f7d71c3..4d341aa 100644
@@ -18,6 +18,14 @@ config TARGET_BAYLEYBAY
 	  4GB memory, HDMI/DP/VGA display, HD audio, SATA, USB2, USB3, SD, eMMC,
 	  PCIe and some other sensor interfaces.
 
+config TARGET_COUGARCANYON2
+	bool "Cougar Canyon 2"
+	help
+	  This is the Intel Cougar Canyon 2 Customer Reference Board. It
+	  is built on the Chief River platform with Intel Ivybridge Processor
+	  and Panther Point chipset. The board has 4GB RAM, with some other
+	  peripheral connectors for PCIe/SATA/USB2/USB3/LAN/UART/PS2/VGA/HDMI.
+
 config TARGET_CROWNBAY
 	bool "Crown Bay"
 	help
@@ -54,6 +62,7 @@ config TARGET_MINNOWMAX
 endchoice
 
 source "board/intel/bayleybay/Kconfig"
+source "board/intel/cougarcanyon2/Kconfig"
 source "board/intel/crownbay/Kconfig"
 source "board/intel/galileo/Kconfig"
 source "board/intel/minnowmax/Kconfig"
board/intel/cougarcanyon2/Kconfig new file +25 -0
new file mode 100644
index 0000000..95a617b
@@ -0,0 +1,25 @@
+if TARGET_COUGARCANYON2
+
+config SYS_BOARD
+	default "cougarcanyon2"
+
+config SYS_VENDOR
+	default "intel"
+
+config SYS_SOC
+	default "ivybridge"
+
+config SYS_CONFIG_NAME
+	default "cougarcanyon2"
+
+config SYS_TEXT_BASE
+	default 0xffe00000
+
+config BOARD_SPECIFIC_OPTIONS # dummy
+	def_bool y
+	select X86_RESET_VECTOR
+	select NORTHBRIDGE_INTEL_IVYBRIDGE
+	select HAVE_FSP
+	select BOARD_ROMSIZE_KB_2048
+
+endif
board/intel/cougarcanyon2/MAINTAINERS new file +6 -0
new file mode 100644
index 0000000..a486739
@@ -0,0 +1,6 @@
+INTEL COUGAR CANYON 2 BOARD
+M:	Bin Meng <[email protected]>
+S:	Maintained
+F:	board/intel/cougarcanyon2/
+F:	include/configs/cougarcanyon2.h
+F:	configs/cougarcanyon2_defconfig
board/intel/cougarcanyon2/Makefile new file +7 -0
new file mode 100644
index 0000000..abd924c
@@ -0,0 +1,7 @@
+#
+# Copyright (C) 2016, Bin Meng <[email protected]>
+#
+# SPDX-License-Identifier:	GPL-2.0+
+#
+
+obj-y	+= cougarcanyon2.o start.o
board/intel/cougarcanyon2/cougarcanyon2.c new file +58 -0

58 lines not on this page · raw message

board/intel/cougarcanyon2/start.S new file +9 -0
new file mode 100644
index 0000000..d8f227c
@@ -0,0 +1,9 @@
+/*
+ * Copyright (C) 2016, Bin Meng <[email protected]>
+ *
+ * SPDX-License-Identifier:	GPL-2.0+
+ */
+
+.globl early_board_init
+early_board_init:
+	jmp	early_board_init_ret
configs/cougarcanyon2_defconfig new file +20 -0
new file mode 100644
index 0000000..09306bb
@@ -0,0 +1,20 @@
+CONFIG_X86=y
+CONFIG_VENDOR_INTEL=y
+CONFIG_DEFAULT_DEVICE_TREE="cougarcanyon2"
+CONFIG_TARGET_COUGARCANYON2=y
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+CONFIG_CMD_GPIO=y
+# CONFIG_CMD_SETEXPR is not set
+# CONFIG_CMD_NFS is not set
+CONFIG_OF_CONTROL=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_WINBOND=y
+CONFIG_DM_PCI=y
+CONFIG_DM_RTC=y
+CONFIG_SYS_NS16550=y
+CONFIG_ICH_SPI=y
+CONFIG_TIMER=y
+CONFIG_USB=y
+CONFIG_DM_USB=y
+CONFIG_USE_PRIVATE_LIBGCC=y
doc/README.x86 +21 -0
index 6d9cb10..948deca 100644
@@ -133,6 +133,27 @@ $ make all
 
 ---
 
+Intel Cougar Canyon 2 specific instructions for bare mode:
+
+This uses Intel FSP for 3rd generation Intel Core and Intel Celeron processors
+with mobile Intel HM76 and QM77 chipsets platform. Download it from Intel FSP
+website and put the .fd file (CHIEFRIVER_FSP_GOLD_001_09-OCTOBER-2013.fd at the
+time of writing) in the board directory and rename it to fsp.bin.
+
+Now build U-Boot and obtain u-boot.rom
+
+$ make cougarcanyon2_defconfig
+$ make all
+
+The board has two 8MB SPI flashes mounted, which are called SPI-0 and SPI-1 in
+the board manual. The SPI-0 flash should have flash descriptor plus ME firmware
+and SPI-1 flash is used to store U-Boot. For convenience, the complete 8MB SPI-0
+flash image is included in the FSP package (named Rom00_8M_MB_PPT.bin). Program
+this image to the SPI-0 flash according to the board manual just once and we are
+all set. For programming U-Boot we just need to program SPI-1 flash.
+
+---
+
 Intel Minnowboard Max instructions for bare mode:
 
 This uses as FSP as with Crown Bay, except it is for the Atom E3800 series.
include/configs/cougarcanyon2.h new file +34 -0
new file mode 100644
index 0000000..88845dc
@@ -0,0 +1,34 @@
+/*
+ * Copyright (C) 2016, Bin Meng <[email protected]>
+ *
+ * SPDX-License-Identifier:	GPL-2.0+
+ */
+
+#ifndef __CONFIG_H
+#define __CONFIG_H
+
+#include <configs/x86-common.h>
+
+#define CONFIG_SYS_MONITOR_LEN		(2 << 20)
+#define CONFIG_BOARD_EARLY_INIT_F
+
+#define CONFIG_SMSC_SIO1007
+
+#define CONFIG_PCI_PNP
+
+#define CONFIG_STD_DEVICES_SETTINGS	"stdin=serial,i8042-kbd,usbkbd\0" \
+					"stdout=serial,vga\0" \
+					"stderr=serial,vga\0"
+
+#define CONFIG_SCSI_DEV_LIST		\
+	{PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_PANTHERPOINT_AHCI_MOBILE}
+
+/* Environment configuration */
+#define CONFIG_ENV_SECT_SIZE		0x1000
+#define CONFIG_ENV_OFFSET		0x5ff000
+
+/* Video is not supported for now */
+#undef CONFIG_VIDEO
+#undef CONFIG_CFB_CONSOLE
+
+#endif	/* __CONFIG_H */
Signature · 1 line
1.8.2.1
author
#10 lore raw

PATCH v3 5/5 x86: Add Intel Cougar Canyon 2 board

Quoted 8 lines · Bin Meng

This adds basic support to Intel Cougar Canyon 2 board, a board based on Chief River platform with an Ivy Bridge processor and a Panther Point chipset.

---

applied to u-boot-x86/master, thanks!