From: Joel Stanley <joel@jms.id.au>
To: Rob Herring <robh+dt@kernel.org>,
Andrew Jeffery <andrew@aj.id.au>, Jeremy Kerr <jk@ozlabs.org>,
Alistar Popple <alistair@popple.id.au>,
Eddie James <eajames@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
devicetree@vger.kernel.org, linux-fsi@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] fsi: Add AST2600 FSI master
Date: Fri, 1 Nov 2019 21:59:02 +1030 [thread overview]
Message-ID: <20191101112905.7282-2-joel@jms.id.au> (raw)
In-Reply-To: <20191101112905.7282-1-joel@jms.id.au>
This adds support for the FSI master included in the ASPEED AST2600 BMC
SoC.
The driver has been tested on hardware for most operations. Future
enhancements include robust error recovery, DMA support and interrupt
support.
This patch doesn't include Andrew's endian fix from today, but we can
merge that as a follow up.
Please review!
Joel Stanley (3):
dt-bindings: fsi: Add description of FSI master
fsi: Add ast2600 master driver
fsi: aspeed: Add trace points
.../bindings/fsi/fsi-master-aspeed.txt | 24 +
drivers/fsi/Kconfig | 6 +
drivers/fsi/Makefile | 1 +
drivers/fsi/fsi-master-aspeed.c | 550 ++++++++++++++++++
include/trace/events/fsi_master_aspeed.h | 77 +++
5 files changed, 658 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/fsi-master-aspeed.txt
create mode 100644 drivers/fsi/fsi-master-aspeed.c
create mode 100644 include/trace/events/fsi_master_aspeed.h
--
2.24.0.rc1
next prev parent reply other threads:[~2019-11-01 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 11:29 [PATCH 0/3] fsi: Add AST2600 FSI master Joel Stanley
2019-11-01 11:29 ` Joel Stanley [this message]
2019-11-01 11:29 ` [PATCH 1/3] dt-bindings: fsi: Add description of " Joel Stanley
2019-11-27 23:30 ` Andrew Jeffery
2019-11-01 11:29 ` [PATCH 2/3] fsi: Add ast2600 master driver Joel Stanley
2019-11-01 11:29 ` [PATCH 3/3] fsi: aspeed: Add trace points 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=20191101112905.7282-2-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.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).