From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
David Brownell <david-b@pacbell.net>,
linux-usb-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Early USB handoff
Date: Thu, 02 Sep 2004 19:43:29 +0100 [thread overview]
Message-ID: <1094150607.5645.26.camel@localhost.localdomain> (raw)
In-Reply-To: <5F106036E3D97448B673ED7AA8B2B6B30162E74A@scl-exch2k.phoenix.com>
On Iau, 2004-09-02 at 20:03, Aleksey Gorelov wrote:
> Basically, in a case of legacy free BIOS, HC is not in
> SMM mode, and USB IRQ is routed to PCI IRQ line and generates
> interrupts. When this IRQ is enabled in PIC (by driver that
> starts before HC driver), system is flooded with interrupts.
The BIOS should not be leaving the device generating interrupts surely ?
If that IRQ line ends up shared we are in trouble at boot time.
> One solution is to reset HC, but it takes some time (at
> least 50ms). I agree that it might duplicate SOME code in HC
> driver, but HC init executes too late. Well, if handoff has
> been done early, it might not be necessary to do the same in
> HC driver.
We don't always want to hand off. Some setups only work in USB legacy
mode because of other bugs. Thats why the SMM fixup I did for E750x is
triggered in specific cases. We can do such things with DMI table
blacklists easily enough.
My E750x fix already duplicates some of the hand off code so we are
going to need it anyway and if there are more reasons for needing it
then so be it. I happened to only need to fix UHCI thats all.
Alan
next prev parent reply other threads:[~2004-09-02 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:03 [PATCH] Early USB handoff Aleksey Gorelov
2004-09-02 18:43 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 20:26 Aleksey Gorelov
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=1094150607.5645.26.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Aleksey_Gorelov@Phoenix.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=zaitcev@redhat.com \
/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