Apparently there is an issue w/ the IBM x440/x445's BIOS's USB
Legacy support. Due to the delay in issuing SMI's across the IOAPICs,
its possible for I/O to ports 60/64 to cause register corruption.

The solution is to disable the BIOS's USB Legacy support early in
boot(via PCI quirks) for x440/x445 systems.

Originally written by Vojtech against SuSE's tree, this patch was then
updated to disable EHCI by Aleksey Gorelov, cleaned up by Pete Zaitcev
for 2.4 and finally tweaked and updated against 2.6 by me.

I've lightly tested this version of the patch, but it differs little
from what Aleksey, Pete and I have been testing for 2.4.
Signed-off-by: John Stultz <jstultz@us.ibm.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

I've discussed this with Vojtech. If I brake the probe method,
I can also break the rest ;-)
Signed-Off-By: Oliver Neukum <oliver@neukum.name>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


  - new cdc acm maintainer

This removes the "don't run on OMAP 1510" constraint from the
driver and teaches it how not to use registers only available on
newer chips.  It's effectively just a compile fix, though ... hasn't
got any board support yet.


Basic build fixes for the OMAP 1510/5910.  This first generation chip
doesn't include an OTG controller.  The patch makes the driver stop
using OTG registers, and adds some #defines that will be needed to
support boards using those chips.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Fix the hub probe logic so that when khubd wakes up, it will actually
look at all ports on the new hub.  This resolved a root hub enumeration
issue, and I expect the "boot from USB disk" folk will like this too.

The fix includes cleanup: centralizing the logic to make khubd look
at a given hub, instead of cloning it three times (or in the case of
hub probing, frankensteining it).

This also adds a FIXME to the new routine centralizing disconnect
processing:  we also want "power down port but don't wake khubd"
(for PM_SUSPEND_DISK as well as SRP).
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Small bugfixes, at least one of which gets rid of  some
rather random behavior from certain board init
behaviors.


OHCI updates:

 - Bugfix the code taking frame clock adjustments from the boot loader.
   A recent change had a bug which caused inconsistent failures on some
   OHCI configs, including amd756.  Thanks to <pacman@manson.clss.net>
   for tracking down the specifics.

 - From Lothar Wassmann <lk@karo-electronics.de> two fixes:
     (a) don't let tick clock sign-extend, that can make unlinks
         take excessively long (could happen easily enough);
     (b) when re-activating schedules after suspend, use the right
         bitmask (rare/exotic)

 - When suspending the root hub, mark it as USB_STATE_SUSPENDED
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This adds recognition of one more UDC driver.
(Driver is available separately.)


Tell gadget drivers about the National 9603/9604 UDC.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch is mostly cleanup, but it all helps make PM_SUSPEND_DISK
start to behave better.


This exports the new usb_set_device_state() routine for the virtual root
hubs, and uses it in OHCI during resume after power-off to replace some
HC-private code doing almost the same thing.

