mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-26 14:25:09 +07:00
f2d0b0d5c1
Provide amendments to the MIPS generic platform framework so that
the new generic-based board Ranchu can be chosen to be built.
The Ranchu board is intended to be used by Android emulator. The name
"Ranchu" originates from Android development community. "Goldfish" and
"Ranchu" are terms used for two generations of virtual boards used by
Android emulator. The name "Ranchu" is a newer one among the two, and
this patch deals with Ranchu. However, for historical reasons, some
devices/drivers still contain the name "Goldfish".
MIPS Ranchu machine includes a number of Goldfish devices. The support
for Virtio devices is also included. Ranchu board supports up to 16
Virtio devices which can be attached using Virtio MMIO Bus. This is
summarized in the following picture:
ABUS
||----MIPS CPU
|| | IRQs
||----Goldfish PIC------------(32)--------
|| | | | | | | | | |
||----Goldfish TTY------ | | | | | | | |
|| | | | | | | | |
||----Goldfish RTC-------- | | | | | | |
|| | | | | | | |
||----Goldfish FB----------- | | | | | |
|| | | | | | |
||----Goldfish Events--------- | | | | |
|| | | | | |
||----Goldfish Audio------------ | | | |
|| | | | |
||----Goldfish Battery------------ | | |
|| | | |
||----Android PIPE------------------ | |
|| | |
||----Virtio MMIO Bus | |
|| | | | | |
|| | | (virtio-block)--------- |
|| (16) | |
|| | (virtio-net)------------------
Device Tree is created on the QEMU side based on the information about
devices IO map and IRQ numbers. Kernel will load this DTB using UHI
boot protocol DTB handover mode.
Signed-off-by: Miodrag Dinic <miodrag.dinic@mips.com>
Signed-off-by: Goran Ferenc <goran.ferenc@mips.com>
Signed-off-by: Aleksandar Markovic <aleksandar.markovic@mips.com>
Reviewed-by: James Hogan <jhogan@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/18138/
Signed-off-by: James Hogan <jhogan@kernel.org>
63 lines
2.0 KiB
Plaintext
63 lines
2.0 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
if MIPS_GENERIC
|
|
|
|
config LEGACY_BOARDS
|
|
bool
|
|
help
|
|
Select this from your board if the board must use a legacy, non-UHI,
|
|
boot protocol. This will cause the kernel to scan through the list of
|
|
supported machines calling their detect functions in turn if the
|
|
kernel is booted without being provided with an FDT via the UHI
|
|
boot protocol.
|
|
|
|
config YAMON_DT_SHIM
|
|
bool
|
|
help
|
|
Select this from your board if the board uses the YAMON bootloader
|
|
and you wish to include code which helps translate various
|
|
YAMON-provided environment variables into a device tree properties.
|
|
|
|
comment "Legacy (non-UHI/non-FIT) Boards"
|
|
|
|
config LEGACY_BOARD_SEAD3
|
|
bool "Support MIPS SEAD-3 boards"
|
|
select LEGACY_BOARDS
|
|
select YAMON_DT_SHIM
|
|
help
|
|
Enable this to include support for booting on MIPS SEAD-3 FPGA-based
|
|
development boards, which boot using a legacy boot protocol.
|
|
|
|
comment "FIT/UHI Boards"
|
|
|
|
config FIT_IMAGE_FDT_BOSTON
|
|
bool "Include FDT for MIPS Boston boards"
|
|
help
|
|
Enable this to include the FDT for the MIPS Boston development board
|
|
from Imagination Technologies in the FIT kernel image. You should
|
|
enable this if you wish to boot on a MIPS Boston board, as it is
|
|
expected by the bootloader.
|
|
|
|
config FIT_IMAGE_FDT_NI169445
|
|
bool "Include FDT for NI 169445"
|
|
help
|
|
Enable this to include the FDT for the 169445 platform from
|
|
National Instruments in the FIT kernel image.
|
|
|
|
config FIT_IMAGE_FDT_XILFPGA
|
|
bool "Include FDT for Xilfpga"
|
|
help
|
|
Enable this to include the FDT for the MIPSfpga platform
|
|
from Imagination Technologies in the FIT kernel image.
|
|
|
|
config VIRT_BOARD_RANCHU
|
|
bool "Support Ranchu platform for Android emulator"
|
|
help
|
|
This enables support for the platform used by Android emulator.
|
|
|
|
Ranchu platform consists of a set of virtual devices. This platform
|
|
enables emulation of variety of virtual configurations while using
|
|
Android emulator. Android emulator is based on Qemu, and contains
|
|
the support for the same set of virtual devices.
|
|
|
|
endif
|