From: Ivan Bornyakov <i.bornyakov@metrotek.ru>
To: "Conor Dooley" <conor.dooley@microchip.com>,
"Moritz Fischer" <mdf@kernel.org>, "Wu Hao" <hao.wu@intel.com>,
"Xu Yilun" <yilun.xu@intel.com>, "Tom Rix" <trix@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Ivan Bornyakov <i.bornyakov@metrotek.ru>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
system@metrotek.ru
Subject: [PATCH v3 0/3] Reliability improvements for Microchip MPF FPGA manager
Date: Tue, 27 Dec 2022 13:04:47 +0300 [thread overview]
Message-ID: <20221227100450.2257-1-i.bornyakov@metrotek.ru> (raw)
A couple of reliability improvements for Microchip Polarfire FPGA
manager:
* move SPI I/O buffers out of stack
* rewrite status polling routine in a time measurable way
Also improve mpf_ops_write() code readability by separating single data
frame writing routine.
ChangeLog:
v1:
[https://lore.kernel.org/linux-fpga/20221223123854.8023-1-i.bornyakov@metrotek.ru/]
v2:
* split into 3 distinct patches
[https://lore.kernel.org/linux-fpga/20221226142326.8111-1-i.bornyakov@metrotek.ru/]
v3:
* fix polling stop condition in mpf_poll_status() as Ilpo suggested.
Ivan Bornyakov (3):
fpga: microchip-spi: move SPI I/O buffers out of stack
fpga: microchip-spi: rewrite status polling in a time measurable way
fpga: microchip-spi: separate data frame write routine
drivers/fpga/microchip-spi.c | 137 ++++++++++++++++++-----------------
1 file changed, 72 insertions(+), 65 deletions(-)
--
2.38.2
next reply other threads:[~2022-12-27 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 10:04 Ivan Bornyakov [this message]
2022-12-27 10:04 ` [PATCH v3 1/3] fpga: microchip-spi: move SPI I/O buffers out of stack Ivan Bornyakov
2022-12-28 14:42 ` Conor Dooley
2022-12-27 10:04 ` [PATCH v3 2/3] fpga: microchip-spi: rewrite status polling in a time measurable way Ivan Bornyakov
2022-12-27 10:22 ` Ilpo Järvinen
2022-12-28 14:50 ` Conor Dooley
2022-12-27 10:04 ` [PATCH v3 3/3] fpga: microchip-spi: separate data frame write routine Ivan Bornyakov
2022-12-28 14:54 ` Conor Dooley
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=20221227100450.2257-1-i.bornyakov@metrotek.ru \
--to=i.bornyakov@metrotek.ru \
--cc=conor.dooley@microchip.com \
--cc=hao.wu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=system@metrotek.ru \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/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).