From: Jaewon Kim <jaewon02.kim@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andi Shyti <andi@etezian.org>, Mark Brown <broonie@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Chanho Park" <chanho61.park@samsung.com>,
"Łukasz Stelmach" <l.stelmach@samsung.com>
Subject: Re: [PATCH v3 3/3] spi: s3c64xx: support interrupt based pio mode
Date: Wed, 10 May 2023 13:05:21 +0900 [thread overview]
Message-ID: <0ef75bd7-e7e6-a806-2c3f-35c7312c391d@samsung.com> (raw)
In-Reply-To: <d8fa2d7b-6604-1fad-6b0b-19d7e551a1d2@samsung.com>
Hello Marek
On 23. 5. 9. 22:03, Marek Szyprowski wrote:
> On 02.05.2023 08:28, Jaewon Kim wrote:
>> Support interrupt based pio mode to optimize cpu usage.
>> When transmitting data size is larget than 32 bytes, operates with
>> interrupt based pio mode.
>>
>> By using the FIFORDY INT, an interrupt can be triggered when
>> the desired size of data has been received. Using this, we can support
>> interrupt based pio mode.
>>
>> Signed-off-by: Jaewon Kim <jaewon02.kim@samsung.com>
> This patch landed recently in linux-next as commit 1ee806718d5e ("spi:
> s3c64xx: support interrupt based pio mode"). Unfortunately it breaks
> ethernet chip operation on Exynos3250 based Artik5 Development board. I
> see the flood of the following messages:
>
> [ 36.097739] ax88796c spi0.0: I/O Error: rx-1 tx-0 rx-f tx-p len-496
> dma-1 res-(-5)
> [ 36.100877] ax88796c spi0.0: RX residue: 248
> [ 36.101383] ax88796c spi0.0: SPI transfer failed: -5
> [ 36.101939] spi_master spi0: failed to transfer one message from queue
> [ 36.102439] ax88796c spi0.0: axspi_read_rxq() failed: ret = -5
> [ 36.107830] s3c64xx-spi 13920000.spi: Failed to get RX DMA channel
> [ 36.148875] ax88796c spi0.0: I/O Error: rx-0 tx-1 rx-p tx-f len-4
> dma-0 res-(-5)
> [ 36.149517] ax88796c spi0.0: SPI transfer failed: -5
> [ 36.150053] spi_master spi0: failed to transfer one message from queue
> [ 36.150562] ax88796c spi0.0: axspi_read_reg() failed: ret = -5
> [ 36.152175] s3c64xx-spi 13920000.spi: Failed to get RX DMA channel
> [ 36.191651] ax88796c spi0.0: I/O Error: rx-0 tx-1 rx-p tx-f len-4
> dma-0 res-(-5)
> [ 36.192268] ax88796c spi0.0: SPI transfer failed: -5
>
> ...
>
> I didn't analyze the details, but imho it looks like some kind of
> mishandling of the corner case or switching between PIO and DMA mode. I
> will check the details later.
>
>
> Best regards
Thanks for testing the various cases.
The problem occurred when DMA mode and IRQ mode were enabled at the same
time.
In the above case, BUS_WIDTH register invaded.
Because, target length 496 were written to RX_RDY_LVL, but it exceeded
6-bits.
Could you test with below code??? If the problem is solved, I will send
a fix patch as soon as possible.
-----------------------------
diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
index 238db29fc93b..a72e11e965c3 100644
--- a/drivers/spi/spi-s3c64xx.c
+++ b/drivers/spi/spi-s3c64xx.c
@@ -782,7 +782,7 @@ static int s3c64xx_spi_transfer_one(struct
spi_master *master,
do {
/* transfer size is greater than 32, change to IRQ mode */
- if (xfer->len > S3C64XX_SPI_POLLING_SIZE)
+ if (!use_dma && (xfer->len > S3C64XX_SPI_POLLING_SIZE))
use_irq = true;
if (use_irq) {
-----------------------------
Best regards
Jaewon Kim
next prev parent reply other threads:[~2023-05-10 4:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230502065025epcas2p16f5a02e6990d6f2b2257f001979ebcf9@epcas2p1.samsung.com>
2023-05-02 6:28 ` [PATCH v3 0/3] Improve polling mode of s3c64xx driver Jaewon Kim
2023-05-02 6:28 ` [PATCH v3 1/3] spi: s3c64xx: change polling mode to optional Jaewon Kim
2023-05-05 9:09 ` Krzysztof Kozlowski
2023-05-02 6:28 ` [PATCH v3 2/3] spi: s3c64xx: add sleep during transfer Jaewon Kim
2023-05-05 9:09 ` Krzysztof Kozlowski
2023-05-02 6:28 ` [PATCH v3 3/3] spi: s3c64xx: support interrupt based pio mode Jaewon Kim
2023-05-05 9:47 ` Krzysztof Kozlowski
2023-05-08 1:42 ` Jaewon Kim
2023-05-09 13:03 ` Marek Szyprowski
2023-05-10 4:05 ` Jaewon Kim [this message]
2023-05-10 6:54 ` Marek Szyprowski
2023-05-08 13:27 ` [PATCH v3 0/3] Improve polling mode of s3c64xx driver Mark Brown
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=0ef75bd7-e7e6-a806-2c3f-35c7312c391d@samsung.com \
--to=jaewon02.kim@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=chanho61.park@samsung.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=l.stelmach@samsung.com \
--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=m.szyprowski@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox