From: Jonathan Cameron <jic23@kernel.org>
To: Eason Yang <j2anfernee@gmail.com>
Cc: avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, lars@metafoo.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, nuno.sa@analog.com,
dlechner@baylibre.com, javier.carrasco.cruz@gmail.com,
andriy.shevchenko@linux.intel.com, marcelo.schmitt@analog.com,
olivier.moysan@foss.st.com, mitrutzceclan@gmail.com,
tgamblin@baylibre.com, matteomartelli3@gmail.com,
alisadariana@gmail.com, gstols@baylibre.com,
thomas.bonnefille@bootlin.com, ramona.nechita@analog.com,
mike.looijmans@topic.nl, chanh@os.amperecomputing.com,
KWLIU@nuvoton.com, yhyang2@nuvoton.com, openbmc@lists.ozlabs.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: adc: add Nuvoton NCT720x ADC driver
Date: Sun, 8 Dec 2024 17:22:36 +0000 [thread overview]
Message-ID: <20241208172236.18441e64@jic23-huawei> (raw)
In-Reply-To: <20241203091540.3695650-3-j2anfernee@gmail.com>
On Tue, 3 Dec 2024 17:15:40 +0800
Eason Yang <j2anfernee@gmail.com> wrote:
> Add Nuvoton NCT7201/NCT7202 system voltage monitor 12-bit ADC driver
>
> NCT7201/NCT7202 supports up to 12 analog voltage monitor inputs and up to
> 4 SMBus addresses by ADDR pin. Meanwhile, ALERT# hardware event pins for
> independent alarm signals, and the all threshold values could be set for
> system protection without any timing delay. It also supports reset input
> RSTIN# to recover system from a fault condition.
>
> Currently, only single-edge mode conversion and threshold events support.
>
> Signed-off-by: Eason Yang <j2anfernee@gmail.com>
Hi Eason,
Given you have some good reviews already I only took a very quick glance
through. A few things inline
Jonathan
> diff --git a/drivers/iio/adc/nct720x.c b/drivers/iio/adc/nct720x.c
> new file mode 100644
> index 000000000000..b28b5f4d7d70
> --- /dev/null
> +++ b/drivers/iio/adc/nct720x.c
> +
> +static int nct720x_write_event_value(struct iio_dev *indio_dev,
> + const struct iio_chan_spec *chan,
> + enum iio_event_type type,
> + enum iio_event_direction dir,
> + enum iio_event_info info,
> + int val, int val2)
> +{
> + struct nct720x_chip_info *chip = iio_priv(indio_dev);
> + int index, err = 0;
> + long v1, v2, volt;
> +
> + index = nct720x_chan_to_index[chan->address];
> + volt = (val * NCT720X_IN_SCALING_FACTOR) / NCT720X_IN_SCALING;
> + v1 = volt >> 5;
> + v2 = (volt & REG_VIN_LIMIT_LSB_MASK) << 3;
> +
> + if (chan->type != IIO_VOLTAGE)
> + return -EOPNOTSUPP;
> +
> + if (info == IIO_EV_INFO_VALUE) {
> + if (dir == IIO_EV_DIR_FALLING) {
> + guard(mutex)(&chip->access_lock);
Might as well move this up one level as it is called in both legs.
> + err = regmap_write(chip->regmap, REG_VIN_LOW_LIMIT[index], v1);
> + if (err < 0)
> + dev_err(&indio_dev->dev, "Failed to write REG_VIN%d_LOW_LIMIT\n",
> + index + 1);
> +
> + err = regmap_write(chip->regmap, REG_VIN_LOW_LIMIT_LSB[index], v2);
> + if (err < 0)
> + dev_err(&indio_dev->dev, "Failed to write REG_VIN%d_LOW_LIMIT_LSB\n",
> + index + 1);
> +
> + } else {
> + guard(mutex)(&chip->access_lock);
> + err = regmap_write(chip->regmap, REG_VIN_HIGH_LIMIT[index], v1);
> + if (err < 0)
> + dev_err(&indio_dev->dev, "Failed to write REG_VIN%d_HIGH_LIMIT\n",
> + index + 1);
> +
> + err = regmap_write(chip->regmap, REG_VIN_HIGH_LIMIT_LSB[index], v2);
> + if (err < 0)
> + dev_err(&indio_dev->dev, "Failed to write REG_VIN%d_HIGH_LIMIT_LSB\n",
> + index + 1);
> + }
> + }
> + return err;
> +}
> +
> +static const struct iio_info nct720x_info = {
> + .read_raw = nct720x_read_raw,
> + .read_event_config = nct720x_read_event_config,
> + .write_event_config = nct720x_write_event_config,
> + .read_event_value = nct720x_read_event_value,
> + .write_event_value = nct720x_write_event_value,
Given you are supporting with and without interrupts, should probably pick between
versions of this that have the event config part and one that doesn't.
> +};
> +
> +static const struct nct720x_adc_model_data nct7201_model_data = {
> + .model_name = "nct7201",
> + .channels = nct7201_channels,
> + .num_channels = ARRAY_SIZE(nct7201_channels),
> + .vin_max = 8,
> +};
> +
> +static const struct nct720x_adc_model_data nct7202_model_data = {
> + .model_name = "nct7202",
> + .channels = nct7202_channels,
> + .num_channels = ARRAY_SIZE(nct7202_channels),
> + .vin_max = 12,
> +};
> +
> +static int nct720x_init_chip(struct nct720x_chip_info *chip)
> +{
> + u8 data[2];
> + unsigned int value;
> + int err;
> +
> + err = regmap_write(chip->regmap, REG_CONFIGURATION, BIT_CONFIGURATION_RESET);
> + if (err) {
> + dev_err(&chip->client->dev, "Failed to write REG_CONFIGURATION\n");
> + return err;
> + }
> +
> + /*
> + * After about 25 msecs, the device should be ready and then
> + * the Power Up bit will be set to 1. If not, wait for it.
> + */
> + mdelay(25);
> + err = regmap_read(chip->regmap, REG_BUSY_STATUS, &value);
> + if (err < 0)
> + return err;
> + if (!(value & BIT_PWR_UP))
> + return err;
> +
> + /* Enable Channel */
> + err = regmap_write(chip->regmap, REG_CHANNEL_ENABLE_1, REG_CHANNEL_ENABLE_1_MASK);
> + if (err) {
> + dev_err(&chip->client->dev, "Failed to write REG_CHANNEL_ENABLE_1\n");
> + return err;
> + }
> +
> + if (chip->vin_max == 12) {
> + err = regmap_write(chip->regmap, REG_CHANNEL_ENABLE_2, REG_CHANNEL_ENABLE_2_MASK);
> + if (err) {
> + dev_err(&chip->client->dev, "Failed to write REG_CHANNEL_ENABLE_2\n");
> + return err;
> + }
> + }
> +
> + guard(mutex)(&chip->access_lock);
> + err = regmap_read(chip->regmap, REG_CHANNEL_ENABLE_1, &value);
> + if (err < 0)
> + return err;
> + data[0] = (u8)value;
> +
> + err = regmap_read(chip->regmap, REG_CHANNEL_ENABLE_2, &value);
> + if (err < 0)
> + return err;
Here I think you can use a bulk read as the registers are next to each other.
> + data[1] = (u8)value;
> +
> + value = get_unaligned_le16(data);
> + chip->vin_mask = value;
> +
> + /* Start monitoring if needed */
> + err = regmap_read(chip->regmap, REG_CONFIGURATION, &value);
> + if (err < 0) {
> + dev_err(&chip->client->dev, "Failed to read REG_CONFIGURATION\n");
> + return value;
> + }
> +
> + value |= BIT_CONFIGURATION_START;
> + err = regmap_write(chip->regmap, REG_CONFIGURATION, value);
> + if (err < 0) {
> + dev_err(&chip->client->dev, "Failed to write REG_CONFIGURATION\n");
> + return err;
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2024-12-08 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 9:15 [PATCH v2 0/2] iio: adc: add Nuvoton NCT720x ADC driver Eason Yang
2024-12-03 9:15 ` [PATCH v2 1/2] dt-bindings: iio: adc: Add binding for Nuvoton NCT720x ADCs Eason Yang
2024-12-03 9:25 ` Krzysztof Kozlowski
2024-12-04 3:10 ` Yu-Hsian Yang
2024-12-04 7:12 ` Krzysztof Kozlowski
2024-12-04 8:47 ` Yu-Hsian Yang
2024-12-03 9:15 ` [PATCH v2 2/2] iio: adc: add Nuvoton NCT720x ADC driver Eason Yang
2024-12-03 13:50 ` Andy Shevchenko
2024-12-04 3:20 ` Yu-Hsian Yang
2024-12-04 4:27 ` Andy Shevchenko
2024-12-04 9:05 ` Yu-Hsian Yang
2024-12-08 17:16 ` Jonathan Cameron
2024-12-05 18:22 ` David Lechner
2024-12-05 19:01 ` David Lechner
2024-12-10 5:27 ` Yu-Hsian Yang
2024-12-10 5:20 ` Yu-Hsian Yang
2024-12-08 17:22 ` Jonathan Cameron [this message]
2024-12-10 5:38 ` Yu-Hsian Yang
2024-12-10 5:47 ` Yu-Hsian Yang
2024-12-11 18:28 ` Jonathan Cameron
2024-12-11 18:26 ` Jonathan Cameron
2024-12-08 17:47 ` Christophe JAILLET
2024-12-10 5:59 ` Yu-Hsian Yang
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=20241208172236.18441e64@jic23-huawei \
--to=jic23@kernel.org \
--cc=KWLIU@nuvoton.com \
--cc=alisadariana@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=chanh@os.amperecomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gstols@baylibre.com \
--cc=j2anfernee@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=matteomartelli3@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=mitrutzceclan@gmail.com \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=openbmc@lists.ozlabs.org \
--cc=ramona.nechita@analog.com \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tgamblin@baylibre.com \
--cc=thomas.bonnefille@bootlin.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yhyang2@nuvoton.com \
--cc=yuenn@google.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