From: Ben Walker <benjamin.walker@intel.com>
To: vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, ludovic.desroches@microchip.com,
okaya@kernel.org, dave.jiang@intel.com,
Ben Walker <benjamin.walker@intel.com>
Subject: [PATCH v3 0/4] dmaengine: memset clarifications and fixes
Date: Tue, 1 Mar 2022 11:25:47 -0700 [thread overview]
Message-ID: <20220301182551.883474-1-benjamin.walker@intel.com> (raw)
The following contains a clarification for the behavior of the 'value'
parameter in the memset operation. It is intended to be a single byte
pattern as laid out here:
https://lore.kernel.org/dmaengine/YejrA5ZWZ3lTRO%2F1@matsya/
Then I'm attempting to fix all places it is currently used. But note
that I do not have access to this hardware and cannot test it. We'll
really need a maintainer to take a look at each of these to verify that
the changes are correct.
v3:
- Using signed byte for pattern everywhere
Ben Walker (4):
dmaengine: Document dmaengine_prep_dma_memset
dmaengine: at_hdmac: In atc_prep_dma_memset, treat value as a single
byte
dmaengine: at_xdmac: In at_xdmac_prep_dma_memset, treat value as a
single byte
dmaengine: hidma: In hidma_prep_dma_memset treat value as a single
byte
drivers/dma/at_hdmac.c | 10 +++++++++-
drivers/dma/at_xdmac.c | 9 ++++++++-
drivers/dma/qcom/hidma.c | 13 ++++++++++++-
include/linux/dmaengine.h | 8 ++++++++
4 files changed, 37 insertions(+), 3 deletions(-)
--
2.33.1
next reply other threads:[~2022-03-01 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 18:25 Ben Walker [this message]
2022-03-01 18:25 ` [PATCH v3 1/4] dmaengine: Document dmaengine_prep_dma_memset Ben Walker
2022-03-01 18:25 ` [PATCH v3 2/4] dmaengine: at_hdmac: In atc_prep_dma_memset, treat value as a single byte Ben Walker
2022-03-01 18:25 ` [PATCH v3 3/4] dmaengine: at_xdmac: In at_xdmac_prep_dma_memset, " Ben Walker
2022-03-15 18:06 ` Tudor.Ambarus
2022-03-01 18:25 ` [PATCH v3 4/4] dmaengine: hidma: In hidma_prep_dma_memset " Ben Walker
2022-04-20 11:58 ` [PATCH v3 0/4] dmaengine: memset clarifications and fixes Vinod Koul
2022-08-02 15:53 ` Tudor.Ambarus
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=20220301182551.883474-1-benjamin.walker@intel.com \
--to=benjamin.walker@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=okaya@kernel.org \
--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).