Linux IIO development
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
	Jonathan Cameron <jic23@kernel.org>,
	linux-iio@vger.kernel.org
Cc: "Nuno Sá" <noname.nuno@gmail.com>,
	"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 5/8] iio: accel: kx022a: Switch to sparse friendly iio_device_claim/release_direct()
Date: Wed, 19 Feb 2025 07:36:25 +0200	[thread overview]
Message-ID: <ead33fc6-48b9-488c-8993-2ca647e59735@gmail.com> (raw)
In-Reply-To: <85d97cbe-9d34-462c-a89f-de6fc1ac6e34@baylibre.com>

On 18/02/2025 17:42, David Lechner wrote:
> On 2/18/25 1:39 AM, Matti Vaittinen wrote:
>> On 17/02/2025 16:01, Jonathan Cameron wrote:
>>> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>>
>>> These new functions allow sparse to find failures to release
>>> direct mode reducing chances of bugs over the claim_direct_mode()
>>> functions that are deprecated.
>>>
>>> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>> Cc: Matti Vaittinen <mazziesaccount@gmail.com>
>>> ---
>>>    drivers/iio/accel/kionix-kx022a.c | 14 ++++++--------
>>>    1 file changed, 6 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/drivers/iio/accel/kionix-kx022a.c b/drivers/iio/accel/kionix-kx022a.c
>>> index 727e007c5fc1..07dcf5f0599f 100644
>>> --- a/drivers/iio/accel/kionix-kx022a.c
>>> +++ b/drivers/iio/accel/kionix-kx022a.c
>>> @@ -577,13 +577,12 @@ static int kx022a_write_raw(struct iio_dev *idev,
>>>         * issues if users trust the watermark to be reached within known
>>>         * time-limit).
>>>         */
>>> -    ret = iio_device_claim_direct_mode(idev);
>>> -    if (ret)
>>> -        return ret;
>>> +    if (!iio_device_claim_direct(idev))
>>> +        return -EBUSY;
>>
>> Not really in the scope of this review - but in my opinion the logic of this check is terribly counter intuitive. I mean,
>>
>>> +    if (iio_device_claim_direct(idev))
>>> +        return -EBUSY;
> 
> I'm curious how you read this then. I read this as:
> 
> "If claiming direct mode succeeded, then return an error!"

I am used to seeing a pattern where function returning zero indicates a 
success. I have no statistics but I believe this is true for a vast 
majority of functions in the kernel. I believe this was the case with 
the old 'iio_device_claim_direct_mode(idev)' too.

I am not saying this is 'absolutely' bad. I can only tell that _I_ 
really had to go and look up the implementation of the 
iio_device_claim_direct() in order to review this change to ensure the 
return value check was not inverted.

Yours,
	-- Matti


  reply	other threads:[~2025-02-19  5:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 14:01 [PATCH 0/8] IIO: Accelerometers: Sparse friendly claim of direct mode Jonathan Cameron
2025-02-17 14:01 ` [PATCH 1/8] iio: accel: mma8452: Ensure error return on failure to matching oversampling ratio Jonathan Cameron
2025-02-17 14:01 ` [PATCH 2/8] iio: accel: mma8452: Factor out guts of write_raw() to simplify locking Jonathan Cameron
2025-02-17 14:01 ` [PATCH 3/8] iio: accel: mma8452: Switch to sparse friendly iio_device_claim/release_direct() Jonathan Cameron
2025-02-17 14:01 ` [PATCH 4/8] iio: accel: kx022a: Factor out guts of write_raw() to allow direct returns Jonathan Cameron
2025-02-18  7:32   ` Matti Vaittinen
2025-02-17 14:01 ` [PATCH 5/8] iio: accel: kx022a: Switch to sparse friendly iio_device_claim/release_direct() Jonathan Cameron
2025-02-18  7:39   ` Matti Vaittinen
2025-02-18 15:42     ` David Lechner
2025-02-19  5:36       ` Matti Vaittinen [this message]
2025-02-19 10:51         ` Nuno Sá
2025-02-19 12:21           ` Matti Vaittinen
2025-02-19 15:25             ` David Lechner
2025-02-19 19:05               ` Jonathan Cameron
2025-02-20  6:31                 ` Matti Vaittinen
2025-02-20 17:49                   ` Jonathan Cameron
2025-02-20  6:26               ` Matti Vaittinen
2025-02-19 16:06             ` Jonathan Cameron
2025-02-17 14:01 ` [PATCH 6/8] iio: accel: msa311: Fix failure to release runtime pm if direct mode claim fails Jonathan Cameron
2025-02-17 14:01 ` [PATCH 7/8] iio: accel: msa311: Switch to sparse friendly iio_device_claim/release_direct() Jonathan Cameron
2025-02-17 14:01 ` [PATCH 8/8] iio: accel: " Jonathan Cameron
2025-02-17 22:21 ` [PATCH 0/8] IIO: Accelerometers: Sparse friendly claim of direct mode David Lechner
2025-02-22 12:42   ` Jonathan Cameron

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=ead33fc6-48b9-488c-8993-2ca647e59735@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=noname.nuno@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