devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Cristian Pop <cristian.pop@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] Documentation/ABI/testing: Add documentation for AD5766 new ABI
Date: Tue, 29 Dec 2020 16:47:28 +0000	[thread overview]
Message-ID: <20201229164728.38a7d892@archlinux> (raw)
In-Reply-To: <20201229162758.187beafd@archlinux>

On Tue, 29 Dec 2020 16:27:58 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Fri, 18 Dec 2020 19:12:30 +0200
> Cristian Pop <cristian.pop@analog.com> wrote:
> 
> > New interface is proposed for dither functionality. This future allows
> > composing  an external signals to the selected output channel.
> > The dither signal can be turned on/off, scaled, inverted, or it can be
> > selected from different sources.
> > 
> > Signed-off-by: Cristian Pop <cristian.pop@analog.com>  
> Coming together nicely though a few more thoughts came to mind when reading
> this. Only significant one is whether we are better with decimal scaling
> than percentage scaling for consistency with channel scales etc?
> 
> Jonathan
> 
> > ---
> > Changelog v4:
> > 	- Change to "in_voltageY_dither_enable"
> > 	- Change scale to numbers + 100% for no scaling
> > 	- Possible dither source values: 0 - N0, 1 - N1 
> >  .../ABI/testing/sysfs-bus-iio-dac-ad5766      | 36 +++++++++++++++++++
> >  1 file changed, 36 insertions(+)
> >  create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766
> > 
> > diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766 b/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766
> > new file mode 100644
> > index 000000000000..72100edb88bb
> > --- /dev/null
> > +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-ad5766
> > @@ -0,0 +1,36 @@
> > +What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_pwr  
> 
> in_voltageY_dither_en would be more consistent with existing ABI naming.
Seems to be different in the code (dither_enable I think) so please sanity
check this file carefully against the driver.

Thanks,

Jonathan

> 
> > +KernelVersion:
> > +Contact:	linux-iio@vger.kernel.org
> > +Description:
> > +		Dither enable. Write 1 to enable dither or 0 to disable it.
> > +
> > +What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_invert
> > +KernelVersion:
> > +Contact:	linux-iio@vger.kernel.org
> > +Description:
> > +		Inverts the dither applied to the selected DAC channel. Dither is not
> > +		inverted by default. Write "1" to invert dither.
> > +
> > +What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale_available
> > +KernelVersion:
> > +Contact:	linux-iio@vger.kernel.org
> > +Description:
> > +		Returns possible scalings available for the current channel:  
> 
> Given this one is self defining and may well get generalized to other devices I'd
> got with a description that doesn't provide values.
> 
> Returns possible scalings as percentages.
> 
> However, thinking more on this it's a bit inconsistent with other scale values we have
> which are given in decimal.  Would "1 0.75 0.5 0.25" work as well here?
> 
> > +		"100 75 50 25" scaling.
> > +
> > +What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_scale
> > +KernelVersion:
> > +Contact:	linux-iio@vger.kernel.org
> > +Description:
> > +		Scales the dither before it is applied to the selected channel:
> > +		100 - No scaling
> > +		75 - 75% scaling
> > +		50 - 50% scaling
> > +		25 - 25% scaling  
> 
> As above, I'm don't really see an advantage in providing the values.  Any userspace
> ought to cope with any (finding out what is there via _available).
> "Scales the dither before it is applied to the selected channel.  1 corresponds
> to no scaling".
> 
> > +
> > +What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_dither_source
> > +KernelVersion:  
> 
> Please fill in the expected kernel version.  I'll fix it if this happens to merge near
> the change over in a cycle, but it's easier to fix something that is there
> than to add it from scratch :)
> 
> > +Contact:	linux-iio@vger.kernel.org
> > +Description:
> > +		Selects dither source applied to the selected channel. Write "0" to
> > +		select N0 source, write "1" to select N1 source.  
> 


  reply	other threads:[~2020-12-29 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 17:12 [PATCH v4 1/3] dt-bindings: iio: dac: AD5766 yaml documentation Cristian Pop
2020-12-18 17:12 ` [PATCH v4 2/3] Documentation/ABI/testing: Add documentation for AD5766 new ABI Cristian Pop
2020-12-29 16:27   ` Jonathan Cameron
2020-12-29 16:47     ` Jonathan Cameron [this message]
2020-12-18 17:12 ` [PATCH v4 3/3] iio: dac: ad5766: add driver support for AD5766 Cristian Pop
2020-12-29 16:52   ` Jonathan Cameron
2020-12-21 18:44 ` [PATCH v4 1/3] dt-bindings: iio: dac: AD5766 yaml documentation Rob Herring
2020-12-29 16:19   ` 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=20201229164728.38a7d892@archlinux \
    --to=jic23@kernel.org \
    --cc=cristian.pop@analog.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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).