From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/7] Add serio start() and stop() methods
Date: Fri, 12 Nov 2004 01:29:56 -0500 [thread overview]
Message-ID: <200411120129.58520.dtor_core@ameritech.net> (raw)
In-Reply-To: <200411120129.04300.dtor_core@ameritech.net>
===================================================================
ChangeSet@1.1986, 2004-11-11 23:04:12-05:00, dtor_core@ameritech.net
Input: add serio->start() and serio->stop() callback methods that
are called whenever serio port is finishes being registered
or unregistered. The callbacks are useful for drivers that
share interrupt between several ports and there is a danger
that interrupt handler will reference port that was just
unregistered.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
drivers/input/serio/serio.c | 8 +++++++-
include/linux/serio.h | 2 ++
2 files changed, 9 insertions(+), 1 deletion(-)
===================================================================
diff -Nru a/drivers/input/serio/serio.c b/drivers/input/serio/serio.c
--- a/drivers/input/serio/serio.c 2004-11-12 01:00:20 -05:00
+++ b/drivers/input/serio/serio.c 2004-11-12 01:00:20 -05:00
@@ -328,7 +328,10 @@
serio->dev.release = serio_release_port;
if (serio->parent)
serio->dev.parent = &serio->parent->dev;
- device_register(&serio->dev);
+ device_initialize(&serio->dev);
+ if (serio->start)
+ serio->start(serio);
+ device_add(&serio->dev);
}
/*
@@ -350,6 +353,9 @@
up_write(&serio_bus.subsys.rwsem);
put_driver(&drv->driver);
}
+
+ if (serio->stop)
+ serio->stop(serio);
if (serio->parent) {
spin_lock_irqsave(&serio->parent->lock, flags);
diff -Nru a/include/linux/serio.h b/include/linux/serio.h
--- a/include/linux/serio.h 2004-11-12 01:00:20 -05:00
+++ b/include/linux/serio.h 2004-11-12 01:00:20 -05:00
@@ -42,6 +42,8 @@
int (*write)(struct serio *, unsigned char);
int (*open)(struct serio *);
void (*close)(struct serio *);
+ int (*start)(struct serio *);
+ void (*stop)(struct serio *);
struct serio *parent, *child;
next prev parent reply other threads:[~2004-11-12 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 6:27 [PATCH 0/7] New set of input patches Dmitry Torokhov
2004-11-12 6:29 ` [PATCH 1/7] i8042 panicblink code rearrange Dmitry Torokhov
2004-11-12 6:29 ` Dmitry Torokhov [this message]
2004-11-12 6:30 ` [PATCH 3/7] i8042 - use start() and stop() methods Dmitry Torokhov
2004-11-12 6:31 ` [PATCH 4/7] suppress duplicate serio events Dmitry Torokhov
2004-11-12 6:32 ` [PATCH 5/7] evdev_read: report -EINVAL when buffer is to small Dmitry Torokhov
2004-11-12 6:33 ` [PATCH 6/7] Correctly set mouse name when using PS2++ protocol Dmitry Torokhov
2004-11-12 6:34 ` [PATCH 7/7] Limit Synaptics rate on Toshibas Dmitry Torokhov
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=200411120129.58520.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.