[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180622043134.18238-1-benh@kernel.crashing.org>
Date: Fri, 22 Jun 2018 14:31:20 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: openbmc@...ts.ozlabs.org
Cc: linux-aspeed@...ts.ozlabs.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Jeffery <andrew@...id.au>
Subject: [RFC PATCH 00/14] fsi: Fixes and Coldfire coprocessor offload
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 ;-)
Powered by blists - more mailing lists