From: Joy Chakraborty <joychakr@google.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, manugautam@google.com,
danielmentz@google.com, sjadavani@google.com,
Joy Chakraborty <joychakr@google.com>
Subject: [PATCH v2 0/6] dmaengine: pl330: Updates and logical changes for peripheral usecases
Date: Fri, 12 May 2023 14:14:39 +0000 [thread overview]
Message-ID: <20230512141445.2026660-1-joychakr@google.com> (raw)
This patch series makes some initial minor and cosmetic changes:
-Add variables and logic to handle separate source and destination
AxSize and AxLen.
-Use __ffs to calculate AxSize for consistency in the driver
-Use switch-case in prep_slave_sg() for consistency
-Change args get_burst_len() to remove redundant "len" and add
burst_size so that it can be used in multiple places.
to majorly enable addition of 2 logical changes in the last 2 patches:
-Allow transactions towards memory to use the maximum possible
bus width (AxSize) during a memory to peripheral dma usage or
vise-versa.
-Add logic to copy left over data after executing bursts to
the peripheral in singles instead of bursts.
---
V1->V2 Changes : Remove Quirk logic and update description texts.
---
Joy Chakraborty (6):
dmaengine: pl330: Separate SRC and DST burst size and len
dmaengine: pl330: Use FFS to calculate burst size
dmaengine: pl330: Change if-else to switch-case for consistency
dmaengine: pl330: Change unused arg "len" from get_burst_len()
dmaengine: pl330: Optimize AxSize for peripheral usecases
dmaengine: pl330: Use dma singles for peripheral _dregs
drivers/dma/pl330.c | 223 ++++++++++++++++++++++++++++++++++++--------
1 file changed, 185 insertions(+), 38 deletions(-)
--
2.40.1.606.ga4b1b128d6-goog
next reply other threads:[~2023-05-12 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 14:14 Joy Chakraborty [this message]
2023-05-12 14:14 ` [PATCH v2 1/6] dmaengine: pl330: Separate SRC and DST burst size and len Joy Chakraborty
2023-05-12 14:14 ` [PATCH v2 2/6] dmaengine: pl330: Use FFS to calculate burst size Joy Chakraborty
2023-05-12 14:14 ` [PATCH v2 3/6] dmaengine: pl330: Change if-else to switch-case for consistency Joy Chakraborty
2023-05-12 14:14 ` [PATCH v2 4/6] dmaengine: pl330: Change unused arg "len" from get_burst_len() Joy Chakraborty
2023-05-12 14:14 ` [PATCH v2 5/6] dmaengine: pl330: Optimize AxSize for peripheral usecases Joy Chakraborty
2023-05-12 14:14 ` [PATCH v2 6/6] dmaengine: pl330: Use dma singles for peripheral _dregs Joy Chakraborty
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=20230512141445.2026660-1-joychakr@google.com \
--to=joychakr@google.com \
--cc=danielmentz@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manugautam@google.com \
--cc=sjadavani@google.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®