From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] zynq: move static peripheral mappings
Date: Tue, 23 Oct 2012 17:48:33 +0000 [thread overview]
Message-ID: <201210231748.33373.arnd@arndb.de> (raw)
In-Reply-To: <20121023162641.GG20593@beefymiracle.amer.corp.natinst.com>
On Tuesday 23 October 2012, Josh Cartwright wrote:
> On Tue, Oct 23, 2012 at 02:50:11PM +0000, Arnd Bergmann wrote:
> > On Monday 22 October 2012, Josh Cartwright wrote:
>
> > > diff --git a/arch/arm/mach-zynq/include/mach/zynq_soc.h b/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > index d0d3f8f..ae3b236 100644
> > > --- a/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > +++ b/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > -#define TTC0_PHYS 0xF8001000
> > > -#define TTC0_VIRT TTC0_PHYS
> > > +#define TTC0_PHYS 0xF8001000
> > > +#define TTC0_SIZE SZ_4K
> > > +#define TTC0_VIRT (UART0_VIRT - TTC0_SIZE)
> >
> > It's quite likely that this does not have to be a fixed mapping
> > any more. Just have a look at how drivers/clocksource/dw_apb_timer_of.c
> > calls of_iomap() to get the address.
>
> Yes, this is already on my list of plans. The in-tree TTC driver
> unfortunately doesn't yet support device tree bindings. Are you
> comfortable waiting on the DT-ification of the TTC in a follow-up
> patchset?
Yes, that's fine. If you do that, you can also move the driver to
drivers/clocksource in another patch.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Josh Cartwright <josh.cartwright@ni.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH v2 2/4] zynq: move static peripheral mappings
Date: Tue, 23 Oct 2012 17:48:33 +0000 [thread overview]
Message-ID: <201210231748.33373.arnd@arndb.de> (raw)
In-Reply-To: <20121023162641.GG20593@beefymiracle.amer.corp.natinst.com>
On Tuesday 23 October 2012, Josh Cartwright wrote:
> On Tue, Oct 23, 2012 at 02:50:11PM +0000, Arnd Bergmann wrote:
> > On Monday 22 October 2012, Josh Cartwright wrote:
>
> > > diff --git a/arch/arm/mach-zynq/include/mach/zynq_soc.h b/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > index d0d3f8f..ae3b236 100644
> > > --- a/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > +++ b/arch/arm/mach-zynq/include/mach/zynq_soc.h
> > > -#define TTC0_PHYS 0xF8001000
> > > -#define TTC0_VIRT TTC0_PHYS
> > > +#define TTC0_PHYS 0xF8001000
> > > +#define TTC0_SIZE SZ_4K
> > > +#define TTC0_VIRT (UART0_VIRT - TTC0_SIZE)
> >
> > It's quite likely that this does not have to be a fixed mapping
> > any more. Just have a look at how drivers/clocksource/dw_apb_timer_of.c
> > calls of_iomap() to get the address.
>
> Yes, this is already on my list of plans. The in-tree TTC driver
> unfortunately doesn't yet support device tree bindings. Are you
> comfortable waiting on the DT-ification of the TTC in a follow-up
> patchset?
Yes, that's fine. If you do that, you can also move the driver to
drivers/clocksource in another patch.
Arnd
next prev parent reply other threads:[~2012-10-23 17:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 21:10 [PATCH v2 0/4] zynq subarch cleanups Josh Cartwright
2012-10-22 21:10 ` Josh Cartwright
2012-10-22 21:11 ` [PATCH v2 1/4] ARM: annotate VMALLOC_END definition with _AC Josh Cartwright
2012-10-22 21:11 ` Josh Cartwright
2012-10-22 21:12 ` [PATCH v2 2/4] zynq: move static peripheral mappings Josh Cartwright
2012-10-22 21:12 ` Josh Cartwright
2012-10-23 14:50 ` Arnd Bergmann
2012-10-23 14:50 ` Arnd Bergmann
2012-10-23 16:26 ` Josh Cartwright
2012-10-23 16:26 ` Josh Cartwright
2012-10-23 17:48 ` Arnd Bergmann [this message]
2012-10-23 17:48 ` Arnd Bergmann
2012-10-23 20:27 ` Nick Bowler
2012-10-23 20:27 ` Nick Bowler
2012-10-23 23:42 ` Josh Cartwright
2012-10-23 23:42 ` Josh Cartwright
2012-10-24 20:19 ` Nick Bowler
2012-10-24 20:19 ` Nick Bowler
2012-10-23 20:09 ` Rob Herring
2012-10-23 20:09 ` Rob Herring
2012-10-23 20:53 ` Josh Cartwright
2012-10-23 20:53 ` Josh Cartwright
2012-10-23 21:17 ` Nick Bowler
2012-10-23 21:17 ` Nick Bowler
2012-10-23 21:24 ` Josh Cartwright
2012-10-23 21:24 ` Josh Cartwright
2012-10-22 21:12 ` [PATCH v2 3/4] zynq: use GIC device tree bindings Josh Cartwright
2012-10-22 21:12 ` Josh Cartwright
2012-10-22 21:13 ` [PATCH v2 4/4] zynq: remove use of CLKDEV_LOOKUP Josh Cartwright
2012-10-22 21:13 ` Josh Cartwright
2012-10-23 14:41 ` [PATCH v2 0/4] zynq subarch cleanups Arnd Bergmann
2012-10-23 14:41 ` Arnd Bergmann
2012-10-23 20:50 ` Rob Herring
2012-10-23 20:50 ` Rob Herring
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=201210231748.33373.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.