From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Nuno Sa <nuno.sa@analog.com>,
David Lechner <dlechner@baylibre.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] iio: adc: Support ROHM BD79124 ADC
Date: Tue, 11 Feb 2025 19:19:00 +0000 [thread overview]
Message-ID: <20250211191900.36fdd4d9@jic23-huawei> (raw)
In-Reply-To: <87b712f9-6191-4626-b031-0234379a166c@gmail.com>
> >> +
> >> +static void bd79124_re_enable_hi(struct bd79124_data *data, unsigned int channel)
> >> +{
> >> + int ret, evbit = BIT(IIO_EV_DIR_RISING);
> >> +
> >> + if (!(data->alarm_suppressed[channel] & evbit))
> >> + return;
> >> +
> >> + data->alarm_suppressed[channel] &= (~evbit);
> >> +
> >> + if (!(data->alarm_monitored[channel] & evbit))
> >> + return;
> > This lot is very similar to the lo variant. Can we combine them or
> > use some helper for both?
>
> Initially I did this.
>
> But the code looked a bit dull because the evbitm, alarm-limit array and
> prints depend on the direction. Furthermore, the caller already knows
> the direction (as the caller does also handle directions separately), so
> doing:
>
> foo(dir)
> {
> if (dir == bar)
> ...
> else
> ...
> }
>
> ...
>
> if (dir == bar)
> foo(dir);
> else
> foo(dir);
>
> started to feel just a bit, meh. Hence I separated the stuff to own _lo
> and _hi functions.
Hmm. I was thinking of something like
static void bd79124_re_enable_xx(struct bd79124_data *data, unsigned int channel,
unsigned int reg, u16 limit,
enum iio_event_dir dir)
{
int ret, evbit = BIT(dir);
if (!(data->alarm_suppressed[channel] & evbit))
return;
data->alarm_suppressed[channel] &= (~evbit);
if (!(data->alarm_monitored[channel] & evbit))
return;
ret = bd79124_write_int_to_reg(data, reg, limit);
if (ret)
dev_warn(data->dev, "Low limit enabling failed for channel%d\n",
channel);
}
static void bd71924_reenable_hi(struct bd79124_data *data, unsigned int channel)
{
return bd71924_reenable_x(data, channel, BD79124_GET_HIGH_LIMIT_REG(channel)
data->alarm_r_limit[channel], IIO_EV_DIR_RISING);
}
static void bd71924_reenable_lo(struct bd79124_data *data, unsigned int channel)
{
return bd71924_reenable_x(data, channel, BD79124_GET_LOW_LIMIT_REG(channel)
data->alarm_f_limit[channel], IIO_EV_DIR_FALLING);
}
But I guess not really a saving in the end.
>
>
> >> +
> >> + ret = bd79124_write_int_to_reg(data, BD79124_GET_HIGH_LIMIT_REG(channel),
> >> + data->alarm_r_limit[channel]);
> >> + if (ret)
> >> + dev_warn(data->dev, "High limit enabling failed for channel%d\n",
> >> + channel);
> >> +}
> >
>
> Yours,
> -- Matti
>
>
next prev parent reply other threads:[~2025-02-11 19:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 13:34 [PATCH v2 0/5] Support ROHM BD79124 ADC/GPO Matti Vaittinen
2025-02-05 13:34 ` [PATCH v2 1/5] dt-bindings: " Matti Vaittinen
2025-02-05 20:03 ` Conor Dooley
2025-02-06 8:39 ` Matti Vaittinen
2025-02-06 18:16 ` Conor Dooley
2025-02-05 13:34 ` [PATCH v2 2/5] iio: adc: add helpers for parsing ADC nodes Matti Vaittinen
2025-02-08 16:41 ` Jonathan Cameron
2025-02-11 8:52 ` Matti Vaittinen
2025-02-11 19:07 ` Jonathan Cameron
2025-02-16 17:50 ` David Lechner
2025-02-17 6:29 ` Matti Vaittinen
2025-02-17 16:05 ` David Lechner
2025-02-17 7:08 ` Matti Vaittinen
2025-02-17 14:24 ` Matti Vaittinen
2025-02-05 13:38 ` [PATCH v2 3/5] iio: adc: Support ROHM BD79124 ADC Matti Vaittinen
2025-02-06 22:42 ` kernel test robot
2025-02-08 16:52 ` Jonathan Cameron
2025-02-11 9:06 ` Matti Vaittinen
2025-02-11 19:19 ` Jonathan Cameron [this message]
2025-02-05 13:38 ` [PATCH v2 4/5] MAINTAINERS: Add IIO ADC helpers Matti Vaittinen
2025-02-05 13:38 ` [PATCH v2 5/5] MAINTAINERS: Add ROHM BD79124 ADC/GPO Matti Vaittinen
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=20250211191900.36fdd4d9@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.com \
--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;
as well as URLs for NNTP newsgroup(s).