From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] ARM: BCM2836: Add io map initialization for bcm2836.
Date: Tue, 21 Apr 2015 23:11:33 +0200 [thread overview]
Message-ID: <60195891.q3RtUhgfkn@wuerfel> (raw)
In-Reply-To: <87oamh9q12.fsf@eliezer.anholt.net>
On Tuesday 21 April 2015 13:37:13 Eric Anholt wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > On Tuesday 21 April 2015 11:09:52 Eric Anholt wrote:
> >> +static struct map_desc bcm2836_io_map __initdata = {
> >> + .virtual = BCM2835_PERIPH_VIRT,
> >> + .pfn = __phys_to_pfn(BCM2836_PERIPH_PHYS),
> >> + .length = BCM2835_PERIPH_SIZE,
> >> + .type = MT_DEVICE
> >> +};
> >> +
> >> static void __init bcm2835_map_io(void)
> >> {
> >> - iotable_init(&io_map, 1);
> >> + iotable_init(&bcm2835_io_map, 1);
> >> +}
> >> +
> >> +static void __init bcm2836_map_io(void)
> >> +{
> >> + iotable_init(&bcm2836_io_map, 1);
> >> }
> >>
> >
> > Can you explain what this is needed for? Most platform ports don't
> > do this any more.
>
> Nope, I can't! I'm not sure what the bcm2835 side of it does, and I was
> just replicating that for 2836.
>
> Should it be removed from 2835, too?
>
Hard to know. Does anything reference BCM2835_PERIPH_VIRT? Does it work
if you remove it?
Arnd
next prev parent reply other threads:[~2015-04-21 21:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 18:09 BCM2836 (Raspberry Pi 2) port Eric Anholt
2015-04-21 18:09 ` [PATCH 1/9] dt-bindings: Add root properties for Raspberry Pi 2 Eric Anholt
2015-04-24 4:27 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 2/9] ARM: BCM2835: Split peripheral definitions off to a common include Eric Anholt
2015-04-24 4:28 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 3/9] ARM: Make a copy of the 2835 dts for the 2836 Eric Anholt
2015-04-24 4:35 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 4/9] ARM: Update the device trees for 2836 Eric Anholt
2015-04-24 4:36 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 5/9] ARM: BCM2836: Add io map initialization for bcm2836 Eric Anholt
2015-04-21 18:53 ` Arnd Bergmann
2015-04-21 20:37 ` Eric Anholt
2015-04-21 21:11 ` Arnd Bergmann [this message]
2015-04-21 23:02 ` Eric Anholt
2015-04-22 7:22 ` Arnd Bergmann
2015-04-24 7:16 ` Arnd Bergmann
2015-04-21 18:09 ` [PATCH 6/9] ARM: Make a Kconfig option for shared BCM2835/BCM2836 code Eric Anholt
2015-04-21 18:09 ` [PATCH 7/9] ARM: Add Kconfig support for bcm2836 Eric Anholt
2015-04-21 18:59 ` Arnd Bergmann
2015-04-21 20:38 ` Eric Anholt
2015-04-24 3:30 ` Stephen Warren
2015-04-21 18:09 ` [PATCH 8/9] ARM: Add MAINTAINERS for 2836 Eric Anholt
2015-04-24 4:38 ` Stephen Warren
2015-04-24 17:03 ` Eric Anholt
2015-04-21 18:09 ` [PATCH 9/9] ARM: BCM283x: Register fixed clocks for uart in the DT Eric Anholt
2015-04-24 4:44 ` Stephen Warren
2015-04-24 17:06 ` Eric Anholt
2015-04-25 4:23 ` Stephen Warren
2015-04-24 4:25 ` BCM2836 (Raspberry Pi 2) port Stephen Warren
2015-04-24 18:41 ` Eric Anholt
2015-04-24 18:57 ` Stephen Warren
2015-04-27 17:19 ` Eric Anholt
2015-05-08 16:14 ` Alexander Stein
2015-05-12 2:36 ` Stephen Warren
2015-05-12 15:39 ` Alexander Stein
2015-05-12 16:03 ` Stephen Warren
2015-05-12 17:32 ` Eric Anholt
2015-05-12 22:03 ` Stephen Warren
2015-05-13 17:46 ` Eric Anholt
2015-05-13 18:32 ` Stephen Warren
2015-05-13 18:59 ` Eric Anholt
2015-04-29 2:38 ` Stephen Warren
2015-04-29 3:41 ` Florian Fainelli
2015-05-06 18:51 ` Eric Anholt
2015-05-06 19:05 ` 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=60195891.q3RtUhgfkn@wuerfel \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox