public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Jonathan.Cameron@huawei.com, linux-iio@vger.kernel.org,
	Felipe Balbi <balbi@kernel.org>,
	Raymond Tan <raymond.tan@intel.com>
Subject: Re: [PATCH 2/2] counter: Add support for Intel Quadrature Encoder Peripheral
Date: Thu, 8 Apr 2021 08:42:42 +0900	[thread overview]
Message-ID: <YG5DcjXAFafqbD5t@shinobu> (raw)
In-Reply-To: <778390eb-d27b-c486-0f3d-610e019e69f0@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

On Wed, Apr 07, 2021 at 05:25:48PM +0300, Jarkko Nikula wrote:
> On 4/2/21 1:30 PM, William Breathitt Gray wrote:
> > On Thu, Apr 01, 2021 at 06:32:28PM +0300, Jarkko Nikula wrote:
> >> +static const struct counter_device_ext intel_qep_ext[] = {
> >> +	INTEL_QEP_COUNTER_EXT_RW(noise),
> >> +	INTEL_QEP_COUNTER_EXT_RW(preset_enable)
> >> +};
> > 
> > "noise" is a new attribute so you'll need to provide an entry in
> > Documentation/ABI/testing/sysfs-bus-counter explaining it.
> > 
> Should this noise actually be visible as seconds (ns, µs, ms) instead of 
> plain register value? From the spec "It selects the maximum glitch width 
> to remove in terms of peripheral clock cycles: PCLK_CYCLES = MAX_COUNT + 2".
> 
> I think it should since for a person configuring the system plain 
> register value is more or less guesswork.
> 
> Jarkko

If this clock is actually temporal in nature then denominating this
value in a temporal unit such as nanonseconds should be fine as long as
such values have a well-defined behavior for this device. I do recommend
giving this attribute a more fitting name however because it is not
immediately obvious what an attribute called "noise" controls.

William Breathitt Gray

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-07 23:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 15:32 [PATCH 1/2] counter: Add support for Quadrature x4 with swapped inputs Jarkko Nikula
2021-04-01 15:32 ` [PATCH 2/2] counter: Add support for Intel Quadrature Encoder Peripheral Jarkko Nikula
2021-04-02 10:30   ` William Breathitt Gray
2021-04-07 14:25     ` Jarkko Nikula
2021-04-07 23:42       ` William Breathitt Gray [this message]
2021-04-02  9:06 ` [PATCH 1/2] counter: Add support for Quadrature x4 with swapped inputs William Breathitt Gray

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=YG5DcjXAFafqbD5t@shinobu \
    --to=vilhelm.gray@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=balbi@kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=raymond.tan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox