From: Zhen Lei <thunder.leizhen@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Jianguo Chen <chenjianguo3@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Libin <huawei.libin@huawei.com>,
Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 0/2] ARM: support PHYS_OFFSET minimum aligned at 64KiB boundary
Date: Tue, 15 Sep 2020 09:52:02 +0800 [thread overview]
Message-ID: <20200915015204.2971-1-thunder.leizhen@huawei.com> (raw)
Currently, only support the kernels where the base of physical memory is
at a 16MiB boundary. Because the add/sub instructions only contains 8bits
unrotated value. But we can use one more "add/sub" instructions to handle
bits 23-16, to support PHYS_OFFSET minimum aligned at 64KiB boundary.
This function is required at least by some Huawei boards, such as Hi1380
board. Becuase the kernel Image is loaded at 2MiB boundary.
Zhen Lei (2):
ARM: fix trivial comments in head.S
ARM: support PHYS_OFFSET minimum aligned at 64KiB boundary
arch/arm/Kconfig | 18 +++++++++++++++++-
arch/arm/include/asm/memory.h | 16 +++++++++++++---
arch/arm/kernel/head.S | 31 ++++++++++++++++++++++---------
3 files changed, 52 insertions(+), 13 deletions(-)
--
1.8.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-15 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 1:52 Zhen Lei [this message]
2020-09-15 1:52 ` [PATCH 1/2] ARM: fix trivial comments in head.S Zhen Lei
2020-09-15 1:52 ` [PATCH 2/2] ARM: support PHYS_OFFSET minimum aligned at 64KiB boundary Zhen Lei
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=20200915015204.2971-1-thunder.leizhen@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=chenjianguo3@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
/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).