From: <Tudor.Ambarus@microchip.com>
To: <gregkh@linuxfoundation.org>
Cc: <richard.genoud@gmail.com>, <jirislaby@kernel.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <linux-serial@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: serial: atmel: Check return code of dmaengine_submit()
Date: Tue, 16 Nov 2021 06:14:23 +0000 [thread overview]
Message-ID: <1910ee9a-19f8-e155-9cc9-4a67412f3402@microchip.com> (raw)
In-Reply-To: <YZKDmb/ZlYwtyX8j@kroah.com>
On 11/15/21 5:58 PM, Greg KH wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Mon, Nov 15, 2021 at 04:30:04PM +0200, Tudor Ambarus wrote:
>> dma_cookie_t < 0 indicates an error code, check for it.
>
> Very odd changelog text, please be more descriptive about what is
> happening here.
>
The tx_submit() method of struct dma_async_tx_descriptor is entitled to do
sanity checks and return errors if encountered. It's not the case for the
DMA controller drivers that this client is using (at_h/xdmac), because they
currently don't do sanity checks and always return a positive cookie at
tx_submit() method. In case the controller drivers will implement sanity
checks and return errors, print a message so that the client will be informed
that something went wrong at tx_submit() level.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>> ---
>> drivers/tty/serial/atmel_serial.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
>> index 2c99a47a2535..376f7a9c2868 100644
>> --- a/drivers/tty/serial/atmel_serial.c
>> +++ b/drivers/tty/serial/atmel_serial.c
>> @@ -1004,6 +1004,11 @@ static void atmel_tx_dma(struct uart_port *port)
>> desc->callback = atmel_complete_tx_dma;
>> desc->callback_param = atmel_port;
>> atmel_port->cookie_tx = dmaengine_submit(desc);
>> + if (dma_submit_error(atmel_port->cookie_tx)) {
>> + dev_err(port->dev, "dma_submit_error %d\n",
>> + atmel_port->cookie_tx);
>> + return;
>
> What can a user do with this error message?
>
will be informed that something went wrong at tx_submit() level.
> Have you seen this happen in real life?
No. I debugged a locking problem and I observed that dma_submit_error() is not called,
so I thought to update this.
>
> What commit does this "fix"?
This is rather an improvement, but if you're looking for a fixes tag, I think
we can use:
Fixes: 08f738be88bb ("serial: at91: add tx dma support")
I'll send a v2 as part of a bigger series. If you find this patch does not worth it,
I can as well drop it.
Cheers,
ta
next prev parent reply other threads:[~2021-11-16 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 14:30 [PATCH] tty: serial: atmel: Check return code of dmaengine_submit() Tudor Ambarus
2021-11-15 15:58 ` Greg KH
2021-11-16 6:14 ` Tudor.Ambarus [this message]
2021-11-16 8:26 ` Greg KH
2021-11-16 11:33 ` 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=1910ee9a-19f8-e155-9cc9-4a67412f3402@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=richard.genoud@gmail.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