6f18ce8026
Add snapshot of device tree bindings from keystone common kernel, branch
"android-mainline-keystone-qcom-release" at c4c12103f9c0 ("Snap for 9228065
from e32903b9a63bb558df8b803b076619c53c16baad to
android-mainline-keystone-qcom-release").
Change-Id: I7682079615cbd9f29340a5c1f2a1d84ec441a1f1
Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
55 lines
1.4 KiB
YAML
55 lines
1.4 KiB
YAML
# SPDX-License-Identifier: GPL-2.0
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/firmware/qemu,fw-cfg-mmio.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: QEMU Firmware Configuration bindings
|
|
|
|
maintainers:
|
|
- Rob Herring <robh@kernel.org>
|
|
|
|
description: |
|
|
Various QEMU 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 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.
|
|
|
|
|
|
properties:
|
|
compatible:
|
|
const: qemu,fw-cfg-mmio
|
|
|
|
reg:
|
|
maxItems: 1
|
|
description: |
|
|
* 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.
|
|
|
|
dma-coherent: true
|
|
|
|
required:
|
|
- compatible
|
|
- reg
|
|
|
|
additionalProperties: false
|
|
|
|
examples:
|
|
- |
|
|
|
|
fw-cfg@9020000 {
|
|
compatible = "qemu,fw-cfg-mmio";
|
|
reg = <0x9020000 0xa>;
|
|
};
|
|
...
|