From: Ian Campbell <Ian.Campbell@citrix.com>
To: Frediano Ziglio <frediano.ziglio@huawei.com>
Cc: Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@linaro.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
zoltan.kiss@huawei.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 01/10] xen/arm: Implement hip04-d01 platform
Date: Tue, 13 Jan 2015 11:58:03 +0000 [thread overview]
Message-ID: <1421150283.19103.39.camel@citrix.com> (raw)
In-Reply-To: <1415009522-6344-2-git-send-email-frediano.ziglio@huawei.com>
On Mon, 2014-11-03 at 10:11 +0000, Frediano Ziglio wrote:
> Add this new platform to Xen.
> This platform require specific code to initialize CPUs.
What is the "bootwrapper"? Are you running this on real silicon or on an
emulator? Can the platform be made to do PSCI instead?
> + np_fab = dt_find_compatible_node(NULL, NULL, "hisilicon,hip04-fabric");
Please add a reference to the DT bindings document for these values.
linux/Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt
seems related but doesn't talk about most of these fields.
> + msg = "hisilicon,hip04-fabric missing in DT\n";
> + if ( !np_fab )
> + goto err;
> +
> + msg = "failed to get bootwrapper-phys\n";
> + if ( !dt_property_read_u32(np, "bootwrapper-phys",
> + &hip04_boot.bootwrapper_phys) )
> + goto err;
> +
> + msg = "failed to get bootwrapper-size\n";
> + if ( !dt_property_read_u32(np, "bootwrapper-size",
> + &hip04_boot.bootwrapper_size) )
> + goto err;
> +
> + msg = "failed to get bootwrapper-magic\n";
> + if ( !dt_property_read_u32(np, "bootwrapper-magic",
> + &hip04_boot.bootwrapper_magic) )
> + goto err;
> +
> + msg = "failed to get relocation-entry\n";
> + if ( !dt_property_read_u32(np, "relocation-entry",
> + &hip04_boot.relocation_entry) )
> + goto err;
> +
> + msg = "failed to get relocation-size\n";
> + if ( !dt_property_read_u32(np, "relocation-size",
> + &hip04_boot.relocation_size) )
> + goto err;
next prev parent reply other threads:[~2015-01-13 11:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 10:11 xen/arm: Add support for Huawei hip04-d01 platform Frediano Ziglio
2014-11-03 10:11 ` [PATCH 01/10] xen/arm: Implement " Frediano Ziglio
2014-11-03 13:39 ` Julien Grall
2015-01-13 11:58 ` Ian Campbell [this message]
2015-01-13 14:09 ` Frediano Ziglio
2015-01-13 14:42 ` Ian Campbell
2015-01-13 15:11 ` Frediano Ziglio
2015-01-13 15:23 ` Ian Campbell
2015-01-13 15:48 ` Frediano Ziglio
2015-02-19 14:23 ` Frediano Ziglio
2015-02-19 16:19 ` Ian Campbell
2014-11-03 10:11 ` [PATCH 02/10] xen/arm: Implement hip04-d01 board reboot Frediano Ziglio
2014-11-03 13:40 ` Julien Grall
2014-11-03 10:11 ` [PATCH 03/10] xen/arm: Define quirk for Hip04 GICv2 divergence Frediano Ziglio
2014-11-03 13:50 ` Julien Grall
2014-11-03 13:54 ` Ian Campbell
2014-11-03 10:11 ` [PATCH 04/10] xen/arm: Make gic-v2 code handle hip04-d01 platform Frediano Ziglio
2014-11-03 14:10 ` Julien Grall
2015-01-13 11:54 ` Ian Campbell
2015-01-13 13:36 ` Frediano Ziglio
2014-11-03 10:11 ` [PATCH 05/10] xen/arm: Add support for DTBs with strange names of Hip04 GICv2 Frediano Ziglio
2014-11-03 10:11 ` [PATCH 06/10] xen/arm: handle GICH register changes for hip04-d01 platform Frediano Ziglio
2014-11-03 14:12 ` Julien Grall
2014-11-03 10:11 ` [PATCH 07/10] xen/arm: Force domains to use normal GICv2 driver on Hip04 platform Frediano Ziglio
2014-11-03 14:16 ` Julien Grall
2015-01-13 11:54 ` Ian Campbell
2014-11-03 10:12 ` [PATCH 08/10] xen/arm: Move vGIC registers " Frediano Ziglio
2014-11-03 10:12 ` [PATCH 09/10] xen/device_tree: Add new helper to read arrays from a DTB Frediano Ziglio
2014-11-03 14:14 ` Julien Grall
2014-11-03 14:15 ` Julien Grall
2014-11-03 10:12 ` [PATCH 10/10] xen/arm: Handle different bootwrapper locations for Hip04 platform Frediano Ziglio
2014-11-03 14:13 ` Julien Grall
2014-11-03 15:28 ` Frediano Ziglio
2014-11-03 15:33 ` Julien Grall
2014-11-03 15:36 ` Frediano Ziglio
2014-11-03 15:40 ` Julien Grall
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=1421150283.19103.39.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=frediano.ziglio@huawei.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.