From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: kernel@pengutronix.de, linus.walleij@linaro.org,
bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org
Subject: [PATCH v2 1/2] include: linux: siox: more for declaring siox drivers
Date: Tue, 18 Jun 2019 12:40:26 +0200 [thread overview]
Message-ID: <1560854427-27537-2-git-send-email-info@metux.net> (raw)
In-Reply-To: <1560854427-27537-1-git-send-email-info@metux.net>
From: Enrico Weigelt <info@metux.net>
Add more helper macros for trivial driver init cases, similar to the
already existing module_platform_driver() or module_i2c_driver().
This helps to reduce driver init boilerplate.
Signed-off-by: Enrico Weigelt <info@metux.net>
---
include/linux/siox.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/linux/siox.h b/include/linux/siox.h
index d79624e..d53b2b2 100644
--- a/include/linux/siox.h
+++ b/include/linux/siox.h
@@ -75,3 +75,12 @@ static inline void siox_driver_unregister(struct siox_driver *sdriver)
{
return driver_unregister(&sdriver->driver);
}
+
+/* module_siox_driver() - Helper macro for drivers that don't do
+ * anything special in module init/exit. This eliminates a lot of
+ * boilerplate. Each module may only use this macro once, and
+ * calling it replaces module_init() and module_exit()
+ */
+#define module_siox_driver(__siox_driver) \
+ module_driver(__siox_driver, siox_driver_register, \
+ siox_driver_unregister)
--
1.9.1
next prev parent reply other threads:[~2019-06-18 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 10:40 siox: driver init boilerplate reduction v2 Enrico Weigelt, metux IT consult
2019-06-18 10:40 ` Enrico Weigelt, metux IT consult [this message]
2019-06-18 16:17 ` [PATCH v2 1/2] include: linux: siox: more for declaring siox drivers Uwe Kleine-König
2019-06-24 5:33 ` Enrico Weigelt, metux IT consult
2019-06-18 10:40 ` [PATCH v2 2/2] drivers: gpio: siox: use module_siox_driver() Enrico Weigelt, metux IT consult
2019-06-18 16:13 ` Uwe Kleine-König
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=1560854427-27537-2-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=bgolaszewski@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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).