public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <Eugen.Hristev@microchip.com>, <jic23@kernel.org>
Cc: <vkoul@kernel.org>, <Ludovic.Desroches@microchip.com>,
	<linux-iio@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: at91: Use dma_request_chan() instead dma_request_slave_channel()
Date: Tue, 17 Dec 2019 12:32:43 +0200	[thread overview]
Message-ID: <d4885bc6-4e3b-42ee-1cf6-c782fa70d3cb@ti.com> (raw)
In-Reply-To: <102e71da-8b9c-8528-3bec-b4a22895fb44@microchip.com>

Hi Eugen,

On 17/12/2019 9.59, Eugen.Hristev@microchip.com wrote:
> 
> 
> On 17.12.2019 09:50, Peter Ujfalusi wrote:
> 
>> dma_request_slave_channel() is a wrapper on top of dma_request_chan()
>> eating up the error code.
>>
>> By using dma_request_chan() directly the driver can support deferred
>> probing against DMA.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> ---
>>   drivers/iio/adc/at91-sama5d2_adc.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> Hi Peter,
> 
> Thank you for the patch.
> Nitpick : at91 is another driver (old one for different platforms), so 
> can you please change the commit oneline to iio: adc: at91-sama5d2_adc: 
> to not be confused about which driver is affected.

Sorry, just sent v2 with the correct subject prefix.
By mistake I looked at the git log of at91_adc.c and picked the wrong
prefix.

> 
> Thanks !
> Eugen
> 
>>
>> diff --git a/drivers/iio/adc/at91-sama5d2_adc.c b/drivers/iio/adc/at91-sama5d2_adc.c
>> index e1850f3d5cf3..a5c7771227d5 100644
>> --- a/drivers/iio/adc/at91-sama5d2_adc.c
>> +++ b/drivers/iio/adc/at91-sama5d2_adc.c
>> @@ -1444,10 +1444,10 @@ static void at91_adc_dma_init(struct platform_device *pdev)
>>          if (st->dma_st.dma_chan)
>>                  return;
>>
>> -       st->dma_st.dma_chan = dma_request_slave_channel(&pdev->dev, "rx");
>> -
>> -       if (!st->dma_st.dma_chan)  {
>> +       st->dma_st.dma_chan = dma_request_chan(&pdev->dev, "rx");
>> +       if (IS_ERR(st->dma_st.dma_chan))  {
>>                  dev_info(&pdev->dev, "can't get DMA channel\n");
>> +               st->dma_st.dma_chan = NULL;
>>                  goto dma_exit;
>>          }
>>
>> --
>> Peter
>>
>> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
>> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>>

- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

      reply	other threads:[~2019-12-17 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  7:50 [PATCH] iio: adc: at91: Use dma_request_chan() instead dma_request_slave_channel() Peter Ujfalusi
2019-12-17  7:59 ` Eugen.Hristev
2019-12-17 10:32   ` Peter Ujfalusi [this message]

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=d4885bc6-4e3b-42ee-1cf6-c782fa70d3cb@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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