linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg@ti.com>
To: Alexander Koch <mail@alexanderkoch.net>, <jic23@kernel.org>
Cc: <knaack.h@gmx.de>, <lars@metafoo.de>, <pmeerw@pmeerw.net>,
	<mhornung.linux@gmail.com>, <balbi@ti.com>,
	<fengguang.wu@intel.com>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] iio: light: opt3001: Enable operation w/o IRQ
Date: Fri, 29 Jan 2016 12:05:42 -0600	[thread overview]
Message-ID: <20160129180542.GD7960@LTA0797059A> (raw)
In-Reply-To: <1452960878-1727-1-git-send-email-mail@alexanderkoch.net>

On Sat, Jan 16, 2016 at 05:14:35PM +0100, Alexander Koch wrote:
> This patch series aims at enabling IRQ-less operation for the TI OPT3001 light
> sensor.

Jon,
I was checking to see if the DT bindings have been updated to reflect
the interrupt-less operation however I can't seem to find it in the
Kernel tree. The last activity I can find is this one...

https://patchwork.ozlabs.org/patch/490819/

I guess it may have slipped through the cracks so I'm going to update
the bindings document and re-submit.

Regards,
Andreas

> 
> The current version of the driver requires an interrupt line to be connected to
> the INT pin of the sensor, through which the IIO framework gets notified about
> readout values being ready. In the datasheet this is described as optional (sec.
> 8.1.1).
> 
> In my use case of the OPT3001 I do not have any interrupt lines or GPIOs
> available to connect the INT pin to, so I have implemented an interrupt-less
> operation mode that simply sleeps for the specified worst-case readout time
> instead of waiting for the interrupt.
> 
> This change is transparent as interrupt-less operation mode is done only when no
> valid interrupt no. is configured via device tree.
> 
> Patches are taken against linux-next/master, tested by compilation,
> checkpatch.pl and by running on an embedded developer board (both IRQ-enabled
> and IRQ-less mode).
> 
> 
> Changes from v1:
> 
>  - use type bool for introduced member 'use_irq'
>  - include trivial refactoring step that changes the types of two other members
>    to bool, in order to match 'use_irq'
> 
> 
> Alexander Koch (3):
>   iio: light: opt3001: extract int. time constants
>   iio: light: opt3001: trivial type refactoring
>   iio: light: opt3001: enable operation w/o IRQ
> 
>  drivers/iio/light/opt3001.c | 156 ++++++++++++++++++++++++++++++--------------
>  1 file changed, 106 insertions(+), 50 deletions(-)
> 
> -- 
> 2.7.0
> 

      parent reply	other threads:[~2016-01-29 18:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 16:14 [PATCH v2 0/3] iio: light: opt3001: Enable operation w/o IRQ Alexander Koch
2016-01-16 16:14 ` [PATCH v2 1/3] iio: light: opt3001: extract int. time constants Alexander Koch
2016-01-24 15:01   ` Jonathan Cameron
2016-01-29 17:59   ` Andreas Dannenberg
2016-01-16 16:14 ` [PATCH v2 2/3] iio: light: opt3001: trivial type refactoring Alexander Koch
2016-01-24 15:02   ` Jonathan Cameron
2016-01-29 18:00   ` Andreas Dannenberg
2016-01-16 16:14 ` [PATCH v2 3/3] iio: light: opt3001: enable operation w/o IRQ Alexander Koch
2016-01-18 17:07   ` Martin Kepplinger
2016-01-23 18:55     ` Alexander Koch
2016-01-24 14:55       ` Jonathan Cameron
2016-01-24 15:07     ` Jonathan Cameron
2016-01-29 18:01   ` Andreas Dannenberg
2016-01-30 16:27     ` Jonathan Cameron
2016-01-29 18:05 ` Andreas Dannenberg [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=20160129180542.GD7960@LTA0797059A \
    --to=dannenberg@ti.com \
    --cc=balbi@ti.com \
    --cc=fengguang.wu@intel.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@alexanderkoch.net \
    --cc=mhornung.linux@gmail.com \
    --cc=pmeerw@pmeerw.net \
    /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).