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@jms.id.au>, Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH 0/4] fsp2 low level setup
Date: Thu, 2 Nov 2017 16:07:02 +0300 [thread overview]
Message-ID: <20171102130706.76056-1-ivan@de.ibm.com> (raw)
fsp2 board setup with l2 setup and irq handlers
for some critical exceptions.
Ivan Mikhaylov (4):
44x/fsp2: add fsp2 headers
44x/fsp2: l2 setup with error clear
44x/fsp2: tvsense workaround for dd1
44x/fsp2: add irq error handlers
arch/powerpc/include/asm/fsp2_reg.h | 272 +++++++++++++++++++++++++++++++++++
arch/powerpc/platforms/44x/fsp2.c | 254 +++++++++++++++++++++++++++++++++-
2 files changed, 529 insertions(+), 1 deletions(-)
create mode 100644 arch/powerpc/include/asm/fsp2_reg.h
reply other threads:[~2017-11-02 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171102130706.76056-1-ivan@de.ibm.com \
--to=ivan@de.ibm.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=joel@jms.id.au \
--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;
as well as URLs for NNTP newsgroup(s).