u-boot.git/arch/x86/cpu, branch v2018.01

ata: Migrate CONFIG_SCSI_AHCI to Kconfig

2017-12-12T23:13:19Z

And use 'imply' liberally. Signed-off-by: Tuomas Tynkkynen

x86: don't compare pointers to 0

2017-11-30T05:50:17Z

x86_vendor_name is defined as static const char *const x86_vendor_name[] So its elements should not be compared to 0. Remove superfluous paranthesis. Problem identified with Coccinelle. Signed-off-by: Heinrich Schuchardt Reviewed-by: Bin Meng

x86: qemu: Move Cache-As-RAM memory from area mapped to ROM

2017-11-30T05:50:17Z

ROM has been made read-only in qemu recently (namely commit 208fa0e4: "pc: make 'pc.rom' readonly when machine has PCI enabled"). So this patch restores compatibility between U-Boot and qemu. Signed-off-by: Anton Gerasimov Reviewed-by: Bin Meng Tested-by: Bin Meng [bmeng: mention qemu commit title in the commit message] Signed-off-by: Bin Meng

x86: braswell: cherryhill: Update dts for SPI lock down

2017-10-27T07:13:47Z

Intel Braswell FSP requires SPI controller settings to be locked down, let's do this in the chrryhill.dts and remove previous Kconfig option. Signed-off-by: Bin Meng Reviewed-by: Simon Glass

env: x86: braswell: Set ENV_IS_IN_SPI_FLASH as default

2017-10-27T07:13:47Z

Imply does not work for a Kconfig choice. Update ENV_IS_IN_SPI_FLASH to be the default one for Intel Braswell. Signed-off-by: Bin Meng Reviewed-by: Simon Glass

x86: braswell: Fix unexpected crash during Linux kernel boot

2017-10-27T07:13:47Z

It was observed that when booting Linux kernel on Intel Cherry Hill board, unexpected crash happens quite randomly. Sometimes kernel just oops, while sometimes kernel throws MCE errors and hangs: mce: [Hardware Error]: Machine check events logged mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: c400000000010151 mce: [Hardware Error]: TSC 0 ADDR 130f3f2c0 mce: [Hardware Error]: PROCESSOR 0:406c3 TIME 1508160686 SOCKET 0 APIC 0 microcode 363 This looks like a hardware error per mcelog. After debugging, it seems turning off turbo mode on the processor does not expose this behavior, although U-Boot runs OK with turbo mode on. Suspect it is related to an errata of Braswell processor. To fix this, remove the Braswell cpu driver which does the turbo mode configuration, and switch to use the generic cpu-x86 driver. Also there is a configuration option in the FSP that turns on the turbo mode and that has been turned off too. Signed-off-by: Bin Meng Reviewed-by: Simon Glass

x86: baytrail: fsp: Move Azalia update codes to board

2017-10-19T03:37:51Z

Azalia configuration may be different across boards, hence it's not appropriate to do that in the SoC level. Instead, let's make the SoC update_fsp_azalia_configs() routine as a weak version, and do the actual work in the board codes. So far it seems only som-db5800-som-6867 board enables the Azalia. Move the original codes into som-db5800-som-6867.c. Signed-off-by: Bin Meng Reviewed-by: Stefan Roese

x86: baytrail: fsp: Use a function to update the Azalia config pointer

2017-10-19T03:37:51Z

At present we directly pass the Azalia config pointer to the FSP UPD. This updates to use a function to do the stuff, like Braswell does. Signed-off-by: Bin Meng Reviewed-by: Stefan Roese

x86: fsp: Consolidate Azalia header file

2017-10-19T03:37:51Z

So far there are two copies of Azalia struct defines with one in baytrail and the other one in braswell. This consolidates these two into one, put it in the common place, and remove the prefix pch_ to these structs to make their names more generic. This also corrects reset_wait_timer from us to ms. Signed-off-by: Bin Meng Reviewed-by: Stefan Roese

x86: baytrail: Fix unstable ACPI S3 resume

2017-10-19T03:37:51Z

It was observed that when booting a Ubuntu 16.04 kernel, doing ACPI S3 suspend/resume sometimes causes the Ubuntu kernel hang forever. The issue is however not reproduced with a kernel built from i386/ x86_64 defconfig configuration. The unstability is actually caused by unexpected interrupts being generated during the S3 resume. For some unknown reason, FSP (gold4) for BayTrail configures the GPIO DFX5 PAD to enable level interrupt (bit 24 and 25). As this pin keeps generating interrupts during an S3 resume, and there is no IRQ requester in the kernel to handle it, the kernel seems to hang and does not continue resuming. Clear the mysterious interrupt bits for this pin. Reported-by: Stefan Roese Signed-off-by: Bin Meng Tested-by: Stefan Roese Reviewed-by: Stefan Roese