From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] arm64: add early_ioremap support
Date: Thu, 6 Mar 2014 02:20:32 -0600 [thread overview]
Message-ID: <CAL_JsqLSTMp4_OREGdGtah31HZmmMAgqi3eb3NZgM04dfqZNMQ@mail.gmail.com> (raw)
In-Reply-To: <1394037524.5094.35.camel@deneb.redhat.com>
On Wed, Mar 5, 2014 at 10:38 AM, Mark Salter <msalter@redhat.com> wrote:
> On Tue, 2014-03-04 at 17:31 -0600, Rob Herring wrote:
>> On Tue, Mar 4, 2014 at 2:08 PM, Mark Salter <msalter@redhat.com> wrote:
>> > Add support for early IO or memory mappings which are needed
>> > before the normal ioremap() is usable. This also adds fixmap
>> > support for permanent fixed mappings such as that used by the
>> > earlyprintk device register region.
>>
>> One minor comment:
>>
>> > +enum fixed_addresses {
>> > + FIX_EARLYCON,
>>
>> Can you align this name with x86 and rename to FIX_EARLYCON_MEM_BASE.
>> Doing that will help enable the earlycon driver in 8250_early.c.
>
> Is there any advantage to earlycon=uart8250 vs. earlyprintk=uart8250?
Functionally, they are pretty much the same. I'm working on a series
to generalize earlycon and then we will be able to delete
early_printk.c from arm64 and ultimately share with arm. Doing this
alignment just saves a patch to change it later.
> I don't mind using FIX_EARLYCON_MEM_BASE, but CONFIG_FIX_EARLYCON_MEM
> is X86 only right now and I think changing that should be a separate
> patch.
Yes, definitely.
Rob
prev parent reply other threads:[~2014-03-06 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 20:08 [PATCH 0/5] mm: generic early_ioremap support Mark Salter
2014-03-04 20:08 ` [PATCH 2/5] mm: create generic early_ioremap() support Mark Salter
2014-03-05 22:29 ` Andrew Morton
2014-03-06 21:25 ` Mark Salter
2014-03-04 20:08 ` [PATCH 4/5] arm64: initialize pgprot info earlier in boot Mark Salter
2014-03-04 20:08 ` [PATCH 5/5] arm64: add early_ioremap support Mark Salter
2014-03-04 23:31 ` Rob Herring
2014-03-05 16:38 ` Mark Salter
2014-03-06 8:20 ` Rob Herring [this message]
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=CAL_JsqLSTMp4_OREGdGtah31HZmmMAgqi3eb3NZgM04dfqZNMQ@mail.gmail.com \
--to=robherring2@gmail.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).