| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
the illusion of a tunable setting but was always turned on regardless.
MFC after: 1 week
|
|
|
|
| |
Submitted by: Dmitry Luhtionov @ gmail.com
|
|
|
|
|
|
|
|
| |
Andrew Turner. The kernel supports the LN2410SBC evaluation board,
and likely others. These parts (or similar ones) are in some open
hardware designs for phones.
Submitted by: Andrew Turner
|
|
|
|
|
|
| |
because the chip doesn't do this by itself.
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: Giovanni Trematerra
|
|
|
|
|
|
| |
their software.
Obtained from: NetBSD
|
|
|
|
|
|
| |
the hardware to stall.
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Reviewed by: hps
|
|
|
|
|
| |
Submitted by: Marc Balmer <marc@msys.ch>
MFC after: 1 week
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: mitya_cabletv.dp.ua
|
|
|
|
| |
Submitted by: mitya_cabletv.dp.ua
|
|
|
|
|
|
| |
message has been printed is enough to get someones attention. Also remove the
line number for DPRINTF/DPRINTFN, it already prints the funtion name and a
unique message.
|
|
|
|
|
|
|
| |
isnt actually compiled in (or kldloaded) as the controller could cause spurious
interrupts.
Tested by: Florian Smeets
|
|
|
|
| |
Reviewed by: HPS
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
| |
Submitted by: Andriy Gapon
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
| |
endpoint rather than per xfer and provide functions around get/free of resources.
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
| |
but needs intervalling 1:2, 1:4 or 1:8
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some EHCI chips from VIA / ATI seem to trigger interrupts before writing back
the qTD status, or miss signalling occasionally under heavy load. If the host
machine is too fast, we can miss transaction completion - when we scan the
active list the transaction still seems to be active. This generally exhibits
itself as a umass stall that never recovers.
We work around this behaviour by setting up this callback after any softintr
that completes with transactions still pending, giving us another chance to
check for completion after the writeback has taken place
Submitted by: Alexander Nedotsuko
MFC after: 3 days
|
|
|
|
|
|
|
| |
ehci_reset() was called before ehci_init().
PR: usb/140242
Submitted by: Sebastian Huber
|
|
|
|
|
|
|
| |
hw.pci.usb_early_takeover is set to zero and the SMM release
is never done.
Pointed out by: marcel
|
|
|
|
|
| |
Reminded by: jhb
Reviewed by: HPS
|
|
|
|
|
|
|
|
|
| |
all host controllers at the same time, we avoid problems where the BIOS will
actually write to the USB registers of all the USB host controllers every time
we handover one of them, and consequently reset the OS programmed values.
Submitted by: avg
Reviewed by: jhb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The EHCI HW can use the qtd_next field instead of qtd_altnext when a short
packet is received. This contradicts what is stated in the EHCI datasheet.
Also the total-bytes field in the status field of the following TD gets
corrupted upon reception of a short packet! We work this around in software by
not queueing more than one job/TD at a time of up to 16Kbytes! The bug has been
seen on multiple INTEL based EHCI chips. Other vendors have not been tested
yet.
- Applications using /dev/usb/X.Y.Z, where Z is non-zero are affected, but not
applications using LibUSB v0.1, v1.2 and v2.0.
- Mass Storage (umass) is affected.
Submitted by: Hans Petter Selasky
MFC after: 3 days
|
|
|
|
| |
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
| |
statements to zero.
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
|
| |
- Add quirk for ATI SB600 and SB700 to free SMB controller
- Correct schedule sleep time to 10us on the VIA ehci controller
Reported by: Dorian B<FC>ttner, Andriy Gapon
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- clean up USB detach logic. There seems to be some problems detaching multiple
USB HUBs connected in series from the root.
- after this patch the rule is:
1) Always use device_detach() on the USB HUB first.
2) Never just device_delete_child() on the USB HUB, because that function
will traverse to all the device leaves and free them first, and then the USB
stack will free the devices twice which doesn't work very well.
- make sure the did DMA delay gets set after the timeout has elapsed to make
logic more clear. There is no functional difference.
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
| |
setting a sysctl/tunable at boot
- remove some redundant initial explore code
Submitted by: hps
|
|
|
|
|
|
| |
reintroduced after HEAD is reopened for commits by re@.
Approved by: re (kib), attilio
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The newbus lock is responsible for protecting newbus internIal structures,
device states and devclass flags. It is necessary to hold it when all
such datas are accessed. For the other operations, softc locking should
ensure enough protection to avoid races.
Newbus lock is automatically held when virtual operations on the device
and bus are invoked when loading the driver or when the suspend/resume
take place. For other 'spourious' operations trying to access/modify
the newbus topology, newbus lock needs to be automatically acquired and
dropped.
For the moment Giant is also acquired in some key point (modules subsystem)
in order to avoid problems before the 8.0 release as module handlers could
make assumptions about it. This Giant locking should go just after
the release happens.
Please keep in mind that the public interface can be expanded in order
to provide more support, if there are really necessities at some point
and also some bugs could arise as long as the patch needs a bit of
further testing.
Bump __FreeBSD_version in order to reflect the newbus lock introduction.
Reviewed by: ed, hps, jhb, imp, mav, scottl
No answer by: ariff, thompsa, yongari
Tested by: pho,
G. Trematerra <giovanni dot trematerra at gmail dot com>,
Brandon Gooch <jamesbrandongooch at gmail dot com>
Sponsored by: Yahoo! Incorporated
Approved by: re (ksmith)
|
|
|
|
|
|
|
| |
- allow disabling "root_mount_hold()" by setting "hw.usb.no_boot_wait" sysctl
Submitted by: hps
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
| |
- Add minimum polling support to drive UMASS
and UKBD in case of panic.
- Add extra check to ukbd probe to fix problem about
mouse devices attaching like keyboards.
- P4 ID: 166148
Submitted by: hps
Approved by: re
|
|
|
|
|
|
|
|
|
| |
- patch from Alexander Motin <mav@freebsd.org>
- add more ID's
- P4 ID: 165805
Submitted by: hps
Approved by: re
|
|
|
|
|
|
|
|
|
| |
- Add support for devices that handle set and clear stall in hardware.
- Add missing get timestamp function
- Add more xfer flags
Submitted by: Hans Petter Selasky
Approved by: re (kib)
|
|
|
|
| |
- Reduce the number of headers needed for a usb driver, the common case is just usb.h and usbdi.h
|
| |
|
|
|
|
|
|
|
|
| |
so that it isn't exposured unless needed. In particular this means
that it's easier to tune the memory layout based on board details.
While here, remove inclusion of <machine/intr.h> from mvreg.h. This
also contains exposure to SoC specifics in MI drivers, because NIRQ
depends on the SoC.
|
|
|
|
| |
usb_pipe may be used for a different purpose later on.
|
|
|
|
| |
USB_ADD_BYTES macro.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
transactions.
Submitted by: Hans Petter Selasky
|
|
|
|
|
|
|
| |
FreeBSD does not yet support this platform but it makes it easier to stay in
sync.
Submitted by: Hans Petter Selasky
|