exynos: Fix the name of the chip_operations structures.
The exynos directories had been moved from src/cpu to src/soc, but the name of the chip_operations structure wasn't updated properly. That meant that the SOCs never installed their memory resources and the ram stage would fail to load the payload. Change-Id: Ib60489b6d3434e3ebd13827a804452f762747f1b Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://chromium-review.googlesource.com/172400 Reviewed-by: David Hendricks <dhendrix@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org> (cherry picked from commit 9100d475ebcc4dae23184583a6cc0162577e70d1) Signed-off-by: Isaac Christensen <isaac.christensen@se-eng.com> Reviewed-on: http://review.coreboot.org/6781 Tested-by: build bot (Jenkins) Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
This commit is contained in:
parent
f09f2247d7
commit
d81f409514
|
@ -147,8 +147,8 @@ static void enable_exynos5250_dev(device_t dev)
|
|||
dev->ops = &cpu_ops;
|
||||
}
|
||||
|
||||
struct chip_operations cpu_samsung_exynos5250_ops = {
|
||||
CHIP_NAME("CPU Samsung Exynos 5250")
|
||||
struct chip_operations soc_samsung_exynos5250_ops = {
|
||||
CHIP_NAME("SOC Samsung Exynos 5250")
|
||||
.enable_dev = enable_exynos5250_dev,
|
||||
};
|
||||
|
||||
|
|
|
@ -177,7 +177,7 @@ static void enable_exynos5420_dev(device_t dev)
|
|||
dev->ops = &cpu_ops;
|
||||
}
|
||||
|
||||
struct chip_operations cpu_samsung_exynos5420_ops = {
|
||||
CHIP_NAME("CPU Samsung Exynos 5420")
|
||||
struct chip_operations soc_samsung_exynos5420_ops = {
|
||||
CHIP_NAME("SOC Samsung Exynos 5420")
|
||||
.enable_dev = enable_exynos5420_dev,
|
||||
};
|
||||
|
|
Loading…
Reference in New Issue