devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Alexander Graf <agraf@suse.de>, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] ZynqMP: Align gic ranges for 64k in device tree
Date: Mon, 16 May 2016 09:17:32 +0200	[thread overview]
Message-ID: <5739740C.10901@xilinx.com> (raw)
In-Reply-To: <1463053441-57572-1-git-send-email-agraf@suse.de>

On 12.5.2016 13:44, Alexander Graf wrote:
> The GIC ranges in the zynqmp device tree are only 4kb aligned. Since
> commit 12e14066f we automatically deal with aliases GIC regions though,
> so we can map them transparently into guests even on 64kb page size
> systems.
> 
> This patch makes use of that features and sets GICC and GICV to 64kb
> aligned and sized regions.
> 
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
>  arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> index e595f22..38c4310 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> @@ -81,9 +81,9 @@
>  			compatible = "arm,gic-400", "arm,cortex-a15-gic";
>  			#interrupt-cells = <3>;
>  			reg = <0x0 0xf9010000 0x10000>,
> -			      <0x0 0xf902f000 0x2000>,
> +			      <0x0 0xf9020000 0x20000>,
>  			      <0x0 0xf9040000 0x20000>,
> -			      <0x0 0xf906f000 0x2000>;
> +			      <0x0 0xf9060000 0x20000>;
>  			interrupt-controller;
>  			interrupt-parent = <&gic>;
>  			interrupts = <1 9 0xf04>;
> 

Applied to zynqmp/dt with changed subject prefix ARM64: zynqmp:

Thanks,
Michal

      reply	other threads:[~2016-05-16  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 11:44 [PATCH] ZynqMP: Align gic ranges for 64k in device tree Alexander Graf
2016-05-16  7:17 ` Michal Simek [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=5739740C.10901@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=agraf@suse.de \
    --cc=devicetree@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).