Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Julien Stephan <jstephan@baylibre.com>
Cc: "Michael Hennerich" <michael.hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Jonathan Corbet" <corbet@lwn.net>,
	linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: iio: new docs for ad7380 driver
Date: Tue, 16 Jul 2024 19:04:59 +0100	[thread overview]
Message-ID: <20240716190459.7cfad009@jic23-huawei> (raw)
In-Reply-To: <20240709-ad7380-add-docs-v1-1-458ced3dfcc5@baylibre.com>

On Tue, 09 Jul 2024 17:16:46 +0200
Julien Stephan <jstephan@baylibre.com> wrote:

> This adds a new page to document how to use the ad7380 ADC driver.
> 
> Credit: this docs is based on ad7944 docs.
> 
> Signed-off-by: Julien Stephan <jstephan@baylibre.com>
Only thing in here I wondered about is talking about what libiio supports.
That is likely to change if we get lots of devices with the sort of resolution
changing that occurs with this one.  Ah well, I guess we will probably get
stale docs if no one is paying attention.   That happens anyway for so
many other reasons I'm not that worried about one more.

Applied to the testing branch of iio.git for now as I'll be rebasing on rc1
once available.

Thanks,

Jonathan


> +Since the resolution boost feature causes 16-bit chips to now have 18-bit data
> +which means the storagebits has to change from 16 to 32 bits, we use the new
> +ext_scan_type feature to allow changing the scan_type at runtime. Unfortunately
> +libiio does not support it. So when enabling or disabling oversampling, user
> +must restart iiod using the following command:
> +
> +.. code-block:: bash
> +
> +	root:~# systemctl restart iiod
> +
> +

      reply	other threads:[~2024-07-16 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 15:16 [PATCH] docs: iio: new docs for ad7380 driver Julien Stephan
2024-07-16 18:04 ` 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=20240716190459.7cfad009@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dlechner@baylibre.com \
    --cc=jstephan@baylibre.com \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=nuno.sa@analog.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