From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v6 2/2] iio: frequency: adf4350: add clk provider
Date: Mon, 24 Jun 2024 10:09:28 +0200 [thread overview]
Message-ID: <85c7b836721ad49125eebf7498d2d8a9cd15dd64.camel@gmail.com> (raw)
In-Reply-To: <20240622195018.587997ae@jic23-huawei>
On Sat, 2024-06-22 at 19:50 +0100, Jonathan Cameron wrote:
> On Fri, 21 Jun 2024 15:13:59 +0300
> Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
>
> > Add clk provider feature for the adf4350.
> >
> > Even though the driver was sent as an IIO driver in most cases the
> > device is actually seen as a clock provider.
> >
> > This patch aims to cover actual usecases requested by users in order to
> > completely control the output frequencies from userspace.
> >
> > Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> You addressed both of Nuno's comments and I didn't have anything to add,
> so I'll pick this up (can still add a tag though if Nuno wants to give one).
>
Please do.
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
prev parent reply other threads:[~2024-06-24 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 12:13 [PATCH v6 1/2] dt-bindings: iio: adf4350: add clk provider prop Antoniu Miclaus
2024-06-21 12:13 ` [PATCH v6 2/2] iio: frequency: adf4350: add clk provider Antoniu Miclaus
2024-06-22 18:50 ` Jonathan Cameron
2024-06-24 8:09 ` Nuno Sá [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=85c7b836721ad49125eebf7498d2d8a9cd15dd64.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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