From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
sathyanarayanan.kuppuswamy@linux.intel.com,
Daniel Baluta <daniel.baluta@gmail.com>
Cc: Peter Meerwald <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v1 2/3] iio: ltr501: Add interrupt rate control support
Date: Wed, 22 Apr 2015 21:58:46 +0100 [thread overview]
Message-ID: <55380B86.6090404@kernel.org> (raw)
In-Reply-To: <5537C565.4000704@metafoo.de>
On 22/04/15 16:59, Lars-Peter Clausen wrote:
> On 04/10/2015 07:51 AM, Jonathan Cameron wrote:
> [...]
>>>> So level rather than edge triggered. Definitely what we put _period
>>>> in for in the first place. Admittedly persistence might have been a
>>> better
>>>> name, but too late now! (dratted ABI compatibility)
>>>>
>>>> J
>>> But we cannot use period for this use case. According to _period ABI
>>> description,
>>> It specifies the period of time for which the condition must be true
>>> for
>>> getting a
>>> valid event. But here, we are checking for number of times a condition
>>> must be
>>> true for generating a valid event.
>> But we are checking that condition at a known sampling rate I assume?
>> Hence
>> period = persistence x 1/sampling frequency?
>
> Sorry for highjacking this thread.
>
> So period is for the time interval it has the event has to be asserted before it is registered. What would we call the same thing but for the de-assertion of the event? The event has to be de-asserted for X amount of time before it gets propagated.
Err, offperiod? resetperiod? space? (on the basis of mark-space description of square waves?)
It's kind of temporal hysteresis, or a debounce filter I suppose. Period
isn't great for the existing interface.
>
> Thanks,
> - Lars
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-22 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 2:55 [PATCH v1 0/3] Added LTR501 Interrupt support Kuppuswamy Sathyanarayanan
2015-04-01 2:55 ` [PATCH v1 1/3] iio: ltr501: Add interrupt support Kuppuswamy Sathyanarayanan
2015-04-01 2:55 ` [PATCH v1 2/3] iio: ltr501: Add interrupt rate control support Kuppuswamy Sathyanarayanan
2015-04-01 14:04 ` Daniel Baluta
2015-04-01 14:39 ` Lars-Peter Clausen
2015-04-01 15:02 ` Daniel Baluta
2015-04-01 15:15 ` Lars-Peter Clausen
2015-04-01 17:45 ` sathyanarayanan kuppuswamy
2015-04-01 17:48 ` Lars-Peter Clausen
2015-04-01 19:06 ` sathyanarayanan kuppuswamy
2015-04-01 19:22 ` sathyanarayanan kuppuswamy
2015-04-09 10:16 ` Jonathan Cameron
2015-04-09 22:35 ` sathyanarayanan kuppuswamy
2015-04-10 5:51 ` Jonathan Cameron
2015-04-22 15:59 ` Lars-Peter Clausen
2015-04-22 20:58 ` Jonathan Cameron [this message]
2015-04-01 20:19 ` Jonathan Cameron
2015-04-01 17:33 ` sathyanarayanan kuppuswamy
2015-04-01 2:55 ` [PATCH v1 3/3] iio: ltr501: Add ACPI enumeration support Kuppuswamy Sathyanarayanan
2015-04-01 13:02 ` [PATCH v1 0/3] Added LTR501 Interrupt support Daniel Baluta
2015-04-01 17:29 ` sathyanarayanan kuppuswamy
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=55380B86.6090404@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.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.