From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Nuno Sa <Nuno.Sa@analog.com>, Matt Ranostay <mranostay@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 7/9] iio: atlas-sensor: Remove no-op trigger ops
Date: Sun, 31 Oct 2021 15:21:28 +0100 [thread overview]
Message-ID: <20211031142130.20791-7-lars@metafoo.de> (raw)
In-Reply-To: <20211031142130.20791-1-lars@metafoo.de>
The IIO core handles a trigger ops with all NULL callbacks the same as if
the trigger ops itself was NULL.
Remove the empty trigger ops from the interrupt trigger driver to slightly
reduce the boilerplate code. Object size of the driver module is also
slightly reduced.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
drivers/iio/chemical/atlas-sensor.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/iio/chemical/atlas-sensor.c b/drivers/iio/chemical/atlas-sensor.c
index 9cb99585b6ff..04b44a327614 100644
--- a/drivers/iio/chemical/atlas-sensor.c
+++ b/drivers/iio/chemical/atlas-sensor.c
@@ -434,9 +434,6 @@ static int atlas_buffer_predisable(struct iio_dev *indio_dev)
return 0;
}
-static const struct iio_trigger_ops atlas_interrupt_trigger_ops = {
-};
-
static const struct iio_buffer_setup_ops atlas_buffer_setup_ops = {
.postenable = atlas_buffer_postenable,
.predisable = atlas_buffer_predisable,
@@ -645,7 +642,6 @@ static int atlas_probe(struct i2c_client *client,
data->client = client;
data->trig = trig;
data->chip = chip;
- trig->ops = &atlas_interrupt_trigger_ops;
iio_trigger_set_drvdata(trig, indio_dev);
i2c_set_clientdata(client, indio_dev);
--
2.20.1
next prev parent reply other threads:[~2021-10-31 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 14:21 [PATCH 1/9] iio: interrupt-trigger: Remove no-op trigger ops Lars-Peter Clausen
2021-10-31 14:21 ` [PATCH 2/9] iio: sysfs-trigger: " Lars-Peter Clausen
2021-10-31 14:21 ` [PATCH 3/9] iio: ad_sigma_delta: " Lars-Peter Clausen
2021-10-31 14:21 ` [PATCH 4/9] iio: afe4403: " Lars-Peter Clausen
2021-10-31 14:21 ` [PATCH 5/9] iio: afe4404: " Lars-Peter Clausen
2021-10-31 14:21 ` [PATCH 6/9] iio: as3935: " Lars-Peter Clausen
2021-10-31 14:21 ` Lars-Peter Clausen [this message]
2021-10-31 14:21 ` [PATCH 8/9] iio: gp2ap020a00f: " Lars-Peter Clausen
2021-11-09 11:01 ` Linus Walleij
2021-10-31 14:21 ` [PATCH 9/9] iio: lmp91000: " Lars-Peter Clausen
2021-11-03 17:54 ` [PATCH 1/9] iio: interrupt-trigger: " Jonathan Cameron
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=20211031142130.20791-7-lars@metafoo.de \
--to=lars@metafoo.de \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@gmail.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