From: Jonathan Cameron <jic23@kernel.org>
To: Shreeya Patel <shreeya.patel@collabora.com>
Cc: lars@metafoo.de, robh+dt@kernel.org, Zhigang.Shi@liteon.com,
krisman@collabora.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, alvaro.soliverez@collabora.com,
andy.shevchenko@gmail.com, digetx@gmail.com
Subject: Re: [PATCH v5 0/2] Add LTRF216A Driver
Date: Tue, 14 Jun 2022 12:51:46 +0100 [thread overview]
Message-ID: <20220614125146.35b8288d@jic23-huawei> (raw)
In-Reply-To: <20220608113553.32083-1-shreeya.patel@collabora.com>
On Wed, 8 Jun 2022 17:05:51 +0530
Shreeya Patel <shreeya.patel@collabora.com> wrote:
> This patchset adds support for ltrf216a Ambient Light Sensor
> and documents the DT bindings for the same.
>
As Andy already gave some valuable feedback and you have
a few autobuilder checks to fix up (plus I'm low on time this week)
I'll wait for v6 before taking another look.
Thanks,
Jonathan
>
> Changes in v5
> - Add power management support.
> - Add reset functionality.
> - Use readx_poll_timeout() to get data.
> - Cleanup some of the redundant code.
> - Update int_time_fac after I2C write is successful.
> - Rename mutex to lock.
> - Use Reverse Xmas tree pattern for all variable definitions.
> - Improve error handling messages and add error codes.
> - Add one more MODULE_AUTHOR.
> - Remove cleardata which was reading data for infrared light.
> - Remove patch for deprecated vendor prefix [PATCH v4 3/3].
> - Remove deprecated string from DT binding document.
>
> Changes in v4
> - Add more descriptive comment for mutex lock
> - Fix mutex locking in read_raw()
> - Use i2c_smbus_read_i2c_block_data()
>
> Changes in v3
> - Use u16 instead of u8 for int_time_fac
> - Reorder headers in ltrf216a.c file
> - Remove int_time_mapping table and use int_time_available
> - Fix indentation in the bindings file.
>
> Changes in v2
> - Add support for 25ms and 50ms integration time.
> - Rename some of the macros as per names given in datasheet
> - Add a comment for the mutex lock
> - Use read_avail callback instead of attributes and set the
> appropriate _available bit.
> - Use FIELD_PREP() at appropriate places.
> - Add a constant lookup table for integration time and reg val
> - Use BIT() macro for magic numbers.
> - Improve error handling at few places.
> - Use get_unaligned_le24() and div_u64()
> - Use probe_new() callback and devm functions
> - Return errors in probe using dev_err_probe()
> - Use DEFINE_SIMPLE_DEV_PM_OPS()
> - Correct the formula for lux to use 0.45 instead of 0.8
> - Add interrupt and power supply property in DT bindings
> - Add vendor prefix name as per the alphabetical order.
>
>
> Shreeya Patel (2):
> dt-bindings: Document ltrf216a light sensor bindings
> iio: light: Add support for ltrf216a sensor
>
> .../bindings/iio/light/liteon,ltrf216a.yaml | 50 ++
> drivers/iio/light/Kconfig | 10 +
> drivers/iio/light/Makefile | 1 +
> drivers/iio/light/ltrf216a.c | 441 ++++++++++++++++++
> 4 files changed, 502 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
> create mode 100644 drivers/iio/light/ltrf216a.c
>
prev parent reply other threads:[~2022-06-14 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 11:35 [PATCH v5 0/2] Add LTRF216A Driver Shreeya Patel
2022-06-08 11:35 ` [PATCH v5 1/2] dt-bindings: Document ltrf216a light sensor bindings Shreeya Patel
2022-06-08 13:45 ` Rob Herring
2022-06-08 11:35 ` [PATCH v5 2/2] iio: light: Add support for ltrf216a sensor Shreeya Patel
2022-06-08 16:16 ` Andy Shevchenko
2022-06-13 12:52 ` Shreeya Patel
2022-06-09 2:24 ` kernel test robot
2022-06-09 2:24 ` kernel test robot
2022-06-14 11:51 ` Jonathan Cameron [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=20220614125146.35b8288d@jic23-huawei \
--to=jic23@kernel.org \
--cc=Zhigang.Shi@liteon.com \
--cc=alvaro.soliverez@collabora.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.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;
as well as URLs for NNTP newsgroup(s).