linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: Xilinx: Adding Xilinx board support
Date: Sat, 5 Feb 2011 16:18:53 +0000	[thread overview]
Message-ID: <20110205161853.GC29411@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <eee52c43-76da-4e47-9f40-4a2d7ee963b6@VA3EHSMHS032.ehs.local>

On Sat, Feb 05, 2011 at 09:08:42AM -0700, John Linn wrote:
> +void __init irq_init(void)
> +{
> +	gic_cpu_base_addr = (void __iomem *)SCU_GIC_CPU_BASE;

Just pass this address into gic_init - there's no need to initialize
this variable yourself anymore.

> +	gic_init(0, 29, (void __iomem *)SCU_GIC_DIST_BASE, gic_cpu_base_addr);
...
> +static struct map_desc io_desc[] __initdata = {
...
> +#ifdef CONFIG_DEBUG_LL
> +	{
> +		.virtual	= UART0_BASE,
> +		.pfn		= __phys_to_pfn(UART0_BASE),
> +		.length		= SZ_4K,
> +		.type		= MT_DEVICE,
> +	},
> +#endif

You shouldn't need to do this if your addruart macro in mach/debug-macros.S
is correctly returning the virtual and physical addresses in rp and rv.

  reply	other threads:[~2011-02-05 16:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1296922124-23379-1-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08 ` [PATCH 1/4] ARM: Xilinx: Adding Xilinx platform infrastructure support John Linn
2011-02-05 16:16   ` Russell King - ARM Linux
2011-02-05 16:20     ` [PATCH 1/4] ARM: Xilinx: Adding Xilinx platform infrastructuresupport John Linn
     [not found] ` <1296922124-23379-2-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08   ` [PATCH 2/4] ARM: Xilinx: Adding Xilinx board support John Linn
2011-02-05 16:18     ` Russell King - ARM Linux [this message]
2011-02-05 16:21       ` John Linn
2011-02-05 17:25       ` John Linn
2011-02-07 15:44       ` John Linn
2011-02-07 20:54         ` Russell King - ARM Linux
2011-02-07 20:55           ` John Linn
     [not found]   ` <1296922124-23379-3-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08     ` [PATCH 3/4] ARM: Xilinx: Adding timer support to the platform John Linn
2011-02-05 16:36       ` Russell King - ARM Linux
2011-02-05 17:12         ` John Linn
2011-02-08 14:35       ` Russell King - ARM Linux
2011-02-08 15:06         ` John Linn
2011-02-08 15:25           ` Arnd Bergmann
2011-02-08 17:11             ` John Linn
2011-02-08 17:53             ` John Linn
2011-02-08 18:24               ` Arnd Bergmann
2011-02-08 18:31                 ` Grant Likely
     [not found]     ` <1296922124-23379-4-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08       ` [PATCH 4/4] ARM: Xilinx: base header files and assembly macros John Linn
2011-02-05 16:43         ` Russell King - ARM Linux
2011-02-05 17:19           ` John Linn
2011-02-08  0:14           ` John Linn
2011-02-08  8:27             ` Russell King - ARM Linux
2011-02-08 14:08               ` John Linn
2011-02-08 14:30                 ` Russell King - ARM Linux
     [not found] <1296922637-24662-1-git-send-email-john.linn@xilinx.com>
     [not found] ` <1296922637-24662-2-git-send-email-john.linn@xilinx.com>
2011-02-05 16:17   ` [PATCH 2/4] ARM: Xilinx: Adding Xilinx board support John Linn
2011-02-06  0:45     ` Jamie Iles
2011-02-07 14:05       ` John Linn

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=20110205161853.GC29411@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).