Skip to content

Commit 942fc23

Browse files
committed
Add dwc_otg driver
Signed-off-by: popcornmix <[email protected]> usb: dwc: fix lockdep false positive Signed-off-by: Kari Suvanto <[email protected]> usb: dwc: fix inconsistent lock state Signed-off-by: Kari Suvanto <[email protected]> Add FIQ patch to dwc_otg driver. Enable with dwc_otg.fiq_fix_enable=1. Should give about 10% more ARM performance. Thanks to Gordon and Costas Avoid dynamic memory allocation for channel lock in USB driver. Thanks ddv2005. Add NAK holdoff scheme. Enabled by default, disable with dwc_otg.nak_holdoff_enable=0. Thanks gsh Make sure we wait for the reset to finish dwc_otg: fix bug in dwc_otg_hcd.c resulting in silent kernel memory corruption, escalating to OOPS under high USB load. dwc_otg: Fix unsafe access of QTD during URB enqueue In dwc_otg_hcd_urb_enqueue during qtd creation, it was possible that the transaction could complete almost immediately after the qtd was assigned to a host channel during URB enqueue, which meant the qtd pointer was no longer valid having been completed and removed. Usually, this resulted in an OOPS during URB submission. By predetermining whether transactions need to be queued or not, this unsafe pointer access is avoided. This bug was only evident on the Pi model A where a device was attached that had no periodic endpoints (e.g. USB pendrive or some wlan devices). dwc_otg: Fix incorrect URB allocation error handling If the memory allocation for a dwc_otg_urb failed, the kernel would OOPS because for some reason a member of the *unallocated* struct was set to zero. Error handling changed to fail correctly. dwc_otg: fix potential use-after-free case in interrupt handler If a transaction had previously aborted, certain interrupts are enabled to track error counts and reset where necessary. On IN endpoints the host generates an ACK interrupt near-simultaneously with completion of transfer. In the case where this transfer had previously had an error, this results in a use-after-free on the QTD memory space with a 1-byte length being overwritten to 0x00. dwc_otg: add handling of SPLIT transaction data toggle errors Previously a data toggle error on packets from a USB1.1 device behind a TT would result in the Pi locking up as the driver never handled the associated interrupt. Patch adds basic retry mechanism and interrupt acknowledgement to cater for either a chance toggle error or for devices that have a broken initial toggle state (FT8U232/FT232BM). dwc_otg: implement tasklet for returning URBs to usbcore hcd layer The dwc_otg driver interrupt handler for transfer completion will spend a very long time with interrupts disabled when a URB is completed - this is because usb_hcd_giveback_urb is called from within the handler which for a USB device driver with complicated processing (e.g. webcam) will take an exorbitant amount of time to complete. This results in missed completion interrupts for other USB packets which lead to them being dropped due to microframe overruns. This patch splits returning the URB to the usb hcd layer into a high-priority tasklet. This will have most benefit for isochronous IN transfers but will also have incidental benefit where multiple periodic devices are active at once. dwc_otg: fix NAK holdoff and allow on split transactions only This corrects a bug where if a single active non-periodic endpoint had at least one transaction in its qh, on frnum == MAX_FRNUM the qh would get skipped and never get queued again. This would result in a silent device until error detection (automatic or otherwise) would either reset the device or flush and requeue the URBs. Additionally the NAK holdoff was enabled for all transactions - this would potentially stall a HS endpoint for 1ms if a previous error state enabled this interrupt and the next response was a NAK. Fix so that only split transactions get held off. dwc_otg: Call usb_hcd_unlink_urb_from_ep with lock held in completion handler usb_hcd_unlink_urb_from_ep must be called with the HCD lock held. Calling it asynchronously in the tasklet was not safe (regression in c4564d4). This change unlinks it from the endpoint prior to queueing it for handling in the tasklet, and also adds a check to ensure the urb is OK to be unlinked before doing so. NULL pointer dereference kernel oopses had been observed in usb_hcd_giveback_urb when a USB device was unplugged/replugged during data transfer. This effect was reproduced using automated USB port power control, hundreds of replug events were performed during active transfers to confirm that the problem was eliminated. USB fix using a FIQ to implement split transactions This commit adds a FIQ implementaion that schedules the split transactions using a FIQ so we don't get held off by the interrupt latency of Linux dwc_otg: fix device attributes and avoid kernel warnings on boot dcw_otg: avoid logging function that can cause panics See: raspberrypi/firmware#21 Thanks to cleverca22 for fix dwc_otg: mask correct interrupts after transaction error recovery The dwc_otg driver will unmask certain interrupts on a transaction that previously halted in the error state in order to reset the QTD error count. The various fine-grained interrupt handlers do not consider that other interrupts besides themselves were unmasked. By disabling the two other interrupts only ever enabled in DMA mode for this purpose, we can avoid unnecessary function calls in the IRQ handler. This will also prevent an unneccesary FIQ interrupt from being generated if the FIQ is enabled. dwc_otg: fiq: prevent FIQ thrash and incorrect state passing to IRQ In the case of a transaction to a device that had previously aborted due to an error, several interrupts are enabled to reset the error count when a device responds. This has the side-effect of making the FIQ thrash because the hardware will generate multiple instances of a NAK on an IN bulk/interrupt endpoint and multiple instances of ACK on an OUT bulk/interrupt endpoint. Make the FIQ mask and clear the associated interrupts. Additionally, on non-split transactions make sure that only unmasked interrupts are cleared. This caused a hard-to-trigger but serious race condition when you had the combination of an endpoint awaiting error recovery and a transaction completed on an endpoint - due to the sequencing and timing of interrupts generated by the dwc_otg core, it was possible to confuse the IRQ handler. Fix function tracing dwc_otg: whitespace cleanup in dwc_otg_urb_enqueue dwc_otg: prevent OOPSes during device disconnects The dwc_otg_urb_enqueue function is thread-unsafe. In particular the access of urb->hcpriv, usb_hcd_link_urb_to_ep, dwc_otg_urb->qtd and friends does not occur within a critical section and so if a device was unplugged during activity there was a high chance that the usbcore hub_thread would try to disable the endpoint with partially- formed entries in the URB queue. This would result in BUG() or null pointer dereferences. Fix so that access of urb->hcpriv, enqueuing to the hardware and adding to usbcore endpoint URB lists is contained within a single critical section. dwc_otg: prevent BUG() in TT allocation if hub address is > 16 A fixed-size array is used to track TT allocation. This was previously set to 16 which caused a crash because dwc_otg_hcd_allocate_port would read past the end of the array. This was hit if a hub was plugged in which enumerated as addr > 16, due to previous device resets or unplugs. Also add #ifdef FIQ_DEBUG around hcd->hub_port_alloc[], which grows to a large size if 128 hub addresses are supported. This field is for debug only for tracking which frame an allocate happened in. dwc_otg: make channel halts with unknown state less damaging If the IRQ received a channel halt interrupt through the FIQ with no other bits set, the IRQ would not release the host channel and never complete the URB. Add catchall handling to treat as a transaction error and retry. dwc_otg: fiq_split: use TTs with more granularity This fixes certain issues with split transaction scheduling. - Isochronous multi-packet OUT transactions now hog the TT until they are completed - this prevents hubs aborting transactions if they get a periodic start-split out-of-order - Don't perform TT allocation on non-periodic endpoints - this allows simultaneous use of the TT's bulk/control and periodic transaction buffers This commit will mainly affect USB audio playback. dwc_otg: fix potential sleep while atomic during urb enqueue Fixes a regression introduced with eb1b482. Kmalloc called from dwc_otg_hcd_qtd_add / dwc_otg_hcd_qtd_create did not always have the GPF_ATOMIC flag set. Force this flag when inside the larger critical section. dwc_otg: make fiq_split_enable imply fiq_fix_enable Failing to set up the FIQ correctly would result in "IRQ 32: nobody cared" errors in dmesg. dwc_otg: prevent crashes on host port disconnects Fix several issues resulting in crashes or inconsistent state if a Model A root port was disconnected. - Clean up queue heads properly in kill_urbs_in_qh_list by removing the empty QHs from the schedule lists - Set the halt status properly to prevent IRQ handlers from using freed memory - Add fiq_split related cleanup for saved registers - Make microframe scheduling reclaim host channels if active during a disconnect - Abort URBs with -ESHUTDOWN status response, informing device drivers so they respond in a more correct fashion and don't try to resubmit URBs - Prevent IRQ handlers from attempting to handle channel interrupts if the associated URB was dequeued (and the driver state was cleared) dwc_otg: prevent leaking URBs during enqueue A dwc_otg_urb would get leaked if the HCD enqueue function failed for any reason. Free the URB at the appropriate points. dwc_otg: Enable NAK holdoff for control split transactions Certain low-speed devices take a very long time to complete a data or status stage of a control transaction, producing NAK responses until they complete internal processing - the USB2.0 spec limit is up to 500mS. This causes the same type of interrupt storm as seen with USB-serial dongles prior to c8edb23. In certain circumstances, usually while booting, this interrupt storm could cause SD card timeouts. dwc_otg: Fix for occasional lockup on boot when doing a USB reset dwc_otg: Don't issue traffic to LS devices in FS mode Issuing low-speed packets when the root port is in full-speed mode causes the root port to stop responding. Explicitly fail when enqueuing URBs to a LS endpoint on a FS bus. Fix ARM architecture issue with local_irq_restore() If local_fiq_enable() is called before a local_irq_restore(flags) where the flags variable has the F bit set, the FIQ will be erroneously disabled. Fixup arch_local_irq_restore to avoid trampling the F bit in CPSR. Also fix some of the hacks previously implemented for previous dwc_otg incarnations. dwc_otg: fiq_fsm: Base commit for driver rewrite This commit removes the previous FIQ fixes entirely and adds fiq_fsm. This rewrite features much more complete support for split transactions and takes into account several OTG hardware bugs. High-speed isochronous transactions are also capable of being performed by fiq_fsm. All driver options have been removed and replaced with: - dwc_otg.fiq_enable (bool) - dwc_otg.fiq_fsm_enable (bool) - dwc_otg.fiq_fsm_mask (bitmask) - dwc_otg.nak_holdoff (unsigned int) Defaults are specified such that fiq_fsm behaves similarly to the previously implemented FIQ fixes. fiq_fsm: Push error recovery into the FIQ when fiq_fsm is used If the transfer associated with a QTD failed due to a bus error, the HCD would retry the transfer up to 3 times (implementing the USB2.0 three-strikes retry in software). Due to the masking mechanism used by fiq_fsm, it is only possible to pass a single interrupt through to the HCD per-transfer. In this instance host channels would fall off the radar because the error reset would function, but the subsequent channel halt would be lost. Push the error count reset into the FIQ handler. fiq_fsm: Implement timeout mechanism For full-speed endpoints with a large packet size, interrupt latency runs the risk of the FIQ starting a transaction too late in a full-speed frame. If the device is still transmitting data when EOF2 for the downstream frame occurs, the hub will disable the port. This change is not reflected in the hub status endpoint and the device becomes unresponsive. Prevent high-bandwidth transactions from being started too late in a frame. The mechanism is not guaranteed: a combination of bit stuffing and hub latency may still result in a device overrunning. fiq_fsm: fix bounce buffer utilisation for Isochronous OUT Multi-packet isochronous OUT transactions were subject to a few bounday bugs. Fix them. Audio playback is now much more robust: however, an issue stands with devices that have adaptive sinks - ALSA plays samples too fast. dwc_otg: Return full-speed frame numbers in HS mode The frame counter increments on every *microframe* in high-speed mode. Most device drivers expect this number to be in full-speed frames - this caused considerable confusion to e.g. snd_usb_audio which uses the frame counter to estimate the number of samples played. fiq_fsm: save PID on completion of interrupt OUT transfers Also add edge case handling for interrupt transports. Note that for periodic split IN, data toggles are unimplemented in the OTG host hardware - it unconditionally accepts any PID. fiq_fsm: add missing case for fiq_fsm_tt_in_use() Certain combinations of bitrate and endpoint activity could result in a periodic transaction erroneously getting started while the previous Isochronous OUT was still active. fiq_fsm: clear hcintmsk for aborted transactions Prevents the FIQ from erroneously handling interrupts on a timed out channel. fiq_fsm: enable by default fiq_fsm: fix dequeues for non-periodic split transactions If a dequeue happened between the SSPLIT and CSPLIT phases of the transaction, the HCD would never receive an interrupt. fiq_fsm: Disable by default fiq_fsm: Handle HC babble errors The HCTSIZ transfer size field raises a babble interrupt if the counter wraps. Handle the resulting interrupt in this case. dwc_otg: fix interrupt registration for fiq_enable=0 Additionally make the module parameter conditional for wherever hcd->fiq_state is touched. fiq_fsm: Enable by default dwc_otg: Fix various issues with root port and transaction errors Process the host port interrupts correctly (and don't trample them). Root port hotplug now functional again. Fix a few thinkos with the transaction error passthrough for fiq_fsm. fiq_fsm: Implement hack for Split Interrupt transactions Hubs aren't too picky about which endpoint we send Control type split transactions to. By treating Interrupt transfers as Control, it is possible to use the non-periodic queue in the OTG core as well as the non-periodic FIFOs in the hub itself. This massively reduces the microframe exclusivity/contention that periodic split transactions otherwise have to enforce. It goes without saying that this is a fairly egregious USB specification violation, but it works. Original idea by Hans Petter Selasky @ FreeBSD.org. dwc_otg: FIQ support on SMP. Set up FIQ stack and handler on Core 0 only. dwc_otg: introduce fiq_fsm_spin(un|)lock() SMP safety for the FIQ relies on register read-modify write cycles being completed in the correct order. Several places in the DWC code modify registers also touched by the FIQ. Protect these by a bare-bones lock mechanism. This also makes it possible to run the FIQ and IRQ handlers on different cores. fiq_fsm: fix build on bcm2708 and bcm2709 platforms dwc_otg: put some barriers back where they should be for UP bcm2709/dwc_otg: Setup FIQ on core 1 if >1 core active dwc_otg: fixup read-modify-write in critical paths Be more careful about read-modify-write on registers that the FIQ also touches. Guard fiq_fsm_spin_lock with fiq_enable check fiq_fsm: Falling out of the state machine isn't fatal This edge case can be hit if the port is disabled while the FIQ is in the middle of a transaction. Make the effects less severe. Also get rid of the useless return value. squash: dwc_otg: Allow to build without SMP usb: core: make overcurrent messages more prominent Hub overcurrent messages are more serious than "debug". Increase loglevel. usb: dwc_otg: Don't use dma_to_virt() Commit 6ce0d20 changes dma_to_virt() which breaks this driver. Open code the old dma_to_virt() implementation to work around this. Limit the use of __bus_to_virt() to cases where transfer_buffer_length is set and transfer_buffer is not set. This is done to increase the chance that this driver will also work on ARCH_BCM2835. transfer_buffer should not be NULL if the length is set, but the comment in the code indicates that there are situations where this might happen. drivers/usb/isp1760/isp1760-hcd.c also has a similar comment pointing to a possible: 'usb storage / SCSI bug'. Signed-off-by: Noralf Trønnes <[email protected]> dwc_otg: Fix crash when fiq_enable=0 dwc_otg: fiq_fsm: Make high-speed isochronous strided transfers work properly Certain low-bandwidth high-speed USB devices (specialist audio devices, compressed-frame webcams) have packet intervals > 1 microframe. Stride these transfers in the FIQ by using the start-of-frame interrupt to restart the channel at the right time. dwc_otg: Force host mode to fix incorrect compute module boards dwc_otg: Add ARCH_BCM2835 support Signed-off-by: Noralf Trønnes <[email protected]> dwc_otg: Simplify FIQ irq number code Dropping ATAGS means we can simplify the FIQ irq number code. Also add error checking on the returned irq number. Signed-off-by: Noralf Trønnes <[email protected]> dwc_otg: Remove duplicate gadget probe/unregister function dwc_otg: Properly set the HFIR Douglas Anderson reported: According to the most up to date version of the dwc2 databook, the FRINT field of the HFIR register should be programmed to: * 125 us * (PHY clock freq for HS) - 1 * 1000 us * (PHY clock freq for FS/LS) - 1 This is opposed to older versions of the doc that claimed it should be: * 125 us * (PHY clock freq for HS) * 1000 us * (PHY clock freq for FS/LS) and reported lower timing jitter on a USB analyser dcw_otg: trim xfer length when buffer larger than allocated size is received dwc_otg: Don't free qh align buffers in atomic context dwc_otg: Enable the hack for Split Interrupt transactions by default dwc_otg.fiq_fsm_mask=0xF has long been a suggestion for users with audio stutters or other USB bandwidth issues. So far we are aware of many success stories but no failure caused by this setting. Make it a default to learn more. See: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=70437 Signed-off-by: popcornmix <[email protected]> dwc_otg: Use kzalloc when suitable dwc_otg: Pass struct device to dma_alloc*() This makes it possible to get the bus address from Device Tree. Signed-off-by: Noralf Trønnes <[email protected]> dwc_otg: fix summarize urb->actual_length for isochronous transfers Kernel does not copy input data of ISO transfers to userspace if actual_length is set only in ISO transfers and not summarized in urb->actual_length. Fixes #903 fiq_fsm: Use correct states when starting isoc OUT transfers In fiq_fsm_start_next_periodic() if an isochronous OUT transfer was selected, no regard was given as to whether this was a single-packet transfer or a multi-packet staged transfer. For single-packet transfers, this had the effect of repeatedly sending OUT packets with bogus data and lengths. Eventually if the channel was repeatedly enabled enough times, this would lock up the OTG core and no further bus transfers would happen. Set the FSM state up properly if we select a single-packet transfer. Fixes #1842 dwc_otg: make nak_holdoff work as intended with empty queues If URBs reading from non-periodic split endpoints were dequeued and the last transfer from the endpoint was a NAK handshake, the resulting qh->nak_frame value was stale which would result in unnecessarily long polling intervals for the first subsequent transfer with a fresh URB. Fixup qh->nak_frame in dwc_otg_hcd_urb_dequeue and also guard against a case where a single URB is submitted to the endpoint, a NAK was received on the transfer immediately prior to receiving data and the device subsequently resubmits another URB past the qh->nak_frame interval. Fixes #1709 dwc_otg: fix split transaction data toggle handling around dequeues See #1709 Fix several issues regarding endpoint state when URBs are dequeued - If the HCD is disconnected, flush FIQ-enabled channels properly - Save the data toggle state for bulk endpoints if the last transfer from an endpoint where URBs were dequeued returned a data packet - Reset hc->start_pkt_count properly in assign_and_init_hc() dwc_otg: fix several potential crash sources On root port disconnect events, the host driver state is cleared and in-progress host channels are forcibly stopped. This doesn't play well with the FIQ running in the background, so: - Guard the disconnect callback with both the host spinlock and FIQ spinlock - Move qtd dereference in dwc_otg_handle_hc_fsm() after the early-out so we don't dereference a qtd that has gone away - Turn catch-all BUG()s in dwc_otg_handle_hc_fsm() into warnings. dwc_otg: delete hcd->channel_lock The lock serves no purpose as it is only held while the HCD spinlock is already being held. dwc_otg: remove unnecessary dma-mode channel halts on disconnect interrupt Host channels are already halted in kill_urbs_in_qh_list() with the subsequent interrupt processing behaving as if the URB was dequeued via HCD callback. There's no need to clobber the host channel registers a second time as this exposes races between the driver and host channel resulting in hcd->free_hc_list becoming corrupted. dwcotg: Allow to build without FIQ on ARM64 Signed-off-by: popcornmix <[email protected]> dwc_otg: make periodic scheduling behave properly for FS buses If the root port is in full-speed mode, transfer times at 12mbit/s would be calculated but matched against high-speed quotas. Reinitialise hcd->frame_usecs[i] on each port enable event so that full-speed bandwidth can be tracked sensibly. Also, don't bother using the FIQ for transfers when in full-speed mode - at the slower bus speed, interrupt frequency is reduced by an order of magnitude. Related issue: #2020 dwc_otg: fiq_fsm: Make isochronous compatibility checks work properly Get rid of the spammy printk and local pointer mangling. Also, there is a nominal benefit for using fiq_fsm for isochronous transfers in FS mode (~1.1k IRQs per second vs 2.1k IRQs per second) so remove the root port speed check. dwc_otg: add module parameter int_ep_interval_min Add a module parameter (defaulting to ignored) that clamps the polling rate of high-speed Interrupt endpoints to a minimum microframe interval. The parameter is modifiable at runtime as it is used when activating new endpoints (such as on device connect). dwc_otg: fiq_fsm: Add non-periodic TT exclusivity constraints Certain hub types do not discriminate between pipe direction (IN or OUT) when considering non-periodic transfers. Therefore these hubs get confused if multiple transfers are issued in different directions with the same device address and endpoint number. Constrain queuing non-periodic split transactions so they are performed serially in such cases. Related: #2024 dwc_otg: Fixup change to DRIVER_ATTR interface dwc_otg: Fix compilation warnings Signed-off-by: Phil Elwell <[email protected]> USB_DWCOTG: Disable building dwc_otg as a module (#2265) When dwc_otg is built as a module, build will fail with the following error: ERROR: "DWC_TASK_HI_SCHEDULE" [drivers/usb/host/dwc_otg/dwc_otg.ko] undefined! scripts/Makefile.modpost:91: recipe for target '__modpost' failed make[1]: *** [__modpost] Error 1 Makefile:1199: recipe for target 'modules' failed make: *** [modules] Error 2 Even if the error is solved by including the missing DWC_TASK_HI_SCHEDULE function, the kernel will panic when loading dwc_otg. As a workaround, simply prevent user from building dwc_otg as a module as the current kernel does not support it. See: #2258 Signed-off-by: Malik Olivier Boussejra <[email protected]> dwc_otg: New timer API dwc_otg: Fix removed ACCESS_ONCE->READ_ONCE dwc_otg: don't unconditionally force host mode in dwc_otg_cil_init() Add the ability to disable force_host_mode for those that want to use dwc_otg in both device and host modes. dwc_otg: Fix a regression when dequeueing isochronous transfers In 282bed9 (dwc_otg: make nak_holdoff work as intended with empty queues) the dequeue mechanism was changed to leave FIQ-enabled transfers to run to completion - to avoid leaving hub TT buffers with stale packets lying around. This broke FIQ-accelerated isochronous transfers, as this then meant that dozens of transfers were performed after the dequeue function returned. Restore the state machine fence for isochronous transfers. fiq_fsm: rewind DMA pointer for OUT transactions that fail (#2288) See: #2140 dwc_otg: add smp_mb() to prevent driver state corruption on boot Occasional crashes have been seen where the FIQ code dereferences invalid/random pointers immediately after being set up, leading to panic on boot. The crash occurs as the FIQ code races against hcd_init_fiq() and the hcd_init_fiq() code races against the outstanding memory stores from dwc_otg_hcd_init(). Use explicit barriers after touching driver state. usb: dwc_otg: fix memory corruption in dwc_otg driver [Upstream commit 51b1b64] The move from the staging tree to the main tree exposed a longstanding memory corruption bug in the dwc2 driver. The reordering of the driver initialization caused the dwc2 driver to corrupt the initialization data of the sdhci driver on the Raspberry Pi platform, which made the bug show up. The error is in calling to_usb_device(hsotg->dev), since ->dev is not a member of struct usb_device. The easiest fix is to just remove the offending code, since it is not really needed. Thanks to Stephen Warren for tracking down the cause of this. Reported-by: Andre Heider <[email protected]> Tested-by: Stephen Warren <[email protected]> Signed-off-by: Paul Zimmerman <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> [lukas: port from upstream dwc2 to out-of-tree dwc_otg driver] Signed-off-by: Lukas Wunner <[email protected]> usb: dwb_otg: Fix unreachable switch statement warning This warning appears with GCC 7.3.0 from toolchains.bootlin.com: ../drivers/usb/host/dwc_otg/dwc_otg_fiq_fsm.c: In function ‘fiq_fsm_update_hs_isoc’: ../drivers/usb/host/dwc_otg/dwc_otg_fiq_fsm.c:595:61: warning: statement will never be executed [-Wswitch-unreachable] st->hctsiz_copy.b.xfersize = nrpackets * st->hcchar_copy.b.mps; ~~~~~~~~~~~~~~~~~^~~~ Signed-off-by: Nathan Chancellor <[email protected]> dwc_otg: fiq_fsm: fix incorrect DMA register offset calculation Rationalise the offset and update all call sites. Fixes #2408 dwc_otg: fix bug with port_addr assignment for single-TT hubs See #2734 The "Hub Port" field in the split transaction packet was always set to 1 for single-TT hubs. The majority of single-TT hub products apparently ignore this field and broadcast to all downstream enabled ports, which masked the issue. A subset of hub devices apparently need the port number to be exact or split transactions will fail. usb: dwc_otg: Clean up build warnings on 64bit kernels No functional changes. Almost all are changes to logging lines. Signed-off-by: Dave Stevenson <[email protected]> usb: dwc_otg: Use dma allocation for mphi dummy_send buffer The FIQ driver used a kzalloc'ed buffer for dummy_send, passing a kernel virtual address to the hardware block. The buffer is only ever used for a dummy read, so it should be harmless, but there is the chance that it will cause exceptions. Use a dma allocation so that we have a genuine bus address, and read from that. Free the allocation when done for good measure. Signed-off-by: Dave Stevenson <[email protected]> dwc_otg: only do_split when we actually need to do a split The previous test would fail if the root port was in fullspeed mode and there was a hub between the FS device and the root port. While the transfer worked, the schedule mangling performed for high-speed split transfers would break leading to an 8ms polling interval. dwc_otg: fix locking around dequeueing and killing URBs kill_urbs_in_qh_list() is practically only ever called with the fiq lock already held, so don't spinlock twice in the case where we need to cancel an isochronous transfer. Also fix up a case where the global interrupt register could be read with the fiq lock not held. Fixes the deadlock seen in #2907
1 parent 640e47d commit 942fc23

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

