From: Mark Rutland <mark.rutland@arm.com>
To: Peng Hao <peng.hao2@zte.com.cn>
Cc: robh+dt@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
andy@infradead.org, dvhart@infradead.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, hutao@cn.fujitsu.com
Subject: Re: [PATCH 4/4] pvpanic: add document for pvpanic-mmio DT
Date: Tue, 23 Oct 2018 11:41:38 +0100 [thread overview]
Message-ID: <20181023104138.5yqjgul7mrpodjhe@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <1540315537-70007-4-git-send-email-peng.hao2@zte.com.cn>
On Wed, Oct 24, 2018 at 01:25:37AM +0800, Peng Hao wrote:
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> ---
> .../devicetree/bindings/arm/pvpanic-mmio.txt | 26 ++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/pvpanic-mmio.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/pvpanic-mmio.txt b/Documentation/devicetree/bindings/arm/pvpanic-mmio.txt
> new file mode 100644
> index 0000000..96c84e15
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/pvpanic-mmio.txt
> @@ -0,0 +1,26 @@
> +* QEMU PVPANIC MMIO Configuration bindings for ARM
> +
> +QEMU's aarch64-softmmu emulation / virtualization targets provide the
> +following PVPANIC MMIO Configuration interface on the "virt" machine
> +type:
> +
> +- a read-write, 16-bit wide data register.
> +
> +QEMU exposes the data register to ARM guests as memory mapped registers.
Please drop references to arm/arm64 in the commit message. I'm sure
other architectures will pick this up, and we only need to describe that
it's an MMIO device that QEMU can provide.
> +
> +Required properties:
> +
> +- compatible: "qemu,pvpanic-mmio".
The reg property should also be described.
Otherwise, this looks good to me.
Thanks,
Mark.
> +
> +Example:
> +
> +/ {
> + #size-cells = <0x2>;
> + #address-cells = <0x2>;
> +
> + pvpanic-mmio@9060000 {
> + compatible = "qemu,pvpanic-mmio";
> + reg = <0x0 0x9060000 0x0 0x2>;
> + };
> +};
> +
> --
> 1.8.3.1
>
prev parent reply other threads:[~2018-10-23 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 17:25 [PATCH 1/4] pvpanic: move pvpanic to misc as common driver Peng Hao
2018-10-23 17:25 ` [PATCH 2/4] pvpanic: add pvpanic support for arm64 Peng Hao
2018-10-23 10:38 ` Mark Rutland
2018-10-23 17:25 ` [PATCH 3/4] pvpanic: add access to pvpanic device information by using FDT Peng Hao
2018-10-23 17:25 ` [PATCH 4/4] pvpanic: add document for pvpanic-mmio DT Peng Hao
2018-10-23 10:41 ` Mark Rutland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181023104138.5yqjgul7mrpodjhe@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hutao@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.hao2@zte.com.cn \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).