From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: broonie@kernel.org, andi.shyti@kernel.org, semen.protsenko@linaro.org
Cc: krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andre.draszik@linaro.org,
peter.griffin@linaro.org, kernel-team@android.com,
willmcvicker@google.com, Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH v4 10/16] spi: s3c64xx: propagate the dma_submit_error() error code
Date: Mon, 5 Feb 2024 12:45:07 +0000 [thread overview]
Message-ID: <20240205124513.447875-11-tudor.ambarus@linaro.org> (raw)
In-Reply-To: <20240205124513.447875-1-tudor.ambarus@linaro.org>
DMA submit should just add the dma descriptor to a queue, without firing
it. EIO is misleading and hides what happens in DMA. Propagate the
dma_submit_error() error code, don't overwrite it.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
drivers/spi/spi-s3c64xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
index 43b9792988b6..7a37f5d0abd9 100644
--- a/drivers/spi/spi-s3c64xx.c
+++ b/drivers/spi/spi-s3c64xx.c
@@ -321,7 +321,7 @@ static int prepare_dma(struct s3c64xx_spi_dma_data *dma,
ret = dma_submit_error(dma->cookie);
if (ret) {
dev_err(&sdd->pdev->dev, "DMA submission failed");
- return -EIO;
+ return ret;
}
dma_async_issue_pending(dma->ch);
--
2.43.0.594.gd9cf4e227d-goog
WARNING: multiple messages have this Message-ID (diff)
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: broonie@kernel.org, andi.shyti@kernel.org, semen.protsenko@linaro.org
Cc: krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andre.draszik@linaro.org,
peter.griffin@linaro.org, kernel-team@android.com,
willmcvicker@google.com, Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH v4 10/16] spi: s3c64xx: propagate the dma_submit_error() error code
Date: Mon, 5 Feb 2024 12:45:07 +0000 [thread overview]
Message-ID: <20240205124513.447875-11-tudor.ambarus@linaro.org> (raw)
In-Reply-To: <20240205124513.447875-1-tudor.ambarus@linaro.org>
DMA submit should just add the dma descriptor to a queue, without firing
it. EIO is misleading and hides what happens in DMA. Propagate the
dma_submit_error() error code, don't overwrite it.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
drivers/spi/spi-s3c64xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
index 43b9792988b6..7a37f5d0abd9 100644
--- a/drivers/spi/spi-s3c64xx.c
+++ b/drivers/spi/spi-s3c64xx.c
@@ -321,7 +321,7 @@ static int prepare_dma(struct s3c64xx_spi_dma_data *dma,
ret = dma_submit_error(dma->cookie);
if (ret) {
dev_err(&sdd->pdev->dev, "DMA submission failed");
- return -EIO;
+ return ret;
}
dma_async_issue_pending(dma->ch);
--
2.43.0.594.gd9cf4e227d-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-05 12:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 12:44 [PATCH v4 00/16] spi: s3c64xx: straightforward cleanup Tudor Ambarus
2024-02-05 12:44 ` Tudor Ambarus
2024-02-05 12:44 ` [PATCH v4 01/16] spi: s3c64xx: explicitly include <linux/io.h> Tudor Ambarus
2024-02-05 12:44 ` Tudor Ambarus
2024-02-05 15:24 ` Peter Griffin
2024-02-05 15:24 ` Peter Griffin
2024-02-05 12:44 ` [PATCH v4 02/16] spi: s3c64xx: explicitly include <linux/bits.h> Tudor Ambarus
2024-02-05 12:44 ` Tudor Ambarus
2024-02-05 15:25 ` Peter Griffin
2024-02-05 15:25 ` Peter Griffin
2024-02-05 12:45 ` [PATCH v4 03/16] spi: s3c64xx: avoid possible negative array index Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 15:26 ` Peter Griffin
2024-02-05 15:26 ` Peter Griffin
2024-02-05 12:45 ` [PATCH v4 04/16] spi: s3c64xx: fix typo, s/configuartion/configuration Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 05/16] spi: s3c64xx: sort headers alphabetically Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 15:28 ` Peter Griffin
2024-02-05 15:28 ` Peter Griffin
2024-02-05 12:45 ` [PATCH v4 06/16] spi: s3c64xx: remove unneeded (void *) casts in of_match_table Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 15:53 ` Sam Protsenko
2024-02-05 15:53 ` Sam Protsenko
2024-02-05 12:45 ` [PATCH v4 07/16] spi: s3c64xx: remove else after return Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 08/16] spi: s3c64xx: move common code outside if else Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 09/16] spi: s3c64xx: check return code of dmaengine_slave_config() Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus [this message]
2024-02-05 12:45 ` [PATCH v4 10/16] spi: s3c64xx: propagate the dma_submit_error() error code Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 11/16] spi: s3c64xx: rename prepare_dma() to s3c64xx_prepare_dma() Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 12/16] spi: s3c64xx: return ETIMEDOUT for wait_for_completion_timeout() Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 13/16] spi: s3c64xx: drop blank line between declarations Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 14/16] spi: s3c64xx: downgrade dev_warn to dev_dbg for optional dt props Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 15/16] spi: s3c64xx: remove duplicated definition Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-05 12:45 ` [PATCH v4 16/16] spi: s3c64xx: drop a superfluous bitwise NOT operation Tudor Ambarus
2024-02-05 12:45 ` Tudor Ambarus
2024-02-07 7:52 ` [PATCH v4 00/16] spi: s3c64xx: straightforward cleanup Tudor Ambarus
2024-02-07 7:52 ` 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=20240205124513.447875-11-tudor.ambarus@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=semen.protsenko@linaro.org \
--cc=willmcvicker@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.