From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/10] x86: ivybridge: Add Intel FSP support
Date: Fri, 11 Dec 2015 02:55:43 -0800 [thread overview]
Message-ID: <1449831353-933-1-git-send-email-bmeng.cn@gmail.com> (raw)
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.
Bin Meng (10):
fdtdec: Add compatible string for Intel IvyBridge FSP
x86: ivybridge: Add FSP support
tools: microcode-tool: Support parsing header file with a license
block
x86: ivybridge: Add microcode blobs for all the steppings
superio: Add SMSC SIO1007 driver
x86: ivybridge: Do not require HAVE_INTEL_ME
x86: fsp: Make sure HOB list is not overwritten by U-Boot
x86: fsp: Always use hex numbers in the hob command output
x86: ivybridge: Add macros for LPC decode ranges
x86: Add Intel Cougar Canyon 2 board
arch/x86/cpu/ivybridge/Kconfig | 9 +-
arch/x86/cpu/ivybridge/Makefile | 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 | 96 +++
arch/x86/dts/microcode/m12306a2_00000008.dtsi | 554 +++++++++++++++++
arch/x86/dts/microcode/m12306a4_00000007.dtsi | 618 +++++++++++++++++++
arch/x86/dts/microcode/m12306a5_00000007.dtsi | 618 +++++++++++++++++++
arch/x86/dts/microcode/m12306a8_00000010.dtsi | 682 +++++++++++++++++++++
.../include/asm/arch-ivybridge/fsp/fsp_configs.h | 40 ++
arch/x86/include/asm/arch-ivybridge/fsp/fsp_vpd.h | 12 +
arch/x86/include/asm/arch-ivybridge/pch.h | 10 +
arch/x86/lib/fsp/cmd_fsp.c | 4 +-
arch/x86/lib/fsp/fsp_support.c | 27 +
board/google/chromebook_link/Kconfig | 1 +
board/google/chromebox_panther/Kconfig | 1 +
board/intel/Kconfig | 9 +
board/intel/cougarcanyon2/Kconfig | 25 +
board/intel/cougarcanyon2/MAINTAINERS | 6 +
board/intel/cougarcanyon2/Makefile | 7 +
board/intel/cougarcanyon2/cougarcanyon2.c | 48 ++
board/intel/cougarcanyon2/start.S | 9 +
configs/cougarcanyon2_defconfig | 21 +
drivers/misc/Makefile | 1 +
drivers/misc/smsc_sio1007.c | 126 ++++
include/configs/cougarcanyon2.h | 34 +
include/fdtdec.h | 1 +
include/smsc_sio1007.h | 115 ++++
lib/fdtdec.c | 1 +
tools/microcode-tool.py | 14 +
31 files changed, 3158 insertions(+), 3 deletions(-)
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/dts/microcode/m12306a2_00000008.dtsi
create mode 100644 arch/x86/dts/microcode/m12306a4_00000007.dtsi
create mode 100644 arch/x86/dts/microcode/m12306a5_00000007.dtsi
create mode 100644 arch/x86/dts/microcode/m12306a8_00000010.dtsi
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
--
1.8.2.1
next reply other threads:[~2015-12-11 10:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 10:55 Bin Meng [this message]
2015-12-11 10:55 ` [U-Boot] [PATCH 01/10] fdtdec: Add compatible string for Intel IvyBridge FSP Bin Meng
2015-12-19 2:51 ` Simon Glass
2015-12-21 2:33 ` Bin Meng
2016-02-06 4:29 ` Bin Meng
2016-02-19 20:56 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 02/10] x86: ivybridge: Add FSP support Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 2:27 ` Bin Meng
2015-12-23 16:44 ` Simon Glass
2015-12-23 22:48 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 03/10] tools: microcode-tool: Support parsing header file with a license block Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 04/10] x86: ivybridge: Add microcode blobs for all the steppings Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 05/10] superio: Add SMSC SIO1007 driver Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 2:42 ` Bin Meng
2016-01-06 0:24 ` Simon Glass
2016-01-26 8:29 ` Bin Meng
2016-01-26 17:03 ` Simon Glass
2015-12-11 10:55 ` [U-Boot] [PATCH 06/10] x86: ivybridge: Do not require HAVE_INTEL_ME Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 07/10] x86: fsp: Make sure HOB list is not overwritten by U-Boot Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 2:36 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 08/10] x86: fsp: Always use hex numbers in the hob command output Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 09/10] x86: ivybridge: Add macros for LPC decode ranges Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 7:50 ` Bin Meng
2015-12-11 10:55 ` [U-Boot] [PATCH 10/10] x86: Add Intel Cougar Canyon 2 board Bin Meng
2015-12-19 2:52 ` Simon Glass
2015-12-21 2:34 ` Bin Meng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449831353-933-1-git-send-email-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.