From: Antoniu Miclaus <antoniu.miclaus@analog.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Antoniu Miclaus <antoniu.miclaus@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dragos Bogdan <dragos.bogdan@analog.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] *** Add ADF4378 Support ***
Date: Mon, 29 Jul 2024 12:50:42 +0300 [thread overview]
Message-ID: <20240729095047.25040-1-antoniu.miclaus@analog.com> (raw)
Add support for ADF4378 high performance, ultra-low jitter, integer-N
phased locked loop (PLL) with an integrated voltage controlled
oscillator (VCO) and system reference (SYSREF) retimer ideally
suited for data converter and mixed signal front end (MxFE) clock
applications.
The main difference between ADF4377 and ADF4378 is that the second one
provides only one output frequency channel which is enable/disabled via
one GPIO.
Both the driver and the bindings are updated to reflect that difference.
Antoniu Miclaus (2):
dt-bindings: iio: adf4377: add adf4378 support
iio: frequency: adf4377: add adf4378 support
.../bindings/iio/frequency/adi,adf4377.yaml | 10 ++++++
drivers/iio/frequency/adf4377.c | 35 +++++++++++++++----
2 files changed, 38 insertions(+), 7 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-29 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 9:50 Antoniu Miclaus [this message]
2024-07-29 9:50 ` [PATCH v3 1/2] dt-bindings: iio: adf4377: add adf4378 support Antoniu Miclaus
2024-07-30 8:44 ` Krzysztof Kozlowski
2024-07-29 9:50 ` [PATCH v3 2/2] iio: frequency: " Antoniu Miclaus
2024-07-29 14:58 ` [PATCH v3 0/2] *** Add ADF4378 Support *** Krzysztof Kozlowski
2024-07-30 8:23 ` Miclaus, Antoniu
2024-07-30 8:42 ` Krzysztof Kozlowski
2024-07-30 18: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=20240729095047.25040-1-antoniu.miclaus@analog.com \
--to=antoniu.miclaus@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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