From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 1/5] powerpc: move ADDR_MAP to Kconfig
Date: Tue, 2 Jun 2020 10:28:41 -0400 [thread overview]
Message-ID: <20200602142841.GG21630@bill-the-cat> (raw)
In-Reply-To: <20200602120423.6285-2-m.szyprowski@samsung.com>
On Tue, Jun 02, 2020 at 02:04:19PM +0200, Marek Szyprowski wrote:
> Move ADDR_MAP related config options from include/configs/*.h to the
> proper place in lib/Kconfig. This has been done using
> ./tools/moveconfig.py and manual inspection of the generated changes.
> This is a preparation to use ADDR_MAP helper on ARM 32bit Raspberry Pi4
> board for mapping the PCIe XHCI MMIO, which is above the 4GiB identity
> mapping limit.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200602/7d275416/attachment.sig>
next prev parent reply other threads:[~2020-06-02 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200602120704eucas1p29ca38e04d720f89bb6d1a099d41d9abb@eucas1p2.samsung.com>
2020-06-02 12:04 ` [PATCH v4 0/5] ARM: arbitrary virtual-physical mappings for RPi4 XHCI support Marek Szyprowski
2020-06-02 12:04 ` [PATCH v4 1/5] powerpc: move ADDR_MAP to Kconfig Marek Szyprowski
2020-06-02 14:28 ` Tom Rini [this message]
2020-06-02 12:04 ` [PATCH v4 2/5] arm: provide a function for boards init code to modify MMU virtual-physical map Marek Szyprowski
2020-06-02 14:28 ` Tom Rini
2020-06-02 12:04 ` [PATCH v4 3/5] mmc: bcm283x: fix int to pointer cast Marek Szyprowski
2020-06-02 12:04 ` [PATCH v4 4/5] rpi4: add a mapping for the PCIe XHCI controller MMIO registers (ARM 32bit) Marek Szyprowski
2020-06-02 12:04 ` [PATCH v4 5/5] config: Enable support for the XHCI controller on RPI4 board Marek Szyprowski
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=20200602142841.GG21630@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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