From: Markus Rechberger
> >> Dec 27 23:23:50 solist kernel: [ 36.118245] xhci_hcd :00:14.0: ERROR
> >> Transfer event TRB DMA
> ptr
> >
> > These messages might be harmless. The 3.0 kernel contains a fix for
> > Intel Panther Point xHCI hosts that suppresses those messages, commit
> > ad808
Downloaded and compiled the r8168 driver from the Realtek website.
Problem appears to be solved.
One other thing, off Asix's website the driver there for the ax88179 has two
extra module parameters for bulk transfers, one for buffer size the other for
timing. When I was playing around I did no
On Mon, Feb 03, 2014 at 08:51:48PM +, Paul Zimmerman wrote:
> > From: Paul Zimmerman
> > Sent: Monday, February 03, 2014 9:36 AM
> >
> >> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> >> Sent: Saturday, February 01, 2014 7:44 PM
> >>
> >> On 02/01/2014 03:00 AM, Andre Heider wrote:
>
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's mini-desktop, the Intense-PC2.
The bug can be av
This device was mentioned in an OpenWRT forum. Seems to have a "standard"
Sierra Wireless ifnumber to function layout:
0: qcdm
2: nmea
3: modem
8: qmi
9: storage
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/
This device was mentioned in an OpenWRT forum. Seems to have a "standard"
Sierra Wireless ifnumber to function layout:
0: qcdm
2: nmea
3: modem
8: qmi
9: storage
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi
> On 01/30/2014 03:09 PM, Michal Nazarewicz wrote:
>> This is not a good way to do this. You are looping around with
>> 1 µseconds delays in each loop. This is active polling and is not a way
>> to implement anything. To properly use AIO with a single thread while
>> you also handling ep0, you n
From: Ajay Kumar Gupta
Disables PING on status phase of control transfer.
PING token is not mandatory in status phase of control transfer
and so some high speed USB devices don't support it. If such devices
are connected to MUSB then they would not respond to PING token
causing delayed or failed
During resume don't touch SUSPENDM/RESUME bits of POWER register
while restoring controller context. These bits might be changed
by the controller during resume operation and so will be different
than what they were during suspend.
e.g. SUSPENDM bit is set by software during USB global suspend but
Hi Greg,
Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
Patch 2 fixes remote-wakeup resume on beaglebone.
Felipe has Acked the 1st patch but still needs to Ack the 2nd one.
Patches are based on 3.14-rc1
cheers,
-roger
Ajay Kumar Gupta (1):
usb: musb: host: Fix SuperSpeed hub enumera
Hi Alan,
On 29.01.2014 21:42, Alan Stern wrote:
On Wed, 29 Jan 2014, Kamil Debski wrote:
Change the phy provider used from the old one using the USB phy
framework to a new one using the Generic phy framework.
Signed-off-by: Kamil Debski
---
.../devicetree/bindings/usb/exynos-usb.txt
On Mon, 3 Feb 2014, Alan Stern wrote:
> On Mon, 3 Feb 2014, Josh Bendavid wrote:
>
> > Hi Alan,
> > Yes, this hardware was in active use and working fine with 3.5. The usb/ir
> > issue came up as soon as I moved to 3.13-rc8. (As I said, this was not the
> > only change strictly speaking, given
On Tue, Feb 04, 2014 at 03:25:47PM +0200, Roger Quadros wrote:
> Hi Greg,
>
> Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
> Patch 2 fixes remote-wakeup resume on beaglebone.
>
> Felipe has Acked the 1st patch but still needs to Ack the 2nd one.
>
> Patches are based on 3.14-rc1
Why
On 02/04/2014 05:27 PM, Greg KH wrote:
> On Tue, Feb 04, 2014 at 03:25:47PM +0200, Roger Quadros wrote:
>> Hi Greg,
>>
>> Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
>> Patch 2 fixes remote-wakeup resume on beaglebone.
>>
>> Felipe has Acked the 1st patch but still needs to Ack the 2nd
On Tue, 2014-02-04 at 02:22 +, Paul Zimmerman wrote:
> > From: Dinh Nguyen [mailto:dingu...@altera.com]
> > Sent: Monday, February 03, 2014 3:42 PM
> >
> > On Mon, 2014-02-03 at 23:10 +, Paul Zimmerman wrote:
> > > > From: Dinh Nguyen [mailto:dingu...@altera.com]
> > > > Sent: Monday, Febr
From: Dinh Nguyen
According to the spec for the DWC2 controller, when the PRTINT interrupt fires,
the application must clear the appropriate status bit in the Host Port Control
and Status register to clear this bit.
When disconnecting an A-cable when the dwc2 host driver, the PRTINT fires, but
o
I've spent most of the day adding traces to the usbnet, xhci-ring and
ax88179_178a code to try to find out why the link doesn't come up quickly.
I've just found out something significant that someone else might
like to try and repeat.
If I add a trace print to xhci_queue_control_tx() is all seems
On Tue, Feb 04, 2014 at 12:55:25AM +0200, Sami Farin wrote:
> Asus P8Z68-V PRO GEN3 [ bios-version 3402, bios-release-date 05/07/2012 ]
>
> dmesg-3.13.0-rc3-g8d276377+-1391075301.txt
> http://pastebin.com/peJJkXZV
>
> dmesg-3.13.0-g9b0cd304+-1391076985.txt
> http://pastebin.com/p0UQsEte
>
> some
On Mon, Feb 03, 2014 at 08:51:48PM +, Paul Zimmerman wrote:
> > From: Paul Zimmerman
> > Sent: Monday, February 03, 2014 9:36 AM
> >
> >> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> >> Sent: Saturday, February 01, 2014 7:44 PM
> >>
> >> On 02/01/2014 03:00 AM, Andre Heider wrote:
>
Hi Andreas,
Kasberger Andreas wrote:
> XHCI Host Controller on Intel Panther Point with CDC/ACM dead after
> massive NAK
> PCH 82HM76 (PantherPoint) chipset connect with a Renesas RX621
> How to reproduce :
> No Reader on device /dev/ttyACM0 connected
> Writer will send in endless loop always sam
Add usb_disabled() check to prevent kernel oops when booting with "nousb"
in the cmdline:
Unable to handle kernel NULL pointer dereference at virtual address 0030
...
PC is at bus_add_device+0xe0/0x18c
LR is at device_add_groups+0x1c/0x20
...
[] (bus_add_device) from [] (device_add+0x41c/0x538
On Mon, Feb 03, 2014 at 04:45:14PM +, David Laight wrote:
> From: David Laight
> > From: David Laight
> > > From: renev...@internode.on.
> > > But there are also further issues I'm about to look at.
> > > Short 'ping' requests work, but a 'netperf' tcp rr test with 8k blocks
> > > (which probab
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 e
Commit beb7e592bc "staging: dwc2: add check on dwc2_core_reset
return" broke the B -> A role switching on OTG-enabled platforms.
This commit fixes it.
Reported-by: Dinh Nguyen
Tested-by: Dinh Nguyen
Signed-off-by: Paul Zimmerman
---
drivers/usb/dwc2/core.c | 2 +-
1 file changed, 1 insertion(+
Hi Mark and David,
Can you test the following two patches against 3.13?
Please make sure the adapter works when it's plugged directly into a USB
3.0 port and when it's plugged into a USB 2.0 hub.
Thanks,
Sarah Sharp
The following changes since commit d8ec26d7f8287f5788a494f56e8814210f0e64be:
This reverts commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e. It's a
hack that caused regressions in the usb-storage and userspace USB
drivers that use usbfs and libusb. Commit 70cabb7d992f "xhci 1.0: Limit
arbitrarily-aligned scatter gather." should fix the issues seen with the
ax88179_178a driv
> From: Andre Heider [mailto:a.hei...@gmail.com]
> Sent: Tuesday, February 04, 2014 10:44 AM
>
> Add usb_disabled() check to prevent kernel oops when booting with "nousb"
> in the cmdline:
Hi Andre,
Please resend this with GregKH on Cc, since he is the maintainer of the
USB tree and is the one w
xHCI 1.0 hosts have a set of requirements on how to align transfer
buffers on the endpoint rings called "TD fragment" rules. When the
ax88179_178a driver added support for scatter gather in 3.12, with
commit 804fad45411b48233b48003e33a78f290d227c8 "USBNET: ax88179_178a:
enable tso if usb host supp
On Tue, Feb 04, 2014 at 08:10:19PM +, Paul Zimmerman wrote:
> > From: Andre Heider [mailto:a.hei...@gmail.com]
> > Sent: Tuesday, February 04, 2014 10:44 AM
> >
> > Add usb_disabled() check to prevent kernel oops when booting with "nousb"
> > in the cmdline:
>
> Hi Andre,
>
> Please resend t
The following changes since commit 2fc5a7dace3c43e62402ab4e8800a8f1834ffe2a:
usb: chipidea: udc: using MultO at TD as real mult value for ISO-TX
(2014-01-13 15:55:19 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
tags/for-usb-lin
Add usb_disabled() check to prevent kernel oops when booting with "nousb"
in the cmdline:
Unable to handle kernel NULL pointer dereference at virtual address 0030
...
PC is at bus_add_device+0xe0/0x18c
LR is at device_add_groups+0x1c/0x20
...
[] (bus_add_device) from [] (device_add+0x41c/0x538
Don Zickus writes:
Some co-workers of mine bought Samsung laptops that had mostly usb3 ports.
Those ports did not resume correctly (the driver would timeout communicating
and fail). This led to frustration as suspend/resume is a common use for
laptops.
Poking around, I applied the reset on resu
Commit 9df89d85b407690afa46ddfbccc80bec6869971d "usbcore: set
lpm_capable field for LPM capable root hubs" was created under the
assumption that all USB host controllers should have USB 3.0 Link PM
enabled for all devices under the hosts.
Unfortunately, that's not the case. The xHCI driver relies
This reverts commit 7dd09a1af2c7150269350aaa567a11b06e831003.
Many xHCI host controllers can only handle 32-bit addresses, and writing
64-bits at a time causes them to fail. Rafał reports that USB devices
simply do not enumerate, and reverting this patch helps. Branimir
reports that his host con
This reverts commit e8b373326d8efcaf9ec1da8b618556c89bd5ffc4. Many xHCI
host controllers can only handle 32-bit addresses, and writing 64-bits
at a time causes them to fail. Reading 64-bits at a time may also cause
them to return 0x, so revert this commit as well.
Signed-off-by: Sarah Sh
On 14-02-04 02:10 PM, Sarah Sharp wrote:
> On Mon, Feb 03, 2014 at 04:45:14PM +, David Laight wrote:
>
>> From the end of section 4.10.1.1 (Short transfers)
>> - If the Short Packet occurred while processing a Transfer TRB with only an
>> ISP flag set, then two events shall be generated for t
On Tue, Feb 04, 2014 at 12:29:22PM -0800, Sarah Sharp wrote:
> The following changes since commit 2fc5a7dace3c43e62402ab4e8800a8f1834ffe2a:
>
> usb: chipidea: udc: using MultO at TD as real mult value for ISO-TX
> (2014-01-13 15:55:19 -0800)
>
> are available in the git repository at:
>
> g
On Tue, Feb 04, 2014 at 12:29:22PM -0800, Sarah Sharp wrote:
> The following changes since commit 2fc5a7dace3c43e62402ab4e8800a8f1834ffe2a:
>
> usb: chipidea: udc: using MultO at TD as real mult value for ISO-TX
> (2014-01-13 15:55:19 -0800)
>
> are available in the git repository at:
>
> g
> From: dingu...@altera.com [mailto:dingu...@altera.com]
> Sent: Tuesday, February 04, 2014 8:11 AM
>
> According to the spec for the DWC2 controller, when the PRTINT interrupt
> fires,
> the application must clear the appropriate status bit in the Host Port Control
> and Status register to clear
From: Dinh Nguyen
Hello,
This patch is my first attempt in combining the Synopsys DWC2 host and the
s3c-hsotg peripheral into a single dual-role driver.
The patch:
* Moves the s3c-hsotg driver into the dwc2 folder.
* Adds the gadget data structure into the dwc2_hsotg data structure.
* Replace
On Tue, 2014-02-04 at 21:43 +, Paul Zimmerman wrote:
> > From: dingu...@altera.com [mailto:dingu...@altera.com]
> > Sent: Tuesday, February 04, 2014 8:11 AM
> >
> > According to the spec for the DWC2 controller, when the PRTINT interrupt
> > fires,
> > the application must clear the appropria
On Tue, Dec 24, 2013 at 05:14:29PM +0100, Michal Nazarewicz wrote:
> >>This is a bug in user space. FUNCTIONFS_DISABLE event means the host
> >>has chosen a configuration with given function disabled. User-space
> >>should clean up it's state, as any pending requests of any >> kind are
> >>now in
On 14-02-04 03:11 PM, Sarah Sharp wrote:
> Hi Mark and David,
>
> Can you test the following two patches against 3.13?
>
> Please make sure the adapter works when it's plugged directly into a USB
> 3.0 port and when it's plugged into a USB 2.0 hub.
..
> are available in the git repository at:
>
From: Dinh Nguyen
According to the spec for the DWC2 controller, when the PRTINT interrupt fires,
the application must clear the appropriate status bit in the Host Port Control
and Status register to clear this bit.
When disconnecting an A-cable when the dwc2 host driver, the PRTINT fires, but
o
On 14-02-04 05:55 PM, Mark Lord wrote:
> On 14-02-04 03:11 PM, Sarah Sharp wrote:
>> Hi Mark and David,
>>
>> Can you test the following two patches against 3.13?
>>
>> Please make sure the adapter works when it's plugged directly into a USB
>> 3.0 port and when it's plugged into a USB 2.0 hub.
> .
> From: dingu...@altera.com [mailto:dingu...@altera.com]
> Sent: Tuesday, February 04, 2014 1:46 PM
>
> From: Dinh Nguyen
>
> This means that the driver can be in host or peripheral mode when the
> appropriate
> connector is used. When an A-cable is plugged in, the driver behaves in host
> mode
Use the wrapper function for retrieving the platform data instead
of accessing dev->platform_data directly. This is a cosmetic change
to make the code simpler and enhance the readability.
Signed-off-by: Jingoo Han
---
drivers/usb/chipidea/core.c |4 ++--
1 file changed, 2 insertions(+), 2 de
Hi Mathias, comments below:
On Thu, Jan 30, 2014 at 6:10 AM, Mathias Nyman
wrote:
> To create a global command queue we need to fill a command structure
> for each entry on the command ring.
>
> We start by requiring xhci_configure_endpoint() to be called with
> a proper command structure. Functi
On Thu, Jan 30, 2014 at 6:25 AM, David Laight wrote:
> From: Mathias Nyman
>> Only changes since v1 are fixing smatch warnings and errors.
>> patch 01/10
>> Check for null return from alloc_command, release lock in error path and
>> don't dereference possible null pointer in error path.
From: Bjørn Mork
Date: Tue, 4 Feb 2014 13:04:33 +0100
> This device was mentioned in an OpenWRT forum. Seems to have a "standard"
> Sierra Wireless ifnumber to function layout:
> 0: qcdm
> 2: nmea
> 3: modem
> 8: qmi
> 9: storage
>
> Signed-off-by: Bjørn Mork
Applied and queued up for -
Hi Jack,
Thanks for the information. Last week, we came to know about this patch from
benoitg...@google.com. :)
We have validated this and it works well.
Regards,
Roshan
-Original Message-
From: Jack Pham [mailto:ja...@codeaurora.org]
Sent: Wednesday, February 05, 2014 4:19 AM
To: Ros
On Wed, 2014-02-05 at 00:42 +, Paul Zimmerman wrote:
> > From: dingu...@altera.com [mailto:dingu...@altera.com]
> > Sent: Tuesday, February 04, 2014 1:46 PM
> >
> > From: Dinh Nguyen
> >
> > This means that the driver can be in host or peripheral mode when the
> > appropriate
> > connector
On Thu, Jan 30, 2014 at 6:10 AM, Mathias Nyman
wrote:
> Create a list to store command structures, add a strucure to it every time
> a command is submitted, and remove it from the list once we get a
> command completion event matching the command.
>
> Signed-off-by: Mathias Nyman
> ---
> drivers
Thank you Sarah for your work on this! Thanks to everyone involved!
2014-02-04 Sarah Sharp :
> This reverts commit 7dd09a1af2c7150269350aaa567a11b06e831003.
>
> Many xHCI host controllers can only handle 32-bit addresses, and writing
> 64-bits at a time causes them to fail. Rafał reports that USB
Hello Peter,
many many thanks for your long and detailed answer.
> On the protocol design:
>
> First, using CDC-ACM means sacrificing all structured communication
> offered by the USB packet bus and settling for such primitive use of
> USB is not a decision that should be made lightly. Almost al
55 matches
Mail list logo
