From: David Lechner <dlechner@baylibre.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, "Chris Hall" <c-hall@ti.com>,
"Patrick Edwards" <pedwards@ti.com>,
"Kurt Borja" <kuurtb@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Linus Walleij" <linusw@kernel.org>
Subject: Re: [PATCH v2 2/2] iio: adc: ti-ads112c14: add gpio support
Date: Sat, 10 Oct 2026 08:46:30 -0500 [thread overview]
Message-ID: <cde9d00a-bfe4-4093-b03d-f76a122e4ded@baylibre.com> (raw)
In-Reply-To: <CAMRc=Mfn7+uQYvLjGLxU9wMOnRwx5pyPgaLp6oNx+ZcFXyXL=A@mail.gmail.com>
On 10/10/26 4:00 AM, Bartosz Golaszewski wrote:
> On Sat, 10 Oct 2026 01:25:52 +0200, "David Lechner (TI)"
> <dlechner@baylibre.com> said:
>> Add support for using the AIN4/GPIO0 to AIN7/GPIO3 pins as GPIOs when
>> the gpio-controller property is present.
>>
...
>> @@ -2574,6 +2726,12 @@ static int ads112c14_probe(struct i2c_client *client)
>> if (ret)
>> return ret;
>>
>> + if (device_property_read_bool(dev, "gpio-controller")) {
>
> I think the right one to use is device_property_present().
I thought this was the one case where device_property_read_bool() is
actually correct because gpio-controller property is a
/schemas/types.yaml#/definitions/flag.
Otherwise, we should just remove device_property_read_bool() from the tree
because there would never be a reason to use it.
My understanding is we should use device_property_present() for non-boolean
properties when we want to know if it is present or not before reading the
value of it.
>
>> + ret = ads112c14_gpio_init(indio_dev);
>> + if (ret)
>> + return ret;
>> + }
>> +
>> return devm_iio_device_register(dev, indio_dev);
>> }
>>
>>
>> --
>> 2.53.0
>>
>>
>
> Bart
prev parent reply other threads:[~2026-10-10 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 23:25 [PATCH v2 0/2] " David Lechner (TI)
2026-10-09 23:25 ` [PATCH v2 1/2] iio: adc: ti-ads112c14: parameterize GPIO register field macros David Lechner (TI)
2026-10-10 9:00 ` Bartosz Golaszewski
2026-10-09 23:25 ` [PATCH v2 2/2] iio: adc: ti-ads112c14: add gpio support David Lechner (TI)
2026-10-10 9:00 ` Bartosz Golaszewski
2026-10-10 13:46 ` David Lechner [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=cde9d00a-bfe4-4093-b03d-f76a122e4ded@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=c-hall@ti.com \
--cc=jic23@kernel.org \
--cc=kuurtb@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pedwards@ti.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
all inboxes | Powered by JetHome®