Note that all HCDs will likely need the same kind of suspend-to-disk
support (though it's different when BIOS kicks in).  Some systems
even power-off during suspend-to-ram (to save extra power), which is
why OHCI already has this logic!

Related updates:

 - Use usb_set_device_state() immediately when an HC dies, making khubd
   handle disconnect processing instead of a workqueue.  So now drivers
   won't self-deadlock in this should-be-rare path, when disconnect()
   calls flush_scheduled_work().

 - Don't warn about "Unlink after no-IRQ" for the the root hub's status
   URB ... like when suspending an HCD that never enumerated a device.

 - Minor IRQ handler cleanup, including more accurate tracking of whether
   this driver ever returned IRQ_HANDLED (shared IRQs don't count).
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Thanks to Tom Hughes for jogging my memory about this patch, which has
been sitting here waiting for Greg's return.  It adds an unusual_devs.h
entry for the Panasonic DMC-LCx line of cameras, which incorrectly report
the total number of blocks in response to READ CAPACITY rather than the
highest available block number.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

On Thursday 09 September 2004 08:38, Greg KH wrote:
> On Thu, Sep 09, 2004 at 01:07:05AM -0400, Gene Heskett wrote:
> > Greetings;
> >
> > I just had to reboot back to -mm2 after playing with some printer configs
> > in cups, although the test pages worked, so I'm not sure what this all
> > about, from var log/messages:
> >
> > Sep  8 23:13:42 coyote cups: cupsd -HUP succeeded
> > Sep  8 23:13:43 coyote kernel: usb_unlink_urb() is deprecated for
> > synchronous unlinks.  Use usb_kill_urb() Sep  8 23:13:43 coyote kernel:
> > Badness in usb_unlink_urb at drivers/usb/core/urb.c:456 Sep  8 23:13:44
> > coyote kernel:  [<c01048ce>] dump_stack+0x1e/0x20 Sep  8 23:13:44 coyote
> > kernel:  [<c0295f35>] usb_unlink_urb+0x85/0xa0 Sep  8 23:13:44 coyote
> > kernel:  [<c02a7447>] usblp_unlink_urbs+0x17/0x40 Sep  8 23:13:44 coyote
> > kernel:  [<c02a74a8>] usblp_release+0x38/0x60 Sep  8 23:13:44 coyote
> > kernel:  [<c01501ea>] __fput+0x12a/0x140
> > Sep  8 23:13:44 coyote kernel:  [<c014e8e7>] filp_close+0x57/0x80
> > Sep  8 23:13:44 coyote kernel:  [<c014e971>] sys_close+0x61/0x90
> > Sep  8 23:13:44 coyote kernel:  [<c010425d>] sysenter_past_esp+0x52/0x71
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

As you requested, this patch updates the documented procedure for
submitting new unusual_devs.h entries.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch adds minimal USB On-The-Go support (mainly just an extra
descriptor) to the File-Storage Gadget.  The changes were based on the
additions made to the Gadget Zero driver.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

The usb-storage driver 'fixes up' the INQUIRY data returned by a device so
that it reads SCSI rev 2 by intercepting the data in-flight.  This was done
to make various SCSI drivers (sd, sr, etc.) work with the device.

However, this technique also has the unfortunate side-effect that nobody
can see the real rev. -- not even sg users.

This patch changes that.  Now, the SCSI revision is changed in the
slave_configure() function.  Thus, the 'real' data is available to anyone
who wants to issue an INQUIRY directly via any means.

This also simplifies the code somewhat.
Signed-off-by: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Bug found by Coverity:
http://linuxbugs.coverity.com/external/editbugparent.php?viewbugid=2137&checkers%5B%5D=all&status%5B%5D=BUG&status%5B%5D=UNINSPECTED&status%5B%5D=UNKNOWN&status%5B%5D=DON%27T%20CARE&status%5B%5D=PENDING&product%5B%5D=all&component%5B%5D=all&file=&fn=&sortby=reverse_rank&before=&after=&curpage=2&bugid=-1&comment=&reason=Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

From: Steffen Zieger <lkml@steffenspage.de>

Here is a patch to get the kernel module from Codemerces to work.  The module
is available in source for the 2.4 and 2.6 series except the needed changes in
hid-core.c.  Codemercs distribute the needed changes as a complete file
(version 2.6.4).  This isn't working with 2.6.8.1.

http://www.codemercs.comSigned-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This addresses an SMP-only issue with the EHCI driver, where only one CPU
should scan the schedule at a time (scanning is not re-entrant) but either
the IRQ handler or a watchdog timer could end up starting it.  Many thanks
to Olaf Hering for isolating the failure mode, and testing this fix!

Once once CPU starts scanning, any other might as well finish right
away.  This fix just adds a flag to detect that case.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Changes:

- Add support for SN9C103 based devices. The audio capability is already
  supported but not released in this version. I will release
  it once someone donates two SN9C103 based devices.
- Implement VIDIOC_G_CTRL for TAS5110C1B and TAS51130D1B
- Replace "SN9C10[12]" strings with "SN9C10x"
- Add red, green, blue gain controls to the SN9C103
- Memory offsets are now page-aligned
- Fix typos in the documentation
- Documentation updates
- Setting bounds are checked by the core module
- Add exposure control for TAS51130D1B
Signed-off-by: Luca Risolia <luca.risolia@studio.unibo.it>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch changes a couple of new routines in the suspend/resume code.
Internally they use port numbers starting from 1, unlike every other
routine in the hub driver.  This changes the port numbers to origin-0, for
consistency's sake.  Of course, messages sent to the system log will
continue to start counting from 1.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This patch takes some code that was only used in one place in the hub
driver, and packages it up into a subroutine which is now called from
several places.  The routine does a logical disconnect -- for example,
after issuing a port reset, if the device descriptors have changed
(because of a firmware update perhaps) we logically disconnect the old
device structure and create a new one.  Or if a resume fails for any
reason we can do the same thing.

This touches some of David Brownell's suspend/resume code, obviously.
(It also fixes a couple of small errors in there.)  He has said it looks
okay.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Make code more readable with list_for_each_entry.
Compile tested.
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Make code more readable with list_for_each_entry.
Compile tested.
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>