threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
39 lines
1.1 KiB
Plaintext
39 lines
1.1 KiB
Plaintext
* QEMU Firmware Configuration bindings for ARM
|
|
|
|
QEMU's arm-softmmu and aarch64-softmmu emulation / virtualization targets
|
|
provide the following Firmware Configuration interface on the "virt" machine
|
|
type:
|
|
|
|
- A write-only, 16-bit wide selector (or control) register,
|
|
- a read-write, 64-bit wide data register.
|
|
|
|
QEMU exposes the control and data register to ARM guests as memory mapped
|
|
registers; their location is communicated to the guest's UEFI firmware in the
|
|
DTB that QEMU places at the bottom of the guest's DRAM.
|
|
|
|
The authoritative guest-side hardware interface documentation to the fw_cfg
|
|
device can be found in "docs/specs/fw_cfg.txt" in the QEMU source tree.
|
|
|
|
|
|
Required properties:
|
|
|
|
- compatible: "qemu,fw-cfg-mmio".
|
|
|
|
- reg: the MMIO region used by the device.
|
|
* Bytes 0x0 to 0x7 cover the data register.
|
|
* Bytes 0x8 to 0x9 cover the selector register.
|
|
* Further registers may be appended to the region in case of future interface
|
|
revisions / feature bits.
|
|
|
|
Example:
|
|
|
|
/ {
|
|
#size-cells = <0x2>;
|
|
#address-cells = <0x2>;
|
|
|
|
fw-cfg@9020000 {
|
|
compatible = "qemu,fw-cfg-mmio";
|
|
reg = <0x0 0x9020000 0x0 0xa>;
|
|
};
|
|
};
|