All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Nishant Malpani <nish.malpani25@gmail.com>
Cc: <jic23@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-iio@vger.kernel.org>, <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v3 0/3] iio: gyro: adxrs290: Add triggered buffer & debugfs support
Date: Thu, 10 Sep 2020 18:46:18 +0100	[thread overview]
Message-ID: <20200910184618.00001b86@Huawei.com> (raw)
In-Reply-To: <20200910123000.16860-1-nish.malpani25@gmail.com>

On Thu, 10 Sep 2020 17:59:57 +0530
Nishant Malpani <nish.malpani25@gmail.com> wrote:

> Introduce DATA_RDY trigger for triggered buffer setup; this enables continuous
> data capture. Additionally, add support for direct register access using the debugfs 
> iio interface. 
> 
> The device-tree bindings documentation illustrates an example of using a GPIO irq
> line to trigger a data capture.
> 
> Nishant Malpani (3):
>   iio: gyro: adxrs290: Add triggered buffer support
>   dt-bindings: iio: gyro: adxrs290: Add interrupts support
>   iio: gyro: adxrs290: Add debugfs register access support
> 
>  .../bindings/iio/gyroscope/adi,adxrs290.yaml  |   6 +
>  drivers/iio/gyro/Kconfig                      |   2 +
>  drivers/iio/gyro/adxrs290.c                   | 237 ++++++++++++++++--
>  3 files changed, 231 insertions(+), 14 deletions(-)
> 

Hi Nishant,

Something odd went on with this version.  It's not come across threaded
and patch 1 is missing.  Please resend.

Thanks,

Jonathan


      parent reply	other threads:[~2020-09-10 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 12:29 [PATCH v3 0/3] iio: gyro: adxrs290: Add triggered buffer & debugfs support Nishant Malpani
2020-09-10 13:51 ` Andy Shevchenko
2020-09-10 17:46 ` 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=20200910184618.00001b86@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nish.malpani25@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.