From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/19] New set of input patches
Date: Mon, 28 Jun 2004 07:54:53 -0700 (PDT) [thread overview]
Message-ID: <20040628145454.9403.qmail@web81305.mail.yahoo.com> (raw)
Vojtech Pavlik wrote:
> On Mon, Jun 28, 2004 at 02:13:58AM -0500, Dmitry Torokhov wrote:
>
> > > IMO drivers have no bussiness messing with the serio locks. We could
> use
> > > 'plug' and 'unplug' functions like the network driver use, or handle
> it
> > > inside the driver, but taking the lock is the wrong thing to do.
> >
> > OK, I just don't want to introduce another lock just for that...
>
> I think a bit in flags "PSMOUSE_ENABLED", like we have the
> "ATKBD_ENABLED" bit might be just fine - handle the interrupt, but throw
> away the data during the protocol switch. We aren't interested in the
> data anyway.
>
But the flag will not give you atomicity of resetting other fields, like
pktcount. I guess we can ensure it by carefully rearranging the states
and what is reset at what point but it is too fragile.
Would you accept a pair serio_rx_suspend/serio_rx_resume that would still
take the lock internally but not expose this fact to the driver?
> > > > 15-synaptics-passthrough-handling.patch
> > > > - If data looks like a pass-through packet and tuchpad has
> > > > pass-through capability do not pass it to the main handler
> > > > if child port is disconnected.
> > >
> > > I'll have to look closer on this one - I think we want to pass the
> data
> > > to the serio layer even if there is no driver listening on the
> > > passthrough serio.
> >
> > We probably should issue serio_interrupt on child port to force rescan
> but
> > that packet has no business in parent's motion handling routine and
> that's
> > what this patch tries to fix. Anyway, I will look at it more later.
>
> Indeed, we need it for the rescan. It shouldn't be that hard to fix at
> once.
>
Ok
> >
> > > > (*) These patches have also been sent to Greg KH.
> > >
> > > Did he accept them already?
> >
> > No, not yet. He promised to take a look at
> platoform_device_register_simple by
> > the end of the week but I guess kernel.bkbits.net troubles might
> intervene...
> > And other 2 I just send out today.
>
> Ok. I'll wait then.
Sysfs changes should be useable even without platform device changes
and I would like start syncing with you. Would you take patches 2
through 10 (I will drop the legacy_position stuff)?
--
Dmitry
next reply other threads:[~2004-06-28 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 14:54 Dmitry Torokhov [this message]
2004-06-28 15:07 ` Vojtech Pavlik
2004-06-29 7:01 ` Dmitry Torokhov
2004-06-29 7:25 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2004-06-28 10:05 Sau Dan Lee
2004-06-28 5:08 Dmitry Torokhov
2004-06-28 6:52 ` Vojtech Pavlik
2004-06-28 7:13 ` Dmitry Torokhov
2004-06-28 7:51 ` Vojtech Pavlik
2004-06-28 10:32 ` Neil Brown
2004-06-28 12:13 ` 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=20040628145454.9403.qmail@web81305.mail.yahoo.com \
--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 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®