70 files changed

+60037
-16
lines changed

arch/arm/include/asm/irqflags.h

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -163,13 +163,23 @@ static inline unsigned long arch_local_save_flags(void)
163163
}
164164

165165
/*
166-
* restore saved IRQ & FIQ state
166+
* restore saved IRQ state
167167
*/
168168
#define arch_local_irq_restore arch_local_irq_restore
169169
static inline void arch_local_irq_restore(unsigned long flags)
170170
{
171-
asm volatile(
172-
" msr " IRQMASK_REG_NAME_W ", %0 @ local_irq_restore"
171+
unsigned long temp = 0;
172+
flags &= ~(1 << 6);
173+
asm volatile (
174+
" mrs %0, cpsr"
175+
: "=r" (temp)
176+
:
177+
: "memory", "cc");
178+
/* Preserve FIQ bit */
179+
temp &= (1 << 6);
180+
flags = flags | temp;
181+
asm volatile (
182+
" msr cpsr_c, %0 @ local_irq_restore"
173183
:
174184
: "r" (flags)
175185
: "memory", "cc");

arch/arm/kernel/fiqasm.S

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,3 +47,7 @@ ENTRY(__get_fiq_regs)
4747
mov r0, r0 @ avoid hazard prior to ARMv4
4848
ret lr
4949
ENDPROC(__get_fiq_regs)
50+
51+
ENTRY(__FIQ_Branch)
52+
mov pc, r8
53+
ENDPROC(__FIQ_Branch)

drivers/usb/Makefile

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
obj-$(CONFIG_USB) += core/
99
obj-$(CONFIG_USB_SUPPORT) += phy/
1010

11+
obj-$(CONFIG_USB_DWCOTG) += host/
1112
obj-$(CONFIG_USB_DWC3) += dwc3/
1213
obj-$(CONFIG_USB_DWC2) += dwc2/
1314
obj-$(CONFIG_USB_ISP1760) += isp1760/

drivers/usb/core/generic.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,7 @@ int usb_choose_configuration(struct usb_device *udev)
190190
dev_warn(&udev->dev,
191191
"no configuration chosen from %d choice%s\n",
192192
num_configs, plural(num_configs));
193+
dev_warn(&udev->dev, "No support over %dmA\n", udev->bus_mA);
193194
}
194195
return i;
195196
}

