From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
wsa@the-dreams.de, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: [PATCH 1/3] include: linux: i2c: more helpers for declaring i2c drivers
Date: Mon, 17 Jun 2019 20:39:37 +0200 [thread overview]
Message-ID: <1560796779-17117-1-git-send-email-info@metux.net> (raw)
From: Enrico Weigelt <info@metux.net>
Add more helper macros for trivial driver init cases, similar to the
already existing module_i2c_driver()+friends - now for those which
are initialized at other stages (eg. by subsys_initcall()).
This helps to further reduce driver init boilerplate.
Signed-off-by: Enrico Weigelt <info@metux.net>
---
include/linux/i2c.h | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/include/linux/i2c.h b/include/linux/i2c.h
index 1308126..fee59bd 100644
--- a/include/linux/i2c.h
+++ b/include/linux/i2c.h
@@ -920,6 +920,23 @@ static inline u8 i2c_8bit_addr_from_msg(const struct i2c_msg *msg)
#define builtin_i2c_driver(__i2c_driver) \
builtin_driver(__i2c_driver, i2c_add_driver)
+/* subsys_i2c_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 subsys_initcall() and module_exit()
+ */
+#define subsys_i2c_driver(__i2c_driver) \
+static int __init __i2c_driver##_init(void) \
+{ \
+ return i2c_add_driver(&(__i2c_driver)); \
+} \
+subsys_initcall(__i2c_driver##_init); \
+static void __exit __i2c_driver##_exit(void) \
+{ \
+ i2c_del_driver(&(__i2c_driver)); \
+} \
+module_exit(__i2c_driver##_exit);
+
#endif /* I2C */
#if IS_ENABLED(CONFIG_OF)
--
1.9.1
next reply other threads:[~2019-06-17 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:39 Enrico Weigelt, metux IT consult [this message]
2019-06-17 18:39 ` [PATCH 2/3] drivers: gpio: pca953x: use subsys_i2c_driver() Enrico Weigelt, metux IT consult
2019-06-17 18:39 ` [PATCH 3/3] drivers: gpio: pcf857x: " Enrico Weigelt, metux IT consult
2019-06-21 21:17 ` [PATCH 1/3] include: linux: i2c: more helpers for declaring i2c drivers Wolfram Sang
2019-06-24 5:44 ` Enrico Weigelt, metux IT consult
2019-06-24 8:44 ` Wolfram Sang
2019-06-24 8:59 ` Enrico Weigelt, metux IT consult
2019-08-16 19:56 ` Wolfram Sang
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=1560796779-17117-1-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).