From: David Brownell <david-b@pacbell.net>
To: jt@hpl.hp.com
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [patch 2.6.17-rc3] smsc-ircc2, minimal PNP hotplug support
Date: Mon, 1 May 2006 13:13:43 -0700 [thread overview]
Message-ID: <200605011313.43625.david-b@pacbell.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 39 bytes --]
An old laptop now behaves more sanely.
[-- Attachment #2: ir-smsc.patch --]
[-- Type: text/x-diff, Size: 1317 bytes --]
Minimal PNP hotplug support for the smsc-ircc2 driver. A modular driver
will be modprobed via hotplug, but still bypasses driver model probing.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Index: linux/drivers/net/irda/smsc-ircc2.c
===================================================================
--- linux.orig/drivers/net/irda/smsc-ircc2.c 2006-04-23 23:23:38.000000000 -0700
+++ linux/drivers/net/irda/smsc-ircc2.c 2006-04-28 21:42:14.000000000 -0700
@@ -54,6 +54,7 @@
#include <linux/rtnetlink.h>
#include <linux/serial_reg.h>
#include <linux/dma-mapping.h>
+#include <linux/pnp.h>
#include <linux/platform_device.h>
#include <asm/io.h>
@@ -358,6 +360,16 @@
iobase + IRCC_MASTER);
}
+#ifdef CONFIG_PNP
+/* PNP hotplug support */
+static const struct pnp_device_id smsc_ircc_pnp_table[] = {
+ { .id = "SMCf010", .driver_data = 0 },
+ /* and presumably others */
+ { }
+};
+MODULE_DEVICE_TABLE(pnp, smsc_ircc_pnp_table);
+#endif
+
/*******************************************************************************
*
@@ -2072,7 +2084,8 @@
/* PROBING
*
- *
+ * REVISIT we can be told about the device by PNP, and should use that info
+ * instead of probing hardware and creating a platform_device ...
*/
static int __init smsc_ircc_look_for_chips(void)
next reply other threads:[~2006-05-01 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 20:13 David Brownell [this message]
2006-05-01 21:10 ` Jean Tourrilhes
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=200605011313.43625.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=jt@hpl.hp.com \
--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
all inboxes | Powered by JetHome®