From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: openbmc@lists.ozlabs.org
Cc: linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [RFC PATCH 00/14] fsi: Fixes and Coldfire coprocessor offload
Date: Fri, 22 Jun 2018 14:31:20 +1000 [thread overview]
Message-ID: <20180622043134.18238-1-benh@kernel.crashing.org> (raw)
This series implements support for offloading the FSI protocol bitbanging
to the ColdFire secondary core of the Aspeed SoCs. The result increases
FSI performance by a factor of 4, and on systems that don't support async
FSI clock, provide much more regular and continuous clocking which helps
reliability.
Patch 1 may go a different route and was already posted a few weeks ago,
I included it for completeness.
Patches 2..9 add some infrastructure to the FSI core to control some
of the FSI protocol delays and adjustements/fixes to the existing GPIO
bitbanging master. They are "mechanical" dependencies
Patch 10 moves some protocol definitions to a common place where the
new master driver can find them
Patch 11 is the DT binding for the new driver with comes with patch 12
Finally patch 13 and 14 update the Romulus and Palmetto board device-trees
to use the new driver.
There's another dependency on the Aspeed GPIO driver changes for handling
with GPIO lines ownership and handshaking. The patches have been submitted
and can be found for reference there:
https://github.com/ozbenh/linux-ast/commits/gpio
Finally, the driver needs a machine specific firmware file. The firwmare
is open source and available at:
https://github.com/ozbenh/cf-fsi
I will submit it to linux-firmware if there's enough popular demand ;-)
next reply other threads:[~2018-06-22 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 4:31 Benjamin Herrenschmidt [this message]
2018-06-22 4:31 ` [RFC PATCH 01/14] devres: Add devm_of_iomap() Benjamin Herrenschmidt
2018-06-29 9:14 ` Linus Walleij
2018-06-29 20:27 ` Andy Shevchenko
2018-06-30 1:06 ` Benjamin Herrenschmidt
2018-06-22 4:31 ` [RFC PATCH 02/14] fsi: Move code around to avoid forward declaration Benjamin Herrenschmidt
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=20180622043134.18238-1-benh@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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).