From: Dominik Brodowski <linux@brodo.de>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.5] pcmcia (2/5): add bus_type pcmcia_bus_type
Date: Sat, 22 Mar 2003 17:00:32 +0100 [thread overview]
Message-ID: <20030322160032.GB12342@brodo.de> (raw)
Register a bus_type pcmcia_bus_type. This means the initialization of
the ds module needs to be done in two levels: one quite early
(subsys_initcall) so that drivers may use the bus_type; the other one
must stay that late (late_initcall). As only one initcall can be
specified within one module, some tweaking is needed.
Dominik
diff -ruN linux-original/drivers/pcmcia/ds.c linux/drivers/pcmcia/ds.c
--- linux-original/drivers/pcmcia/ds.c 2003-03-22 16:12:08.000000000 +0100
+++ linux/drivers/pcmcia/ds.c 2003-03-22 16:11:50.000000000 +0100
@@ -881,7 +881,18 @@
/*====================================================================*/
-int __init init_pcmcia_ds(void)
+struct bus_type pcmcia_bus_type = {
+ .name = "pcmcia",
+};
+EXPORT_SYMBOL(pcmcia_bus_type);
+
+static int __init init_pcmcia_bus(void)
+{
+ bus_register(&pcmcia_bus_type);
+ return 0;
+}
+
+static int __init init_pcmcia_ds(void)
{
client_reg_t client_reg;
servinfo_t serv;
@@ -967,11 +978,8 @@
return 0;
}
-late_initcall(init_pcmcia_ds);
-
-#ifdef MODULE
-void __exit cleanup_module(void)
+static void __exit exit_pcmcia_ds(void)
{
int i;
#ifdef CONFIG_PROC_FS
@@ -984,6 +992,23 @@
pcmcia_deregister_client(socket_table[i].handle);
sockets = 0;
kfree(socket_table);
+ bus_unregister(&pcmcia_bus_type);
}
+#ifdef MODULE
+
+/* init_pcmcia_bus must be done early, init_pcmcia_ds late. If we load this
+ * as a module, we can only specify one initcall, though...
+ */
+static int __init init_pcmcia_module(void) {
+ init_pcmcia_bus();
+ return init_pcmcia_ds();
+}
+module_init(init_pcmcia_module);
+
+#else /* !MODULE */
+subsys_initcall(init_pcmcia_bus);
+late_initcall(init_pcmcia_ds);
#endif
+
+module_exit(exit_pcmcia_ds);
diff -ruN linux-original/include/pcmcia/ds.h linux/include/pcmcia/ds.h
--- linux-original/include/pcmcia/ds.h 2003-03-22 16:12:08.000000000 +0100
+++ linux/include/pcmcia/ds.h 2003-03-22 16:12:25.000000000 +0100
@@ -32,6 +32,7 @@
#include <pcmcia/driver_ops.h>
#include <pcmcia/bulkmem.h>
+#include <linux/device.h>
typedef struct tuple_parse_t {
tuple_t tuple;
@@ -143,6 +144,8 @@
#define register_pcmcia_driver register_pccard_driver
#define unregister_pcmcia_driver unregister_pccard_driver
+extern struct bus_type pcmcia_bus_type;
+
#endif /* __KERNEL__ */
#endif /* _LINUX_DS_H */
next reply other threads:[~2003-03-22 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 16:00 Dominik Brodowski [this message]
2003-03-23 4:33 ` Linus Torvalds
2003-03-25 3:39 ` Rusty Russell
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=20030322160032.GB12342@brodo.de \
--to=linux@brodo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®