From: Raju Rangoju <Raju.Rangoju@amd.com>
To: <broonie@kernel.org>, <linux-spi@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <sanju.mehta@amd.com>,
<krishnamoorthi.m@amd.com>, <akshata.mukundshetty@amd.com>,
<Raju.Rangoju@amd.com>
Subject: [PATCH V2 0/8] spi: spi_amd: Performance Optimization Patch Series
Date: Wed, 25 Sep 2024 19:06:36 +0530 [thread overview]
Message-ID: <20240925133644.2922359-1-Raju.Rangoju@amd.com> (raw)
AMD SPI controller’s index mode performance is constrained by the
hardware limitation of the FIFO queue length. This patch series introduces
optimizations to the spi_amd driver, aiming to maximize throughput and
enhance overall performance. The changes includes,
- Enable SPI dual and quad I/O modes and update SPI-MEM support function to
reflect AMD SPI0 hardware capabilities.
- Utilize efficient kernel APIs to streamline SPI I/O operations for
enhanced performance.
- Refine the set tx/rx count functions to optimize SPI I/O throughput.
- Minimize the number of data read calls by efficiently retrieving data
from FIFO queues, improving SPI I/O efficiency.
- Add changes to support AMD HID2 SPI controller and update SPI-MEM support
function to reflect AMD HID2 hardware capabilities.
- Add changes to set SPI controller address mode before initiating the
commands
- Add changes to implement HIDDMA read operation support for HID2 SPI
controller
V1->V2:
-------
- Eliminate the separate patch that introduces SPI-MEM support function
modifications, and incorporate those changes into the existing patches
for enabling dual and quad I/O modes, as well as enhance support for the
HID2 SPI controller.
Raju Rangoju (8):
spi: spi_amd: Sort headers alphabetically
spi: spi_amd: Enable dual and quad I/O modes
spi: spi_amd: Replace ioread/iowrite calls
spi: spi_amd: Updates to set tx/rx count functions
spi: spi_amd: Optimize IO operations
spi: spi_amd: Add support for HID2 SPI controller
spi: spi_amd: Set controller address mode
spi: spi_amd: Add HIDDMA basic read support
drivers/spi/spi-amd.c | 325 ++++++++++++++++++++++++++++++++++++++----
1 file changed, 295 insertions(+), 30 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-25 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 13:36 Raju Rangoju [this message]
2024-09-25 13:36 ` [PATCH V2 1/8] spi: spi_amd: Sort headers alphabetically Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 2/8] spi: spi_amd: Enable dual and quad I/O modes Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 3/8] spi: spi_amd: Replace ioread/iowrite calls Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 4/8] spi: spi_amd: Updates to set tx/rx count functions Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 5/8] spi: spi_amd: Optimize IO operations Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 6/8] spi: spi_amd: Add support for HID2 SPI controller Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 7/8] spi: spi_amd: Set controller address mode Raju Rangoju
2024-09-25 13:36 ` [PATCH V2 8/8] spi: spi_amd: Add HIDDMA basic read support Raju Rangoju
2024-09-30 23:51 ` [PATCH V2 0/8] spi: spi_amd: Performance Optimization Patch Series Mark Brown
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=20240925133644.2922359-1-Raju.Rangoju@amd.com \
--to=raju.rangoju@amd.com \
--cc=akshata.mukundshetty@amd.com \
--cc=broonie@kernel.org \
--cc=krishnamoorthi.m@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sanju.mehta@amd.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