From: Ivan Mikhaylov <ivan@de.ibm.com>
To: Alistair Popple <alistair@popple.id.au>,
Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Joel Stanley <joel@ozlabs.au.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH 0/4] Support for the FSP2 476fpe board in arch/powerpc
Date: Mon, 15 May 2017 16:07:50 +0300 [thread overview]
Message-ID: <20170515130754.59363-1-ivan@de.ibm.com> (raw)
This adds support for the FSP2 (476fpe) board. This includes code in
arch/powerpc/platforms/44x for board initialization. Only uImage is
supported by now. Also there was some problem with whole watchdog TCR
rewrite which causing unexpected very early panic and fixed by 4 patch.
dts and defconfig for common usage included as well. Tested on FSP2 board
with uboot and initramfs image.
Ivan Mikhaylov (4):
arch/powerpc/44x/fsp2: platform support for fsp2(476fpe) board
arch/powerpc/44x/fsp2: add device tree for fsp2 board
arch/powerpc/44x/fsp2: add defconfig for fsp2 board
arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite
arch/powerpc/boot/dts/fsp2.dts | 608 +++++++++++++++++++++++++++++++
arch/powerpc/configs/44x/fsp2_defconfig | 126 +++++++
arch/powerpc/kernel/time.c | 16 +
arch/powerpc/platforms/44x/Kconfig | 12 +
arch/powerpc/platforms/44x/Makefile | 1 +
arch/powerpc/platforms/44x/fsp2.c | 62 ++++
6 files changed, 825 insertions(+), 0 deletions(-)
create mode 100644 arch/powerpc/boot/dts/fsp2.dts
create mode 100644 arch/powerpc/configs/44x/fsp2_defconfig
create mode 100644 arch/powerpc/platforms/44x/fsp2.c
next reply other threads:[~2017-05-15 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 13:07 Ivan Mikhaylov [this message]
2017-05-16 1:53 ` Joel Stanley
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=20170515130754.59363-1-ivan@de.ibm.com \
--to=ivan@de.ibm.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=joel@ozlabs.au.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®