drivers/usb/core/hub.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5286,7 +5286,7 @@ static void port_event(struct usb_hub *hub, int port1)
52865286
port_dev->over_current_count++;
52875287
port_over_current_notify(port_dev);
52885288

5289-
dev_dbg(&port_dev->dev, "over-current change #%u\n",
5289+
dev_notice(&port_dev->dev, "over-current change #%u\n",
52905290
port_dev->over_current_count);
52915291
usb_clear_port_feature(hdev, port1,
52925292
USB_PORT_FEAT_C_OVER_CURRENT);

drivers/usb/core/message.c

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1991,6 +1991,85 @@ int usb_set_configuration(struct usb_device *dev, int configuration)
19911991
if (cp->string == NULL &&
19921992
!(dev->quirks & USB_QUIRK_CONFIG_INTF_STRINGS))
19931993
cp->string = usb_cache_string(dev, cp->desc.iConfiguration);
1994+
/* Uncomment this define to enable the HS Electrical Test support */
1995+
#define DWC_HS_ELECT_TST 1
1996+
#ifdef DWC_HS_ELECT_TST
1997+
/* Here we implement the HS Electrical Test support. The
1998+
* tester uses a vendor ID of 0x1A0A to indicate we should
1999+
* run a special test sequence. The product ID tells us
2000+
* which sequence to run. We invoke the test sequence by
2001+
* sending a non-standard SetFeature command to our root
2002+
* hub port. Our dwc_otg_hcd_hub_control() routine will
2003+
* recognize the command and perform the desired test
2004+
* sequence.
2005+
*/
2006+
if (dev->descriptor.idVendor == 0x1A0A) {
2007+
/* HSOTG Electrical Test */
2008+
dev_warn(&dev->dev, "VID from HSOTG Electrical Test Fixture\n");
2009+
2010+
if (dev->bus && dev->bus->root_hub) {
2011+
struct usb_device *hdev = dev->bus->root_hub;
2012+
dev_warn(&dev->dev, "Got PID 0x%x\n", dev->descriptor.idProduct);
2013+
2014+
switch (dev->descriptor.idProduct) {
2015+
case 0x0101: /* TEST_SE0_NAK */
2016+
dev_warn(&dev->dev, "TEST_SE0_NAK\n");
2017+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2018+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2019+
USB_PORT_FEAT_TEST, 0x300, NULL, 0, HZ);
2020+
break;
2021+
2022+
case 0x0102: /* TEST_J */
2023+
dev_warn(&dev->dev, "TEST_J\n");
2024+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2025+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2026+
USB_PORT_FEAT_TEST, 0x100, NULL, 0, HZ);
2027+
break;
2028+
2029+
case 0x0103: /* TEST_K */
2030+
dev_warn(&dev->dev, "TEST_K\n");
2031+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2032+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2033+
USB_PORT_FEAT_TEST, 0x200, NULL, 0, HZ);
2034+
break;
2035+
2036+
case 0x0104: /* TEST_PACKET */
2037+
dev_warn(&dev->dev, "TEST_PACKET\n");
2038+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2039+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2040+
USB_PORT_FEAT_TEST, 0x400, NULL, 0, HZ);
2041+
break;
2042+
2043+
case 0x0105: /* TEST_FORCE_ENABLE */
2044+
dev_warn(&dev->dev, "TEST_FORCE_ENABLE\n");
2045+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2046+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2047+
USB_PORT_FEAT_TEST, 0x500, NULL, 0, HZ);
2048+
break;
2049+
2050+
case 0x0106: /* HS_HOST_PORT_SUSPEND_RESUME */
2051+
dev_warn(&dev->dev, "HS_HOST_PORT_SUSPEND_RESUME\n");
2052+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2053+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2054+
USB_PORT_FEAT_TEST, 0x600, NULL, 0, 40 * HZ);
2055+
break;
2056+
2057+
case 0x0107: /* SINGLE_STEP_GET_DEVICE_DESCRIPTOR setup */
2058+
dev_warn(&dev->dev, "SINGLE_STEP_GET_DEVICE_DESCRIPTOR setup\n");
2059+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2060+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2061+
USB_PORT_FEAT_TEST, 0x700, NULL, 0, 40 * HZ);
2062+
break;
2063+
2064+
case 0x0108: /* SINGLE_STEP_GET_DEVICE_DESCRIPTOR execute */
2065+
dev_warn(&dev->dev, "SINGLE_STEP_GET_DEVICE_DESCRIPTOR execute\n");
2066+
usb_control_msg(hdev, usb_sndctrlpipe(hdev, 0),
2067+
USB_REQ_SET_FEATURE, USB_RT_PORT,
2068+
USB_PORT_FEAT_TEST, 0x800, NULL, 0, 40 * HZ);
2069+
}
2070+
}
2071+
}
2072+
#endif /* DWC_HS_ELECT_TST */
19942073

