From: Conor Dooley <conor@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: rodrigo.alencar@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH RFC v2 1/9] dt-bindings: iio: frequency: add ad9910
Date: Fri, 20 Mar 2026 17:14:51 +0000 [thread overview]
Message-ID: <20260320-utensil-estate-ea3af0d8a623@spud> (raw)
In-Reply-To: <zi7ifl45h5fu76rlbdubkeq7wa7gtve5wsdruo574gzj5qbfu6@fl6rh3soaj74>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On Fri, Mar 20, 2026 at 11:21:37AM +0000, Rodrigo Alencar wrote:
> On 26/03/19 05:25PM, Conor Dooley wrote:
> > On Wed, Mar 18, 2026 at 05:56:01PM +0000, Rodrigo Alencar via B4 Relay wrote:
> > > From: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > >
> > > DT-bindings for AD9910, a 1 GSPS DDS with 14-bit DAC. It includes
> > > configurations for clocks, DAC current, reset and basic GPIO control.
> > >
> > > Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
>
> ...
>
> > > +
> > > + clock-names:
> > > + oneOf:
> > > + - items:
> > > + - const: ref_clk
> >
> > s/_clk//, not like it can be anything else!
> >
> > > + - items:
> > > + - const: ref_clk
> > > + - const: sync_in
> > > +
> > > + '#clock-cells':
> > > + const: 1
> > > +
> > > + clock-output-names:
> > > + minItems: 1
> > > + maxItems: 3
> > > + items:
> > > + enum: [ sync_clk, pdclk, sync_out ]
> >
> > I'd say same here, but then you've got some issues with differentiation,
> > so idk.
>
> so I've got the names as they are referred in the device pins in the datasheet
Coming back to this one, ye I think it just is less confusing to keep
the _clk ultimately. This looks good then, I think, modulo the RFC-state
of the series.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2026-03-20 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260318-ad9910-iio-driver-v2-0-e79f93becf11@analog.com>
[not found] ` <20260318-ad9910-iio-driver-v2-1-e79f93becf11@analog.com>
[not found] ` <20260319-annex-varying-afbddcb825b7@spud>
[not found] ` <zi7ifl45h5fu76rlbdubkeq7wa7gtve5wsdruo574gzj5qbfu6@fl6rh3soaj74>
2026-03-20 17:14 ` Conor Dooley [this message]
[not found] ` <20260318-ad9910-iio-driver-v2-2-e79f93becf11@analog.com>
2026-03-22 16:50 ` [PATCH RFC v2 2/9] iio: frequency: ad9910: initial driver implementation Jonathan Cameron
2026-03-23 10:34 ` Rodrigo Alencar
2026-03-23 11:00 ` Andy Shevchenko
[not found] ` <20260318-ad9910-iio-driver-v2-5-e79f93becf11@analog.com>
2026-03-22 17:05 ` [PATCH RFC v2 5/9] iio: frequency: ad9910: add RAM mode support Jonathan Cameron
[not found] ` <20260318-ad9910-iio-driver-v2-8-e79f93becf11@analog.com>
2026-03-22 17:22 ` [PATCH RFC v2 8/9] Documentation: ABI: testing: add docs for ad9910 sysfs entries Jonathan Cameron
2026-03-23 11:36 ` Rodrigo Alencar
2026-04-12 14:51 ` Jonathan Cameron
2026-04-12 18:45 ` David Lechner
[not found] ` <20260318-ad9910-iio-driver-v2-9-e79f93becf11@analog.com>
2026-03-22 17:34 ` [PATCH RFC v2 9/9] docs: iio: add documentation for ad9910 driver Jonathan Cameron
2026-03-23 11:58 ` Rodrigo Alencar
2026-04-12 14:54 ` Jonathan Cameron
[not found] ` <20260318-ad9910-iio-driver-v2-3-e79f93becf11@analog.com>
[not found] ` <abru0mNtpJSPSJux@ashevche-desk.local>
2026-03-22 16:52 ` [PATCH RFC v2 3/9] iio: frequency: ad9910: add simple parallel port mode support Jonathan Cameron
2026-03-23 10:39 ` Rodrigo Alencar
2026-03-23 11:01 ` Andy Shevchenko
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=20260320-utensil-estate-ea3af0d8a623@spud \
--to=conor@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@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