From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Darren Schachter <dts86@cornell.edu>,
Christopher Hall <christopher.s.hall@intel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Matt Porter <mporter@konsulko.com>,
robertcnelson@beagleboard.org,
Drew Fustini <drew@beagleboard.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: pulse: Support PWM capture with TI AM3358 eCAP module
Date: Thu, 20 Aug 2020 16:02:01 +0300 [thread overview]
Message-ID: <CAHp75VcpyHgmkerPE7OmkM-FyF1YWLH0u1EPQhaTYcuOYj5htQ@mail.gmail.com> (raw)
In-Reply-To: <20200818153614.6438-1-dts86@cornell.edu>
+Cc: Chris
On Tue, Aug 18, 2020 at 6:37 PM Darren Schachter <dts86@cornell.edu> wrote:
>
> This IIO driver adds support for PWM capture with the TI eCAP module.
> This driver is based on Matt Porter's eCAP driver from January 2014,
> which was never merged into the mainline [1]. Like Matt's code, this
> driver implements interrupt driven triggered buffer capture. However,
> the driver has been updated based on previous suggestions in the IIO
> mailing list. Additionally, support for prescalar control and finer
> polarity control has been included. Users can now configure the
> polarities of CAP1 and CAP2 individually, allowing for the measurement
> of a signal's high-time, low-time, or period.
Chris, does this ring any bell (in terms of certain functionality of
Time-aware GPIO)?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-08-20 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 15:36 [PATCH] iio: pulse: Support PWM capture with TI AM3358 eCAP module Darren Schachter
2020-08-18 20:49 ` kernel test robot
2020-08-19 20:08 ` Darren Schachter
2020-08-20 13:02 ` Andy Shevchenko [this message]
2020-08-30 12:42 ` Jonathan Cameron
2020-09-01 21:11 ` Darren Schachter
2020-09-02 13:16 ` Jonathan Cameron
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=CAHp75VcpyHgmkerPE7OmkM-FyF1YWLH0u1EPQhaTYcuOYj5htQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=christopher.s.hall@intel.com \
--cc=drew@beagleboard.org \
--cc=dts86@cornell.edu \
--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=mporter@konsulko.com \
--cc=pmeerw@pmeerw.net \
--cc=robertcnelson@beagleboard.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).