19952074
/* Now that the interfaces are installed, re-enable LPM. */
19962075
usb_unlocked_enable_lpm(dev);

drivers/usb/core/otg_whitelist.h

Lines changed: 102 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -15,33 +15,82 @@
1515
static struct usb_device_id whitelist_table[] = {
1616

1717
/* hubs are optional in OTG, but very handy ... */
18+
#define CERT_WITHOUT_HUBS
19+
#if defined(CERT_WITHOUT_HUBS)
20+
{ USB_DEVICE( 0x0000, 0x0000 ), }, /* Root HUB Only*/
21+
#else
1822
{ USB_DEVICE_INFO(USB_CLASS_HUB, 0, 0), },
1923
{ USB_DEVICE_INFO(USB_CLASS_HUB, 0, 1), },
24+
{ USB_DEVICE_INFO(USB_CLASS_HUB, 0, 2), },
25+
#endif
2026

2127
#ifdef CONFIG_USB_PRINTER /* ignoring nonstatic linkage! */
2228
/* FIXME actually, printers are NOT supposed to use device classes;
2329
* they're supposed to use interface classes...
2430
*/
25-
{ USB_DEVICE_INFO(7, 1, 1) },
26-
{ USB_DEVICE_INFO(7, 1, 2) },
27-
{ USB_DEVICE_INFO(7, 1, 3) },
31+
//{ USB_DEVICE_INFO(7, 1, 1) },
32+
//{ USB_DEVICE_INFO(7, 1, 2) },
33+
//{ USB_DEVICE_INFO(7, 1, 3) },
2834
#endif
2935

3036
#ifdef CONFIG_USB_NET_CDCETHER
3137
/* Linux-USB CDC Ethernet gadget */
32-
{ USB_DEVICE(0x0525, 0xa4a1), },
38+
//{ USB_DEVICE(0x0525, 0xa4a1), },
3339
/* Linux-USB CDC Ethernet + RNDIS gadget */
34-
{ USB_DEVICE(0x0525, 0xa4a2), },
40+
//{ USB_DEVICE(0x0525, 0xa4a2), },
3541
#endif
3642

3743
#if IS_ENABLED(CONFIG_USB_TEST)
3844
/* gadget zero, for testing */
39-
{ USB_DEVICE(0x0525, 0xa4a0), },
45+
//{ USB_DEVICE(0x0525, 0xa4a0), },
4046
#endif
4147

48+
/* OPT Tester */
49+
{ USB_DEVICE( 0x1a0a, 0x0101 ), }, /* TEST_SE0_NAK */
50+
{ USB_DEVICE( 0x1a0a, 0x0102 ), }, /* Test_J */
51+
{ USB_DEVICE( 0x1a0a, 0x0103 ), }, /* Test_K */
52+
{ USB_DEVICE( 0x1a0a, 0x0104 ), }, /* Test_PACKET */
53+
{ USB_DEVICE( 0x1a0a, 0x0105 ), }, /* Test_FORCE_ENABLE */
54+
{ USB_DEVICE( 0x1a0a, 0x0106 ), }, /* HS_PORT_SUSPEND_RESUME */
55+
{ USB_DEVICE( 0x1a0a, 0x0107 ), }, /* SINGLE_STEP_GET_DESCRIPTOR setup */
56+
{ USB_DEVICE( 0x1a0a, 0x0108 ), }, /* SINGLE_STEP_GET_DESCRIPTOR execute */
57+
58+
/* Sony cameras */
59+
{ USB_DEVICE_VER(0x054c,0x0010,0x0410, 0x0500), },
60+
61+
/* Memory Devices */
62+
//{ USB_DEVICE( 0x0781, 0x5150 ), }, /* SanDisk */
63+
//{ USB_DEVICE( 0x05DC, 0x0080 ), }, /* Lexar */
64+
//{ USB_DEVICE( 0x4146, 0x9281 ), }, /* IOMEGA */
65+
//{ USB_DEVICE( 0x067b, 0x2507 ), }, /* Hammer 20GB External HD */
66+
{ USB_DEVICE( 0x0EA0, 0x2168 ), }, /* Ours Technology Inc. (BUFFALO ClipDrive)*/
67+
//{ USB_DEVICE( 0x0457, 0x0150 ), }, /* Silicon Integrated Systems Corp. */
68+
69+
/* HP Printers */
70+
//{ USB_DEVICE( 0x03F0, 0x1102 ), }, /* HP Photosmart 245 */
71+
//{ USB_DEVICE( 0x03F0, 0x1302 ), }, /* HP Photosmart 370 Series */
72+
73+
/* Speakers */
74+
//{ USB_DEVICE( 0x0499, 0x3002 ), }, /* YAMAHA YST-MS35D USB Speakers */
75+
//{ USB_DEVICE( 0x0672, 0x1041 ), }, /* Labtec USB Headset */
76+
4277
{ } /* Terminating entry */
4378
};
4479

