From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] ARM: u300: push down syscon registers
Date: Fri, 3 May 2013 16:43:47 +0200 [thread overview]
Message-ID: <201305031643.47527.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdZHRQqd277Qv8O0dek_jYb=eewhpLYfKtip-YLYx_ukUA@mail.gmail.com>
On Friday 03 May 2013, Linus Walleij wrote:
> I could do something similar by creating a U300 syscon node
> and referring to it from the clk node, so the clk looks up its
> syscon to find the base.
>
> If so, I can build this on top of the current patch series
> with multiplatform and all, as I convert the clocks to DT
> (which is the next and final step).
Yes, I think this is a good plan. If there are just two drivers,
that is probably the easiest way to do it. Using the syscon
driver is not very different in the end and avoids mapping the
same physical address range multiple times (having a static mapping
avoids this too), and I'd prefer that if you have more drivers
that need to get to the same registers.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Mike Turquette
<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Linus Walleij
<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 1/7] ARM: u300: push down syscon registers
Date: Fri, 3 May 2013 16:43:47 +0200 [thread overview]
Message-ID: <201305031643.47527.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdZHRQqd277Qv8O0dek_jYb=eewhpLYfKtip-YLYx_ukUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Friday 03 May 2013, Linus Walleij wrote:
> I could do something similar by creating a U300 syscon node
> and referring to it from the clk node, so the clk looks up its
> syscon to find the base.
>
> If so, I can build this on top of the current patch series
> with multiplatform and all, as I convert the clocks to DT
> (which is the next and final step).
Yes, I think this is a good plan. If there are just two drivers,
that is probably the easiest way to do it. Using the syscon
driver is not very different in the end and avoids mapping the
same physical address range multiple times (having a static mapping
avoids this too), and I'd prefer that if you have more drivers
that need to get to the same registers.
Arnd
next prev parent reply other threads:[~2013-05-03 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 16:16 [PATCH 0/7] ARM: u300 multiplatform support Linus Walleij
2013-05-02 16:16 ` [PATCH 1/7] ARM: u300: push down syscon registers Linus Walleij
2013-05-02 16:21 ` Arnd Bergmann
2013-05-02 16:38 ` Linus Walleij
2013-05-02 17:39 ` Arnd Bergmann
2013-05-03 8:01 ` Linus Walleij
2013-05-03 8:01 ` Linus Walleij
2013-05-03 14:43 ` Arnd Bergmann [this message]
2013-05-03 14:43 ` Arnd Bergmann
2013-05-03 4:04 ` Mike Turquette
2013-05-02 16:16 ` [PATCH 2/7] ARM: u300: remove deps from debug macro Linus Walleij
2013-05-02 16:16 ` [PATCH 3/7] ARM: u300: delete <mach/hardware.h> Linus Walleij
2013-05-02 16:16 ` [PATCH 4/7] ARM: u300: delete <mach/irqs.h> Linus Walleij
2013-05-02 16:16 ` [PATCH 5/7] ARM: u300: localize <mach/u300-regs.h> Linus Walleij
2013-05-02 16:16 ` [PATCH 6/7] ARM: u300: convert to multiplatform Linus Walleij
2013-05-02 16:16 ` [PATCH 7/7] ARM: u300: delete remnant machine headers Linus Walleij
2013-05-02 16:23 ` [PATCH 0/7] ARM: u300 multiplatform support Arnd Bergmann
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=201305031643.47527.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.