All of lore.kernel.org
 help / color / mirror / Atom feed
From: sophian.yoma@gmail.com (yoma sophian)
To: linux-arm-kernel@lists.infradead.org
Subject: how to mapping device memory in head.S
Date: Mon, 13 Apr 2015 09:30:39 +0800	[thread overview]
Message-ID: <CADUS3o=utaLKTO-kOZmegcxcs0SU+ex7n4PhpdNqvwM9sykzuw@mail.gmail.com> (raw)
In-Reply-To: <20150412191420.GP12732@n2100.arm.linux.org.uk>

hi Russell

2015-04-13 3:14 GMT+08:00 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> On Sun, Apr 12, 2015 at 08:23:59PM +0800, yoma sophian wrote:
>> hi all:
>> I need to map peripheral address in head.S for early usage.
>
> Basically, you do not.
>
> Please explain in detail what you're trying to do.
We try to calculate and record the booting time from head.S,
start_kernel to rest_init.
so we need to mapping the memory for getting count of counter quite early.
it seems quite waist memory mapping if we use short-descriptor
1st-level section descriptor formats.
And we want to get fix mapping such that the va of counter will be the
same and the va of get counter API doesn't need to change.

>
>> 1. CONFIG_DEBUG_LL is  using short-descriptor 1st-level section
>> descriptor formats. Is it possible to use short-descriptor 2nd-level
>> small page descriptor in head.S?
>
> Definitely not, there is no memory management at that stage to allocate
> a 2nd level descriptor table.
>
>> 2. The peripheral mapping virtual address created in head.S is need to
>> access even after paging_init. Is it possible to put the mapping in
>> the persistent mapping in head.S?
>
> No, we don't support that.
>
Appreciate your kind help,

      reply	other threads:[~2015-04-13  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 12:23 how to mapping device memory in head.S yoma sophian
2015-04-12 19:14 ` Russell King - ARM Linux
2015-04-13  1:30   ` yoma sophian [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='CADUS3o=utaLKTO-kOZmegcxcs0SU+ex7n4PhpdNqvwM9sykzuw@mail.gmail.com' \
    --to=sophian.yoma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.