[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240118085856.70758-1-kimseer.paller@analog.com>
Date: Thu, 18 Jan 2024 16:58:54 +0800
From: Kim Seer Paller <kimseer.paller@...log.com>
To: <linux-iio@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
CC: Jonathan Cameron <jic23@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>,
Michael Hennerich <Michael.Hennerich@...log.com>,
Rob Herring
<robh+dt@...nel.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, "Crt
Mori" <cmo@...exis.com>,
Linus Walleij <linus.walleij@...aro.org>,
"Bartosz
Golaszewski" <brgl@...ev.pl>,
Kim Seer Paller <kimseer.paller@...log.com>
Subject: [PATCH v6 0/2] Changes to admfm2000 driver
Hi all,
Apologies for taking a long time to follow up on this series. I took some time to
test and try out the suggested changes. As for the major change in the bindings
and driver, the array of switch and attenuation GPIOs were moved under child nodes
utilizing the devm_fwnode_gpiod_get_index() for GPIO parsing.
I have just an inquiry regarding the difficulty of implementing the use of
guard(mutex)(&st->lock) for my current controller. Is it okay to simply use the
mutex_lock function instead?
Best regards,
Kim Seer Paller
Kim Seer Paller (2):
dt-bindings: iio: frequency: add admfm2000
iio: frequency: admfm2000: New driver
.../bindings/iio/frequency/adi,admfm2000.yaml | 129 ++++++++
MAINTAINERS | 8 +
drivers/iio/frequency/Kconfig | 10 +
drivers/iio/frequency/Makefile | 1 +
drivers/iio/frequency/admfm2000.c | 307 ++++++++++++++++++
5 files changed, 455 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,admfm2000.yaml
create mode 100644 drivers/iio/frequency/admfm2000.c
base-commit: 296455ade1fdcf5f8f8c033201633b60946c589a
--
2.34.1
Powered by blists - more mailing lists