From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Stephen Boyd <swboyd@chromium.org>,
Daniel Campello <campello@chromium.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] iio: sx9310: Support ACPI properties
Date: Fri, 19 Mar 2021 19:49:43 +0200 [thread overview]
Message-ID: <CAHp75Vep=SXxMNs+8MinL_1BXyozrz8cYDZCH8A06a2dppoD0w@mail.gmail.com> (raw)
In-Reply-To: <20210319165807.3639636-1-gwendal@chromium.org>
On Fri, Mar 19, 2021 at 6:58 PM Gwendal Grignou <gwendal@chromium.org> wrote:
>
> Current sx9310 driver only support device tree properties.
> To be able to use sensor on Intel platfrom, add support to read ACPI by
> converting calls of_property_read_...() to device_property_read_...().
>
> A bug was uncovered: if "semtech,combined-sensors" array was less than
> 4 entries, its content would be ignored, as of_property_read_u32_array
> would return -EOVERFLOW.
After addressing comments, feel free to add
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Gwendal Grignou (2):
> iio: sx9310: Fix access to variable DT array
> iio: sx9310: Support ACPI properties
>
> drivers/iio/proximity/sx9310.c | 56 +++++++++++++++++++++-------------
> 1 file changed, 34 insertions(+), 22 deletions(-)
>
> --
> 2.31.0.291.g576ba9dcdaf-goog
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-03-19 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:58 [PATCH v5 0/2] iio: sx9310: Support ACPI properties Gwendal Grignou
2021-03-19 16:58 ` [PATCH v5 1/2] iio: sx9310: Fix access to variable DT array Gwendal Grignou
2021-03-19 16:58 ` [PATCH v5 2/2] iio: sx9310: Support ACPI properties Gwendal Grignou
2021-03-19 17:48 ` Andy Shevchenko
2021-03-19 17:46 ` [PATCH v5 0/2] " Andy Shevchenko
2021-03-19 17:49 ` Andy Shevchenko [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='CAHp75Vep=SXxMNs+8MinL_1BXyozrz8cYDZCH8A06a2dppoD0w@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=campello@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.