public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: BCM2835: Skip doing our own iotable_init() initialization.
Date: Thu, 23 Apr 2015 21:28:31 -0600	[thread overview]
Message-ID: <5539B85F.1060409@wwwdotorg.org> (raw)
In-Reply-To: <1429811351-12600-1-git-send-email-eric@anholt.net>

On 04/23/2015 11:49 AM, Eric Anholt wrote:
> The only thing we were using this 16MB mapping of IO peripherals for
> was the uart's early debug mapping.  If we just drop the map_io hook,
> the kernel will call debug_ll_io_init() for us, which maps the single
> page needed for the device.

I /think/ debug_ll_io_init() didn't exist (or didn't map memory) when I
first upstreamed RPi support. Anyway,

Tested-by: Stephen Warren <swarren@wwwdotorg•org>
Acked-by: Stephen Warren <swarren@wwwdotorg•org>

  reply	other threads:[~2015-04-24  3:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 17:49 [PATCH] ARM: BCM2835: Skip doing our own iotable_init() initialization Eric Anholt
2015-04-24  3:28 ` Stephen Warren [this message]
2015-04-27 18:25 ` Lee Jones

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=5539B85F.1060409@wwwdotorg.org \
    --to=swarren@wwwdotorg$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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