From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: early ioremap and permanent fixmap
Date: Tue, 6 May 2014 17:58:04 -0500 [thread overview]
Message-ID: <1399417087-24772-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <robh@kernel.org>
This is an updated series based on previous work by Mark Salter and Leif
Lindholm. The last version with the ARM bits is here[1]. I've added
fixmap permanent mappings support to this series in order to support
generic earlycon on ARM. This enables early console output before any
machine hooks run and is configurable on the command line unlike
earlyprintk.
This is based on the tty-next tree which has the generic earlycon
support for 3.16. A git tree is available here[2].
Rob
[1] https://lkml.org/lkml/2014/2/12/608
[2] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git arm-fixmap
Mark Salter (2):
arm: use generic fixmap.h
arm: add early_ioremap support
Rob Herring (1):
ARM: fixmap early permanent mapping support
arch/arm/Kconfig | 14 +++++
arch/arm/include/asm/Kbuild | 1 +
arch/arm/include/asm/fixmap.h | 51 +++++++++++-------
arch/arm/include/asm/io.h | 1 +
arch/arm/include/asm/mach/map.h | 1 +
arch/arm/kernel/setup.c | 2 +
arch/arm/mm/Makefile | 2 +
arch/arm/mm/early_ioremap.c | 112 ++++++++++++++++++++++++++++++++++++++++
arch/arm/mm/init.c | 2 +-
arch/arm/mm/mmu.c | 8 +--
10 files changed, 172 insertions(+), 22 deletions(-)
create mode 100644 arch/arm/mm/early_ioremap.c
--
1.9.1
next reply other threads:[~2014-05-06 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:58 Rob Herring [this message]
2014-05-06 22:58 ` [PATCH 1/3] arm: use generic fixmap.h Rob Herring
2014-05-06 22:58 ` [PATCH 2/3] arm: add early_ioremap support Rob Herring
2014-05-06 22:58 ` [PATCH 3/3] ARM: fixmap early permanent mapping support Rob Herring
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=1399417087-24772-1-git-send-email-robherring2@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).