linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: gabriele.mzt@gmail.com, lars@metafoo.de,
	andy.shevchenko@gmail.com, linux-iio@vger.kernel.org
Subject: Re: [PATCH v7 0/3] iio: acpi_als: Add sotfware trigger support
Date: Sat, 20 Mar 2021 17:12:14 +0000	[thread overview]
Message-ID: <20210320171214.0b948527@jic23-huawei> (raw)
In-Reply-To: <20210317074012.2336454-1-gwendal@chromium.org>

On Wed, 17 Mar 2021 00:40:09 -0700
Gwendal Grignou <gwendal@chromium.org> wrote:

> Some devices (chromebooks) present the ACPI ALS device but do not have
> ability to notify when a new sample is present.
> Add support for software trigger (hrtimer/sysfs-trigger) to allow
> retrieving samples using iio buffers.
> 
> The first path fully adds timestamp channel, the second adds a local
> variable in probe routine and the last one adds trigger support.
> 
> This patch assumes the patch "iio: set default trig->dev.parent" is
> applied.
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to poke at it.

Thanks,

Jonathan

> 
> Changes since v7:
>   rebase on iio git testing branch.
> 
> Gwendal Grignou (3):
>   iio: acpi_als: Add timestamp channel
>   iio: acpi_als: Add local variable dev in probe
>   iio: acpi_als: Add trigger support
> 
>  drivers/iio/light/acpi-als.c | 113 +++++++++++++++++++++++------------
>  1 file changed, 76 insertions(+), 37 deletions(-)
> 


      parent reply	other threads:[~2021-03-20 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  7:40 [PATCH v7 0/3] iio: acpi_als: Add sotfware trigger support Gwendal Grignou
2021-03-17  7:40 ` [PATCH v7 1/3] iio: acpi_als: Add timestamp channel Gwendal Grignou
2021-03-17  7:40 ` [PATCH v7 2/3] iio: acpi_als: Add local variable dev in probe Gwendal Grignou
2021-03-17  7:40 ` [PATCH v7 3/3] iio: acpi_als: Add trigger support Gwendal Grignou
2021-03-20 17:12 ` 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=20210320171214.0b948527@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.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 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).