This patch introduces the use of devm_request_irq, devm_gpio_request,
devm_clk_get etc. instead of the corresponding unmanaged interfaces. The
calls to the functions like free_irq to free the allocated resources are
removed as they are no longer required. Some labels in the probe function
are also
Hi Alan,
What happens if you attach the full-speed device to a high-speed hub
and plug that hub into the MUSB?
That's a very interesting test i will definitely do. Unfortunately, even
if that solves the problem, we could not use that on our production
boards because we cannot change the
Use devm_* helpers in the probe function to simplify the error path and
the remove path.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Since V1: Addressed Sergei's comments
---
drivers/usb/gadget/pxa27x_udc.c | 57
Add support for device-tree device discovery. If devicetree is not
provided, fallback to legacy platform data discovery.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: devicet...@vger.kernel.org
---
Since V1: change OF id mrvl,pxa27x_udc - marvell,pxa27x-udc
This is a
Add documentation for device-tree binding of arm PXA 27x udc (usb
device) driver.
Signed-off-by: Robert Jarzmik robert.jarz...@free.fr
Cc: devicet...@vger.kernel.org
---
Since V1: change OF id mrvl,pxa27x_udc - marvell,pxa27x-udc
This is a consequence of other DT reviews on the marvell
Here are some reports of this regression affecting other hardware:
https://bbs.archlinux.org/viewtopic.php?id=183190
lsusb -v output:
Bus 003 Device 003: ID 4971:8017 SimpleTech
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 3.00
Additional affected hardware:
us 002 Device 004: ID 0bc2:3312 Seagate RSS LLC
Couldn't open device, some information will be missing
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass0 (Defined at Interface level)
On Sun, 22 Jun 2014, Wang, Yu wrote:
From: Wang, Yu yu.y.w...@intel.com
The system suspend flow as following:
1, Freeze all user processes and kenrel threads.
2, Trying to suspend all devices.
2.1, If pci device under RPM suspended state, then pci driver will try
to resume it to RPM
On Sun, 22 Jun 2014, pedro wrote:
Hi Alan,
What happens if you attach the full-speed device to a high-speed hub
and plug that hub into the MUSB?
That's a very interesting test i will definitely do. Unfortunately, even
if that solves the problem, we could not use that on our production
Hello,
I'm working on a network driver using USB3 interface to the device. From
time to time I am receiving EPROTO (-71) error on URB completion handler.
Once I get into this state all my subsequent receive URBs return the same
and I have to reset the machine to get things working again.
From
10 matches
Mail list logo
