From: <Dan.Sneddon@microchip.com>
To: <villeb@bytesnap.co.uk>, <Tudor.Ambarus@microchip.com>,
<broonie@kernel.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>
Cc: <linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] spi: atmel: Fix PDC transfer setup bug
Date: Fri, 1 Oct 2021 21:12:45 +0000 [thread overview]
Message-ID: <e151c019-269a-8dbb-610b-2a57cc855e1b@microchip.com> (raw)
In-Reply-To: <20210921072132.21831-1-villeb@bytesnap.co.uk>
Hi Ville,
On 9/21/21 12:21 AM, Ville Baillie wrote:
> Commit 5fa5e6dec762 ("spi: atmel: Switch to transfer_one transfer
> method") refactored the code and changed a conditional causing
> atmel_spi_dma_map_xfer to never be called in PDC mode. This causes the
> driver to silently fail.
>
> This patch changes the conditional to match the behaviour of the
> previous commit before the refactor.
>
> Signed-off-by: Ville Baillie <villeb@bytesnap.co.uk>
Shouldn't this have a FIXES tag?
> ---
> drivers/spi/spi-atmel.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi-atmel.c b/drivers/spi/spi-atmel.c
> index 788dcdf25f00..f872cf196c2f 100644
> --- a/drivers/spi/spi-atmel.c
> +++ b/drivers/spi/spi-atmel.c
> @@ -1301,7 +1301,7 @@ static int atmel_spi_one_transfer(struct spi_master *master,
> * DMA map early, for performance (empties dcache ASAP) and
> * better fault reporting.
> */
> - if ((!master->cur_msg_mapped)
> + if ((!master->cur_msg->is_dma_mapped)
> && as->use_pdc) {
> if (atmel_spi_dma_map_xfer(as, xfer) < 0)
> return -ENOMEM;
> @@ -1381,7 +1381,7 @@ static int atmel_spi_one_transfer(struct spi_master *master,
> }
> }
>
> - if (!master->cur_msg_mapped
> + if (!master->cur_msg->is_dma_mapped
> && as->use_pdc)
> atmel_spi_dma_unmap_xfer(master, xfer);
>
>
Regards,
Dan
next prev parent reply other threads:[~2021-10-01 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 7:21 Ville Baillie
2021-10-01 21:12 ` Dan.Sneddon [this message]
2021-10-02 0:16 ` 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=e151c019-269a-8dbb-610b-2a57cc855e1b@microchip.com \
--to=dan.sneddon@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=villeb@bytesnap.co.uk \
/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
Powered by JetHome