From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] PPC: E500: Implement reboot controller
Date: Fri, 3 Jun 2011 12:00:36 -0500 [thread overview]
Message-ID: <20110603120036.3408086a@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <1307015870-22191-1-git-send-email-agraf@suse.de>
On Thu, 2 Jun 2011 13:57:50 +0200
Alexander Graf <agraf@suse.de> wrote:
> diff --git a/pc-bios/mpc8544ds.dts b/pc-bios/mpc8544ds.dts
> index 872152d..9b95bfd 100644
> --- a/pc-bios/mpc8544ds.dts
> +++ b/pc-bios/mpc8544ds.dts
> @@ -82,6 +82,12 @@
> compatible = "chrp,open-pic";
> device_type = "open-pic";
> };
> +
> + global-utilities@e0000 { //global utilities block
> + compatible = "fsl,mpc8548-guts";
> + reg = <0xe0000 0x1000>;
> + fsl,has-rstcr;
> + };
> };
We're not providing a full mpc8548 (or mpc8544) guts, only the rstcr
register.
Currently Linux looks for a node with the name "global-utilities" and a
property "fsl,has-rstcr", so there's no compatibility reason for a
misleading compatible, either.
I'd go with compatible = "fsl,guts-rstcr" (what we've been using
internally, and would be a nicer thing to bind against than what the
kernel currently does). Or if the goal is to provide more guts registers
later, use "fsl,mpc8544-guts" and have qemu log a warning if other accesses
are made.
-Scott
next prev parent reply other threads:[~2011-06-03 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 11:57 [Qemu-devel] [PATCH] PPC: E500: Implement reboot controller Alexander Graf
2011-06-03 17:00 ` Scott Wood [this message]
2011-06-03 17:33 ` Alexander Graf
2011-06-03 17:35 ` Alexander Graf
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=20110603120036.3408086a@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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).