public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhavya Kapoor <b-kapoor@ti.com>
To: Wadim Egorov <w.egorov@phytec.de>, Jonathan Cameron <jic23@kernel.org>
Cc: <lars@metafoo.de>, <robh@kernel.org>, <heiko@sntech.de>,
	<peter.ujfalusi@ti.com>, <mugunthanvnm@ti.com>,
	<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<nm@ti.com>, <upstream@lists.phytec.de>
Subject: Re: [PATCH v2] iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma()
Date: Mon, 27 Nov 2023 15:14:29 +0530	[thread overview]
Message-ID: <0c26613b-4aba-4e1e-bf0e-57feff23e303@ti.com> (raw)
In-Reply-To: <a58ae80e-e281-425a-9b72-bad8fd305e6a@phytec.de>

LGTM !!🙂

On 24/11/23 5:41 pm, Wadim Egorov wrote:
>
> Am 05.10.23 um 16:09 schrieb Jonathan Cameron:
>> On Mon, 25 Sep 2023 15:44:27 +0200
>> Wadim Egorov <w.egorov@phytec.de> wrote:
>>
>>> Fix wrong handling of a DMA request where the probing only failed
>>> if -EPROPE_DEFER was returned. Instead, let us fail if a non -ENODEV
>>> value is returned. This makes DMAs explicitly optional. Even if the
>>> DMA request is unsuccessfully, the ADC can still work properly.
>>> We do also handle the defer probe case by making use of 
>>> dev_err_probe().
>>>
>>> Fixes: f438b9da75eb ("drivers: iio: ti_am335x_adc: add dma support")
>>> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
Reviewed-by: Bhavya Kapoor <b-kapoor@ti.com>
>> +CC Bhavya,
>>
>> Could you take a look at this given you had comments on v1.
>
> Bhavya, any comments on this?
> If not, is there anything else that is blocking this patch?
>
> Regards,
> Wadim
>
>>
>> Thanks,
>>
>> Jonathan
>>
>>> ---
>>> v2:
>>>    - Update description
>>>    - Drop line break after Fixes tag
>>>    - Move decision about optional DMA into probe/caller
>>> ---
>>>   drivers/iio/adc/ti_am335x_adc.c | 4 +++-
>>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/iio/adc/ti_am335x_adc.c 
>>> b/drivers/iio/adc/ti_am335x_adc.c
>>> index 8db7a01cb5fb..5f8795986995 100644
>>> --- a/drivers/iio/adc/ti_am335x_adc.c
>>> +++ b/drivers/iio/adc/ti_am335x_adc.c
>>> @@ -670,8 +670,10 @@ static int tiadc_probe(struct platform_device 
>>> *pdev)
>>>       platform_set_drvdata(pdev, indio_dev);
>>>         err = tiadc_request_dma(pdev, adc_dev);
>>> -    if (err && err == -EPROBE_DEFER)
>>> +    if (err && err != -ENODEV) {
>>> +        dev_err_probe(&pdev->dev, err, "DMA request failed\n");
>>>           goto err_dma;
>>> +    }
>>>         return 0;

  reply	other threads:[~2023-11-27  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 13:44 [PATCH v2] iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() Wadim Egorov
2023-10-05 14:09 ` Jonathan Cameron
2023-11-24 12:11   ` Wadim Egorov
2023-11-27  9:44     ` Bhavya Kapoor [this message]
2023-12-04  9:33       ` Jonathan Cameron
2023-11-27  9:40   ` Bhavya Kapoor

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=0c26613b-4aba-4e1e-bf0e-57feff23e303@ti.com \
    --to=b-kapoor@ti.com \
    --cc=heiko@sntech.de \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh@kernel.org \
    --cc=upstream@lists.phytec.de \
    --cc=w.egorov@phytec.de \
    /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