From: "Phil Endecott" <phil_dubhl_endecott@chezphil.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: Slow boot due perhaps to locks in mouse and platform system
Date: Wed, 15 Oct 2008 10:19:28 +0100 [thread overview]
Message-ID: <1224062368151@dmwebmail.dmwebmail.chezphil.org> (raw)
In-Reply-To: <20081014222222.4260fa48@infradead.org>
Arjan van de Ven wrote:
> On Wed, 15 Oct 2008 00:17:29 +0100
> "Phil Endecott" <phil_dubhl_endecott@chezphil.org> wrote:
>
>>
>> It looks to me as if uhci holds some lock that 8250 needs before it
>> can complete. Now those are both PCI drivers in the same way that
>> the last two that seemed to contend were both input drivers (touchpad
>> and speaker) [hmm, except that as Dmitry pointed out there's a
>> distinction between the platform bus and the serio bus]. Anyway, my
>> ignorant suspicion is that there's some lock related to the bus or
>> subsystem that they both need. Maybe something in sysfs?
>
> it does do this. And I know which lock... and I fixed it ;)
> Just the patch for this is in Gregkh's tree since it's a change to the
> device/sysfs layer and he wanted to carry it via that way.
>
> I can dig that patch out if you want
Yes please!
Phil.
next prev parent reply other threads:[~2008-10-15 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 14:19 Slow boot due perhaps to locks in mouse and platform system Phil Endecott
2008-10-14 14:54 ` Dmitry Torokhov
2008-10-14 15:12 ` Arjan van de Ven
2008-10-14 15:29 ` Dmitry Torokhov
2008-10-14 15:37 ` Arjan van de Ven
2008-10-14 23:17 ` Phil Endecott
2008-10-15 2:22 ` Arjan van de Ven
2008-10-15 9:19 ` Phil Endecott [this message]
2008-10-22 23:07 ` Phil Endecott
2008-10-14 15:37 ` Arjan van de Ven
2008-10-14 15:48 ` Dmitry Torokhov
2008-10-14 15:58 ` Arjan van de Ven
2008-10-14 16:18 ` Phil Endecott
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=1224062368151@dmwebmail.dmwebmail.chezphil.org \
--to=phil_dubhl_endecott@chezphil.org \
--cc=arjan@infradead.org \
--cc=linux-input@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 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.