linux-kernel - Re: [PATCH v2 0/2] iio: proximity: driver for vcnl3020

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <746c7b3ccbd013edba84a51fc0a99bb11e5f9c26.camel@yadro.com>
Date:   Thu, 26 Mar 2020 16:06:37 +0300
From:   Ivan Mikhaylov <i.mikhaylov@...ro.com>
To:     Ivan Mikhaylov <i.mikhaylov@...ro.com>
CC:     Jonathan Cameron <jic23@...nel.org>,
        Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        <linux-iio@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>, Mark Rutland <mark.rutland@....com>,
        Rob Herring <robh+dt@...nel.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>
Subject: Re: [PATCH v2 0/2] iio: proximity: driver for vcnl3020

On Wed, 2020-03-25 at 18:12 +0300, Ivan Mikhaylov wrote:
> Add proximity sensor driver for Vishay vcnl3020. Only on-demand
> measurement is supported for now.
> 
> Ivan Mikhaylov (2):
>   iio: proximity: provide device tree binding document
>   iio: proximity: Add driver support for vcnl3020 proximity sensor
> 
>  .../bindings/iio/proximity/vcnl3020.yaml      |  47 ++++
>  drivers/iio/proximity/Kconfig                 |  10 +
>  drivers/iio/proximity/Makefile                |   1 +
>  drivers/iio/proximity/vcnl3020.c              | 242 ++++++++++++++++++
>  4 files changed, 300 insertions(+)
>  create mode 100644
> Documentation/devicetree/bindings/iio/proximity/vcnl3020.yaml
>  create mode 100644 drivers/iio/proximity/vcnl3020.c
> 

Changes from v1:
   1. using regmap interface instead of i2c_smbus_* calls.
   2. switch from probe to probe_new.
   3. s32/int32_t -> int