From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Ammar Mustafa" <ammarmustafa34@gmail.com>,
"Alisa-Dariana Roman" <alisa.roman@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Docs: iio: ad7191 Correct clock configuration
Date: Sun, 22 Mar 2026 12:13:14 +0000 [thread overview]
Message-ID: <20260322121314.0143bda3@jic23-huawei> (raw)
In-Reply-To: <aaLIhgJjrNlp3oTy@ashevche-desk.local>
On Sat, 28 Feb 2026 12:50:46 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Fri, Feb 27, 2026 at 02:08:33PM -0500, Ammar Mustafa wrote:
> > Correct the ad7191 documentation to match the datasheet:
> > - Fix inverted CLKSEL pin logic: device uses external clock when pin is
> > inactive, and internal CMOS/crystal when high.
>
> high --> active
>
> Thanks, this part looks good in the below documentation update.
>
> > - Correct CMOS-compatible clock pin from MCLK2 to MCLK1.
>
> I haven't checked driver yet, but is it only for a single component?
> Can you double check that _all_ supported by the driver have the same
> in their datasheet(s)?
>
> ...
Hi Ammar,
Just a quick note to say I'm going to mark this one in patchwork
as needing a new version given Andy's questions have been here a while.
Thanks,
Jonathan
>
> > +- When CLKSEL pin is ACTIVE: Uses internal 4.92MHz clock (no clock property
> > needed)
> > -- When CLKSEL pin is tied HIGH: Requires external clock source
> > +- When CLKSEL pin is INACTIVE: Requires external clock source
> > - Can be a crystal between MCLK1 and MCLK2 pins
> > - - Or a CMOS-compatible clock driving MCLK2 pin
> > + - Or a CMOS-compatible clock driving MCLK1 pin and MCLK2 left unconnected
> > - Must specify the "clocks" property in device tree when using external clock
>
next prev parent reply other threads:[~2026-03-22 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 19:08 [PATCH v2] Docs: iio: ad7191 Correct clock configuration Ammar Mustafa
2026-02-28 10:50 ` Andy Shevchenko
2026-03-22 12:13 ` Jonathan Cameron [this message]
2026-03-26 22:04 ` Ammar Mustafa
2026-03-27 7:31 ` 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=20260322121314.0143bda3@jic23-huawei \
--to=jic23@kernel.org \
--cc=alisa.roman@analog.com \
--cc=ammarmustafa34@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=skhan@linuxfoundation.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