linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, earlyconsole and io mapping
Date: Mon, 30 Mar 2015 14:11:48 +0200	[thread overview]
Message-ID: <20150330141148.299f38a4@free-electrons.com> (raw)
In-Reply-To: <87iodivgfm.fsf@free.fr>

Dear Robert Jarzmik,

On Mon, 30 Mar 2015 14:05:33 +0200, Robert Jarzmik wrote:

> I was wondering how the earlyconsole was supposed to work in order to add
> support to the pxa architecture. More specifically, I don't understand how the
> memory mapping is supposed to be available at the early parameters parsing.
> 
> The thing I don't understand is that :
>  - in kernel initialization, parse_early_param() is called before
>    machine_desc->map_io()
>  - as a consequence, the architecture didn't add the vm early mapping for serial
>    peripheral (which is added in pxa_map_io())
>  - as a consequence, earlycon_map() will fail to map the serial MMIO
>    (as in stack showed in [1])
> 
> Therefore, are there non-DT earlycon users on the list, and could they tell me
> what way they get earlycon support in their arm boards please ?

A very early mapping of the I/O space is done in head.S, way before you
get into C code:

  http://lxr.free-electrons.com/source/arch/arm/kernel/head.S#L277

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-30 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 12:05 ARM, earlyconsole and io mapping Robert Jarzmik
2015-03-30 12:11 ` Thomas Petazzoni [this message]
2015-03-30 13:25   ` Robert Jarzmik
2015-03-30 23:31 ` Peter Hurley
2015-03-31  9:11   ` Robert Jarzmik

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=20150330141148.299f38a4@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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).