From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/6] arm: add early_ioremap support
Date: Fri, 10 Jan 2014 16:58:47 +0000 [thread overview]
Message-ID: <20140110165847.GG925@arm.com> (raw)
In-Reply-To: <CAL_JsqLZQ=3gph4yaNSrZ5oPL3kasQKqA5C5+my0GwjGHsvMeQ@mail.gmail.com>
On Fri, Jan 10, 2014 at 04:11:03PM +0000, Rob Herring wrote:
> On Thu, Jan 9, 2014 at 9:50 PM, Mark Salter <msalter@redhat.com> wrote:
> > This patch uses the generic early_ioremap code to implement
> > early_ioremap for ARM. The ARM-specific bits come mostly from
> > an earlier patch from Leif Lindholm <leif.lindholm@linaro.org>
> > here:
> >
> > https://lkml.org/lkml/2013/10/3/279
>
> I think this will be useful to implement an arm64 style earlycon for
> arm as the current DEBUG_LL doesn't really work with multi-platform
> kernels. I started on this and quickly realized I needed the fixmap
> support.
It would be even better if you can make it more generic
(drivers/tty/serial/) and keep DEBUG_LL as a specialised case for
arch/arm (when !multi-platform).
--
Catalin
next prev parent reply other threads:[~2014-01-10 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 3:50 [PATCH v3 0/6] generic early_ioremap support Mark Salter
2014-01-10 3:50 ` [PATCH v3 2/6] mm: create generic early_ioremap() support Mark Salter
2014-01-10 3:50 ` [PATCH v3 4/6] arm: add early_ioremap support Mark Salter
2014-01-10 11:34 ` Russell King - ARM Linux
2014-01-10 13:50 ` Mark Salter
2014-01-10 16:11 ` Rob Herring
2014-01-10 16:58 ` Catalin Marinas [this message]
2014-01-10 20:04 ` Rob Herring
2014-01-10 20:09 ` Rob Herring
2014-01-10 20:51 ` Mark Salter
2014-01-10 20:40 ` Stephen Boyd
2014-01-10 20:52 ` Mark Salter
2014-01-16 0:32 ` Laura Abbott
2014-01-16 0:35 ` Russell King - ARM Linux
2014-01-16 2:13 ` Mark Salter
2014-01-10 3:50 ` [PATCH v3 5/6] arm64: initialize pgprot info earlier in boot Mark Salter
2014-01-10 3:50 ` [PATCH v3 6/6] arm64: add early_ioremap support Mark Salter
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=20140110165847.GG925@arm.com \
--to=catalin.marinas@arm.com \
--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).