From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: zynq: Add OCM node
Date: Thu, 12 Feb 2015 10:26:16 +0000 [thread overview]
Message-ID: <20150212102615.GC1245@leverpostej> (raw)
In-Reply-To: <135fba212abd740584a2547903cc8d175417344c.1423736523.git.michal.simek@xilinx.com>
On Thu, Feb 12, 2015 at 10:22:07AM +0000, Michal Simek wrote:
> Add OCM node for all zynq boards. OCM location
> can changed but for all current boards this
> is the location where OCM is.`
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> This patch is done based on discussion here.
> https://lkml.org/lkml/2014/12/1/396
>
> There are some ways how to do it.
> OCM location can be changed but board DTS files
> can easily rewrite it.
> The problem which there is that node has address
> in it but maybe someone can suggest better solution.
Given that the node is so simple, can't this be pushed down into the
board files? So long as the label is consistent anything else that's
referring to it should still work.
Thanks,
Mark.
> ---
> arch/arm/boot/dts/zynq-7000.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi
> index a5cd2eda3edf..d55a8b365a6c 100644
> --- a/arch/arm/boot/dts/zynq-7000.dtsi
> +++ b/arch/arm/boot/dts/zynq-7000.dtsi
> @@ -150,6 +150,11 @@
> reg = <0xf8006000 0x1000>;
> };
>
> + ocm: sram at fffc0000 {
> + compatible = "mmio-sram";
> + reg = <0xfffc0000 0x10000>;
> + };
> +
> uart0: serial at e0000000 {
> compatible = "xlnx,xuartps", "cdns,uart-r1p8";
> status = "disabled";
> --
> 1.8.2.3
>
>
next prev parent reply other threads:[~2015-02-12 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 10:22 [PATCH] ARM: dts: zynq: Add OCM node Michal Simek
2015-02-12 10:26 ` Mark Rutland [this message]
2015-02-12 10:40 ` Michal Simek
2015-02-12 14:31 ` Josh Cartwright
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=20150212102615.GC1245@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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