From: Rosen Penev <rosenp@gmail.com>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
linux-kernel@vger.kernel.org (open list),
linux-arm-kernel@lists.infradead.org (moderated list:ARM/STI
ARCHITECTURE)
Subject: [PATCH dmaengine 1/2] dmaengine: st_fdma: change dreg_line to long
Date: Wed, 5 Nov 2025 18:20:14 -0800 [thread overview]
Message-ID: <20251106022015.84970-2-rosenp@gmail.com> (raw)
In-Reply-To: <20251106022015.84970-1-rosenp@gmail.com>
The code is encoding a pointer into an int which works fine with a
32-bit build. Not with a 64-bit one.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/dma/st_fdma.c | 2 +-
drivers/dma/st_fdma.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/st_fdma.c b/drivers/dma/st_fdma.c
index c65ee0c7bfbd..01211090844f 100644
--- a/drivers/dma/st_fdma.c
+++ b/drivers/dma/st_fdma.c
@@ -68,7 +68,7 @@ static void st_fdma_dreq_put(struct st_fdma_chan *fchan)
{
struct st_fdma_dev *fdev = fchan->fdev;
- dev_dbg(fdev->dev, "put dreq_line:%#x\n", fchan->dreq_line);
+ dev_dbg(fdev->dev, "put dreq_line:%#lx\n", fchan->dreq_line);
clear_bit(fchan->dreq_line, &fdev->dreq_mask);
}
diff --git a/drivers/dma/st_fdma.h b/drivers/dma/st_fdma.h
index f296412e96b6..f1e746f7bc7d 100644
--- a/drivers/dma/st_fdma.h
+++ b/drivers/dma/st_fdma.h
@@ -120,7 +120,7 @@ struct st_fdma_chan {
struct dma_slave_config scfg;
struct st_fdma_cfg cfg;
- int dreq_line;
+ long dreq_line;
struct virt_dma_chan vchan;
struct st_fdma_desc *fdesc;
--
2.51.2
next prev parent reply other threads:[~2025-11-06 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 2:20 [PATCH dmaengine 0/2] dmaengine: st_fdma: support COMPILE_TEST Rosen Penev
2025-11-06 2:20 ` Rosen Penev [this message]
2025-11-06 2:20 ` [PATCH dmaengine 2/2] dmaengine: st_fdma: add COMPILE_TEST support Rosen Penev
2025-12-23 11:28 ` [PATCH dmaengine 0/2] dmaengine: st_fdma: support COMPILE_TEST 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=20251106022015.84970-2-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@foss.st.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).