From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/6] arm: add early_ioremap support
Date: Wed, 15 Jan 2014 16:32:03 -0800 [thread overview]
Message-ID: <52D72883.3020500@codeaurora.org> (raw)
In-Reply-To: <1389325833-16535-5-git-send-email-msalter@redhat.com>
On 1/9/2014 7:50 PM, Mark Salter wrote:
....
> diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
> index 987a7f5..038fb75 100644
> --- a/arch/arm/kernel/setup.c
> +++ b/arch/arm/kernel/setup.c
> @@ -36,6 +36,7 @@
> #include <asm/cpu.h>
> #include <asm/cputype.h>
> #include <asm/elf.h>
> +#include <asm/io.h>
> #include <asm/procinfo.h>
> #include <asm/psci.h>
> #include <asm/sections.h>
> @@ -887,6 +888,8 @@ void __init setup_arch(char **cmdline_p)
>
> parse_early_param();
>
> + early_ioremap_init();
> +
> sort(&meminfo.bank, meminfo.nr_banks, sizeof(meminfo.bank[0]), meminfo_cmp, NULL);
>
> early_paging_init(mdesc, lookup_processor_type(read_cpuid_id()));
Any chance we could do this even earlier, say right after
setup_processor? It would be nice to be able to do this while FDT
scanning (I have a use case in mind, potential patches are in the works)
<snip>
> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
> index 580ef2d..bef59b9 100644
> --- a/arch/arm/mm/mmu.c
> +++ b/arch/arm/mm/mmu.c
> @@ -34,6 +34,7 @@
> #include <asm/mach/arch.h>
> #include <asm/mach/map.h>
> #include <asm/mach/pci.h>
> +#include <asm/early_ioremap.h>
>
> #include "mm.h"
> #include "tcm.h"
> @@ -1405,6 +1406,7 @@ void __init paging_init(const struct machine_desc *mdesc)
> {
> void *zero_page;
>
> + early_ioremap_reset();
> build_mem_type_table();
> prepare_page_table();
> map_lowmem();
>
Neither x86 nor arm64 get rid of existing mapping in paging_init. Is
there a reason this needs to be here for arm? Are there concerns about
alias mappings?
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-16 0:32 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
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 [this message]
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=52D72883.3020500@codeaurora.org \
--to=lauraa@codeaurora.org \
--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).