From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Trevor Gamblin" <tgamblin@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"David Lechner" <dlechner@baylibre.com>,
"Uwe Kleine-Konig" <u.kleine-koenig@baylibre.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 0/3] iio: adc: add new ad7625 driver
Date: Thu, 5 Sep 2024 10:01:19 +0200 [thread overview]
Message-ID: <4d156c5a-daea-4e9a-8623-8042b5fe7911@kernel.org> (raw)
In-Reply-To: <123c8bff-6623-4a3b-a49e-69b3ab6f8ab5@baylibre.com>
On 04/09/2024 21:16, Trevor Gamblin wrote:
>
> On 2024-09-04 3:14 p.m., Trevor Gamblin wrote:
>> This series adds a new driver for the Analog Devices Inc. AD7625,
>> AD7626, AD7960, and AD7961. These chips are part of a family of
>> LVDS-based SAR ADCs. The initial driver implementation does not support
>> the devices' self-clocked mode, although that can be added later.
>>
>> The devices make use of two offset PWM signals, one to trigger
>> conversions and the other as a burst signal for transferring data to the
>> host. These rely on the new PWM waveform functionality being
>> reviewed in [1] and also available at [2].
>>
>> This work is being done by BayLibre and on behalf of Analog Devices
>> Inc., hence the maintainers are @analog.com.
>>
>> Special thanks to David Lechner for his guidance and reviews.
>>
>> [1]: https://lore.kernel.org/linux-pwm/cover.1722261050.git.u.kleine-koenig@baylibre.com
>> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git/log/?h=pwm/chardev
>>
>> Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
> Realizing that I forgot to pick up Conor's Reviewed-by on the v3 binding
> before sending. Can that be picked up?
Only you can run `b4 ty -u`. We cannot.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-05 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 19:14 [PATCH v4 0/3] iio: adc: add new ad7625 driver Trevor Gamblin
2024-09-04 19:14 ` [PATCH v4 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs Trevor Gamblin
2024-09-05 6:35 ` Krzysztof Kozlowski
2024-09-08 11:53 ` Jonathan Cameron
2024-09-04 19:14 ` [PATCH v4 2/3] iio: adc: ad7625: add driver Trevor Gamblin
2024-09-05 7:58 ` Nuno Sá
2024-09-05 16:18 ` Trevor Gamblin
2024-09-07 22:50 ` kernel test robot
2024-09-08 11:59 ` Jonathan Cameron
2024-09-09 13:20 ` Trevor Gamblin
2024-09-04 19:14 ` [PATCH v4 3/3] docs: iio: new docs for ad7625 driver Trevor Gamblin
2024-09-04 19:16 ` [PATCH v4 0/3] iio: adc: add new " Trevor Gamblin
2024-09-05 8:01 ` Krzysztof Kozlowski [this message]
2024-09-05 16:32 ` Trevor Gamblin
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=4d156c5a-daea-4e9a-8623-8042b5fe7911@kernel.org \
--to=krzk@kernel.org \
--cc=Michael.Hennerich@analog.com \
--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=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=u.kleine-koenig@baylibre.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;
as well as URLs for NNTP newsgroup(s).