From: Peter Ujfalusi <peter.ujfalusi@gmail.com>
To: vkoul@kernel.org
Cc: dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, vigneshr@ti.com,
grygorii.strashko@ti.com, kishon@ti.com
Subject: [PATCH v2 1/3] dmaengine: Extend the dmaengine_alignment for 128 and 256 bytes
Date: Wed, 13 Jan 2021 13:49:21 +0200 [thread overview]
Message-ID: <20210113114923.9231-2-peter.ujfalusi@gmail.com> (raw)
In-Reply-To: <20210113114923.9231-1-peter.ujfalusi@gmail.com>
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
Some DMA device can benefit with higher order of alignment than the maximum
of 64 bytes currently defined.
Define 128 and 256 bytes alignment for these devices.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
Tested-by: Kishon Vijay Abraham I <kishon@ti.com>
---
include/linux/dmaengine.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 68130f5f599e..004736b6a9c8 100644
--- a/include/linux/dmaengine.h
+++ b/include/linux/dmaengine.h
@@ -745,6 +745,8 @@ enum dmaengine_alignment {
DMAENGINE_ALIGN_16_BYTES = 4,
DMAENGINE_ALIGN_32_BYTES = 5,
DMAENGINE_ALIGN_64_BYTES = 6,
+ DMAENGINE_ALIGN_128_BYTES = 7,
+ DMAENGINE_ALIGN_256_BYTES = 8,
};
/**
--
2.30.0
next prev parent reply other threads:[~2021-01-13 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 11:49 [PATCH v2 0/3] dmaengine: ti: k3-udma: memcpy throughput improvement Peter Ujfalusi
2021-01-13 11:49 ` Peter Ujfalusi [this message]
2021-01-13 11:49 ` [PATCH v2 2/3] dmaengine: ti: k3-udma: Add support for burst_size configuration for mem2mem Peter Ujfalusi
2021-01-13 11:49 ` [PATCH v2 3/3] dmaengine: ti: k3-udma: Do not initialize ret in tisci channel config functions Peter Ujfalusi
2021-01-13 16:30 ` [PATCH v2 0/3] dmaengine: ti: k3-udma: memcpy throughput improvement Vinod Koul
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=20210113114923.9231-2-peter.ujfalusi@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).