80+
static inline void report_errors(struct usb_device *dev)
81+
{
82+
/* OTG MESSAGE: report errors here, customize to match your product */
83+
dev_info(&dev->dev, "device Vendor:%04x Product:%04x is not supported\n",
84+
le16_to_cpu(dev->descriptor.idVendor),
85+
le16_to_cpu(dev->descriptor.idProduct));
86+
if (USB_CLASS_HUB == dev->descriptor.bDeviceClass){
87+
dev_printk(KERN_CRIT, &dev->dev, "Unsupported Hub Topology\n");
88+
} else {
89+
dev_printk(KERN_CRIT, &dev->dev, "Attached Device is not Supported\n");
90+
}
91+
}
92+
93+
4594
static int is_targeted(struct usb_device *dev)
4695
{
4796
struct usb_device_id *id = whitelist_table;
@@ -91,16 +140,57 @@ static int is_targeted(struct usb_device *dev)
91140
continue;
92141

93142
return 1;
94-
}
143+
/* NOTE: can't use usb_match_id() since interface caches
144+
* aren't set up yet. this is cut/paste from that code.
145+
*/
146+
for (id = whitelist_table; id->match_flags; id++) {
147+
#ifdef DEBUG
148+
dev_dbg(&dev->dev,
149+
"ID: V:%04x P:%04x DC:%04x SC:%04x PR:%04x \n",
150+
id->idVendor,
151+
id->idProduct,
152+
id->bDeviceClass,
153+
id->bDeviceSubClass,
154+
id->bDeviceProtocol);
155+
#endif
95156

96-
/* add other match criteria here ... */
157+
if ((id->match_flags & USB_DEVICE_ID_MATCH_VENDOR) &&
158+
id->idVendor != le16_to_cpu(dev->descriptor.idVendor))
159+
continue;
97160

161+
if ((id->match_flags & USB_DEVICE_ID_MATCH_PRODUCT) &&
162+
id->idProduct != le16_to_cpu(dev->descriptor.idProduct))
163+
continue;
98164

99-
/* OTG MESSAGE: report errors here, customize to match your product */
100-
dev_err(&dev->dev, "device v%04x p%04x is not supported\n",
101-
le16_to_cpu(dev->descriptor.idVendor),
102-
le16_to_cpu(dev->descriptor.idProduct));
165+
/* No need to test id->bcdDevice_lo != 0, since 0 is never
166+
greater than any unsigned number. */
167+
if ((id->match_flags & USB_DEVICE_ID_MATCH_DEV_LO) &&
168+
(id->bcdDevice_lo > le16_to_cpu(dev->descriptor.bcdDevice)))
169+
continue;
170+
171+
if ((id->match_flags & USB_DEVICE_ID_MATCH_DEV_HI) &&
172+
(id->bcdDevice_hi < le16_to_cpu(dev->descriptor.bcdDevice)))
173+
continue;
174+
175+
if ((id->match_flags & USB_DEVICE_ID_MATCH_DEV_CLASS) &&
176+
(id->bDeviceClass != dev->descriptor.bDeviceClass))
177+
continue;
178+
179+
if ((id->match_flags & USB_DEVICE_ID_MATCH_DEV_SUBCLASS) &&
180+
(id->bDeviceSubClass != dev->descriptor.bDeviceSubClass))
181+
continue;
182+
183+
if ((id->match_flags & USB_DEVICE_ID_MATCH_DEV_PROTOCOL) &&
184+
(id->bDeviceProtocol != dev->descriptor.bDeviceProtocol))
185+
continue;
186+
187+
return 1;
188+
}
189+
}
190+
191+
/* add other match criteria here ... */
103192

193+
report_errors(dev);
104194
return 0;
105195
}
106196

0 commit comments

Comments
 (0)