From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] ARM: Tegra: dt: Set up an OF IRQ translation range
Date: Sat, 30 Apr 2011 00:36:41 -0600 [thread overview]
Message-ID: <20110430063641.GC3103@ponder.secretlab.ca> (raw)
In-Reply-To: <1304136608-11584-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Fri, Apr 29, 2011 at 10:10:08PM -0600, Stephen Warren wrote:
> Without this, none of the devicetree devices in tegra-harmony.dts can
> map interrupts, and the system fails to boot.
>
> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Merged into arm/dt: full tegra devicetree support patch, thanks.
g.
> ---
> v2: Add a Tegra-specific compatible value, search by that value, minor
> formatting fixes.
>
> arch/arm/boot/dts/tegra-harmony.dts | 3 +++
> arch/arm/mach-tegra/board-dt.c | 14 ++++++++++++++
> 2 files changed, 17 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/tegra-harmony.dts b/arch/arm/boot/dts/tegra-harmony.dts
> index 82fa0c2..a22c1bb 100644
> --- a/arch/arm/boot/dts/tegra-harmony.dts
> +++ b/arch/arm/boot/dts/tegra-harmony.dts
> @@ -25,8 +25,11 @@
> ranges;
>
> intc: intc {
> + compatible = "nvidia,tegra250-gic", "arm,gic";
> interrupt-controller;
> #interrupt-cells = <1>;
> + reg = < 0x50041000 0x1000
> + 0x50040100 0x100 >;
> };
> };
>
> diff --git a/arch/arm/mach-tegra/board-dt.c b/arch/arm/mach-tegra/board-dt.c
> index 0efedb8..fb0d75d 100644
> --- a/arch/arm/mach-tegra/board-dt.c
> +++ b/arch/arm/mach-tegra/board-dt.c
> @@ -22,7 +22,9 @@
> #include <linux/clk.h>
> #include <linux/dma-mapping.h>
> #include <linux/of.h>
> +#include <linux/of_address.h>
> #include <linux/of_fdt.h>
> +#include <linux/of_irq.h>
> #include <linux/of_platform.h>
> #include <linux/pda_power.h>
> #include <linux/io.h>
> @@ -137,8 +139,20 @@ static struct of_device_id tegra_dt_match_table[] __initdata = {
> {}
> };
>
> +struct of_device_id gic_match[] __initdata = {
> + { .compatible = "nvidia,tegra250-gic", },
> + {}
> +};
> +
> static void __init tegra_dt_init(void)
> {
> + struct device_node *node;
> +
> + node = of_find_matching_node_by_address(NULL, gic_match,
> + TEGRA_ARM_INT_DIST_BASE);
> + if (node)
> + of_irq_domain_add_simple(node, INT_GIC_BASE, INT_MAIN_NR);
> +
> /*
> * Before registering devices; tell Linux about which device nodes
> * are intended to be registered so that it doesn't create devices
> --
> 1.7.1
>
prev parent reply other threads:[~2011-04-30 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 4:10 [PATCH v2] ARM: Tegra: dt: Set up an OF IRQ translation range Stephen Warren
[not found] ` <1304136608-11584-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-04-30 6:36 ` Grant Likely [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=20110430063641.GC3103@ponder.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).