linux-kernel - Re: [PATCH v6 2/2] iio: proximity: vl53l0x: add interrupt support

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]

Date:   Wed, 26 Sep 2018 17:46:18 -0500
From:   Rob Herring <robh@...nel.org>
To:     Jonathan Cameron <jic23@...nel.org>
Cc:     Song Qiang <songqiang1304521@...il.com>, knaack.h@....de,
        lars@...afoo.de, pmeerw@...erw.net, mark.rutland@....com,
        andriy.shevchenko@...ux.intel.com, matt.ranostay@...sulko.com,
        tglx@...utronix.de, ak@...klinger.de, linux-iio@...r.kernel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v6 2/2] iio: proximity: vl53l0x: add interrupt support

On Sat, Sep 22, 2018 at 04:05:23PM +0100, Jonathan Cameron wrote:
> On Tue, 18 Sep 2018 16:24:22 +0800
> Song Qiang <songqiang1304521@...il.com> wrote:
> 
> > The first version of this driver issues a measuring request and polling
> > for a status register in the device for measuring completes.
> > vl53l0x support configuring GPIO1 on it to generate interrupt to
> > indicate that new measurement is ready. This patch adds support for
> > using this mechanisim to reduce cpu cost.
> > 
> > Signed-off-by: Song Qiang <songqiang1304521@...il.com>
> Hi Song.
> 
> Looks correct in principal but a few things to tidy up before
> this is ready to apply.
> 
> Also we have an unrelated change in here to check the devices ID.
> That should be in it's own patch.
> 
> Thanks,
> 
> Jonathan
> > ---
> >  .../bindings/iio/proximity/vl53l0x.txt        |  14 +-

This should have been split with the complete binding in one patch 
rather than piecemeal driver feature by feature.

> >  drivers/iio/proximity/vl53l0x-i2c.c           | 135 +++++++++++++++---
> >  2 files changed, 129 insertions(+), 20 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt b/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
> > index ab9a9539fec4..40290f8dd70f 100644
> > --- a/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
> > +++ b/Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
> > @@ -4,9 +4,21 @@ Required properties:
> >  	- compatible: must be "st,vl53l0x-i2c"

Is there more than one interface on this device, such as SPI? If not, 
then '-i2c' should be dropped.

> >  	- reg: i2c address where to find the device
> >  
> > +Optional properties:
> > +	- interrupts : Interrupt line receiving GPIO1's measuring complete
> > +	  output, supports IRQ_TYPE_EDGE_FALLING only.
> > +
> > +	Refer to interrupt-controller/interrupts.txt for generic
> > +	interrupt client node bindings.
> > +
> >  Example:
> >  
> >  vl53l0x@29 {
> > +	pinctrl-names = "default";
> > +	pinctrl-0 = <&vl53l0x_pins>;
> > +
> Please drop this from the example.  This is board specific rather than
> being generally required.
> 
> >  	compatible = "st,vl53l0x-i2c";
> >  	reg = <0x29>;
> > -};
> > +	interrupt-parent = <&gpio3>;
> > +	interrupts = <17 IRQ_TYPE_EDGE_FALLING>;
> > +}