From: Andrii Anisov <andrii.anisov@gmail.com>
To: xen-devel@lists.xen.org
Cc: Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>,
julien.grall@arm.com, sstabellini@kernel.org,
Andrii Anisov <andrii_anisov@epam.com>,
Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Subject: [PATCH V2 2/2] xen:arm: earlyprintk configuration for R-Car Gen3 boards
Date: Thu, 27 Jul 2017 17:50:13 +0300 [thread overview]
Message-ID: <1501167013-32032-2-git-send-email-andrii.anisov@gmail.com> (raw)
In-Reply-To: <1501167013-32032-1-git-send-email-andrii.anisov@gmail.com>
From: Andrii Anisov <andrii_anisov@epam.com>
Introduce an earlyprintk configuration for R-Car Gen3 SoC based development
boards, like:
- Salvator-X [http://elinux.org/R-Car/Boards/Salvator-X]
- M3ULCB [http://elinux.org/R-Car/Boards/M3SK]
- H3ULCB [http://elinux.org/R-Car/Boards/H3SK]
Signed-off-by: Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Signed-off-by: Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>
Signed-off-by: Andrii Anisov <andrii_anisov@epam.com>
---
Changes in v2:
- s/H3/Gen3
- place a configuration symbol in an alpahabetical order
---
docs/misc/arm/early-printk.txt | 1 +
xen/arch/arm/Rules.mk | 1 +
2 files changed, 2 insertions(+)
diff --git a/docs/misc/arm/early-printk.txt b/docs/misc/arm/early-printk.txt
index 41b528b..eb08821 100644
--- a/docs/misc/arm/early-printk.txt
+++ b/docs/misc/arm/early-printk.txt
@@ -41,6 +41,7 @@ the name of the machine:
- lager: printk with SCIF0 on Renesas R-Car H2 processors
- midway: printk with the pl011 on Calxeda Midway processors
- omap5432: printk with UART3 on TI OMAP5432 processors
+ - rcar3: printk with SCIF2 on Renesas R-Car Gen3 processors
- seattle: printk with pl011 for AMD Seattle processor
- sun6i: printk with 8250 on Allwinner A31 processors
- sun7i: printk with 8250 on Allwinner A20 processors
diff --git a/xen/arch/arm/Rules.mk b/xen/arch/arm/Rules.mk
index 569a0ba..2ae7451 100644
--- a/xen/arch/arm/Rules.mk
+++ b/xen/arch/arm/Rules.mk
@@ -36,6 +36,7 @@ EARLY_PRINTK_juno := pl011,0x7ff80000
EARLY_PRINTK_lager := scif,0xe6e60000
EARLY_PRINTK_midway := pl011,0xfff36000
EARLY_PRINTK_omap5432 := 8250,0x48020000,2
+EARLY_PRINTK_rcar3 := scif,0xe6e88000
EARLY_PRINTK_seattle := pl011,0xe1010000
EARLY_PRINTK_sun6i := 8250,0x01c28000,2
EARLY_PRINTK_sun7i := 8250,0x01c28000,2
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-27 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 14:50 [PATCH V2 1/2] xen:arm64: Add SCIF UART support for earlyprintk Andrii Anisov
2017-07-27 14:50 ` Andrii Anisov [this message]
2017-08-01 11:47 ` [PATCH V2 2/2] xen:arm: earlyprintk configuration for R-Car Gen3 boards Julien Grall
2017-08-01 11:46 ` [PATCH V2 1/2] xen:arm64: Add SCIF UART support for earlyprintk Julien Grall
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=1501167013-32032-2-git-send-email-andrii.anisov@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=iurii.konovalenko@globallogic.com \
--cc=iurii.mykhalskyi@globallogic.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).