From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] New input patches
Date: Tue, 21 Sep 2004 14:10:40 +0200 [thread overview]
Message-ID: <20040921121040.GA1603@ucw.cz> (raw)
In-Reply-To: <200409162358.27678.dtor_core@ameritech.net>
On Thu, Sep 16, 2004 at 11:58:27PM -0500, Dmitry Torokhov wrote:
> Hi Vojtech,
>
> I have some more input patches that I would like you to review:
>
> 01-libps2.patch
> - move common code from atkbd and psmouse into one place, create
> ps2dev structure that should be used to build drivers for hardware
> attached to a PS/2 port.
Very nice.
> I think that command processing is now race free - instead of using
> bit operations on flags the ps2_command and ps2_send_byte simply
> take serio->lock (via serio_pause/continue_rx). Since serio->lock
> is also taken by interrupt handler anyway it gives us desired
> serialization. As wakeup routines take a spinlock as well and
> spinlock is guaranteed to be a barrier we should not miss wake up
> events either.
I hope the wait_event* functions also use memory barriers properly, but
they probably must, otherwise they won't be useful, because there we're
accessing the flags variable without a lock.
> 02-serio-pin-driver.patch
> - Add drv_sem to serio structure and implement serio_[un]pin_driver()
> functions. The main purpose is to pin a driver bound to serio port
> when accessing driver's data from sysfs attribute handler; otherwise
> other thread could unbind/unload driver in a middle of processing.
This one looks fine.
> 03-atkbd-sysfs-attr.patch
> - Export extra, scroll, set, softrepeat and softraw atkbd properties
> via sysfs and allow them to be controlled at run time, independently
> for each keyboard.
This bit looks wrong in the patch:
- input_event(&atkbd->dev, EV_MSC, MSC_RAW, code);
+ if (atkbd->softraw)
+ input_event(&atkbd->dev, EV_MSC, MSC_RAW, code);
... we definitely want the RAW codes to be sent when we're not in
softraw mode, because that's when they're passed through keyboard.c to
the console.
So the condition needs to be inverted. However, it's not necessary at
all, since the input layer will not pass the RAW events when the MSC_RAW
bit is not set.
> Now that Linus pulled all pending changes the patches should apply cleanly to
> all trees (his, yours and Andrew's).
Great.
> Please let me know if they are ok and I will push them into my bkbits tree.
I think they're fine except for the above minor bug.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-09-21 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 4:58 [PATCH 0/3] New input patches Dmitry Torokhov
2004-09-17 4:59 ` [PATCH 1/3] libps2.patch Dmitry Torokhov
2004-09-17 5:00 ` [PATCH 2/3] serio-pin-driver.patch Dmitry Torokhov
2004-09-17 5:01 ` [PATCH 3/3] atkbd-sysfs-attr.patch Dmitry Torokhov
2004-09-21 12:10 ` Vojtech Pavlik [this message]
2004-09-21 13:15 ` [PATCH 0/3] New input patches Dmitry Torokhov
2004-09-22 7:12 ` Dmitry Torokhov
2004-09-22 7:30 ` Vojtech Pavlik
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=20040921121040.GA1603@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--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