On Thu, Dec 04, 2014 at 01:06:07PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Commit 1290a958d48e ("usb: phy: propagate __of_usb_find_phy()'s error on
> failure") broke platforms that rely on deferred probing to order probing
> of PHY and host controller drivers. The reason is that t
According to the datasheet, when transfer using DMA, the control
setting for IN packet only need END_BUF_EN, END_BUF_IE, CH_EN,
while for OUT packet, need more two bits END_TR_EN and END_TR_IE
to be configured.
Signed-off-by: Bo Shen
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 6 +++---
1 fil
When receive data, the RXRDY in status register set by hardware
after a new packet has been stored in the endpoint FIFO. When it
is copied from FIFO, this bit is cleared which make the FIFO can
be accessed again.
In the receive_data() function, this bit RXRDY has been cleared.
So, after the receiv
Hi all,
At the first two patches, I add identification registers APIs, we can get
controller's revision by using this APIs. Since I don't have enough spec,
if there are any errors, tell me.
At the third patch, I implement an errata for revision 2.40a, hope it can fix
the problem Sanchayan Maity r
Using hw_write_id_reg and hw_read_id_reg to write and read identification
registers contents, they can be used to get controller information, change
some system configurations, and so on.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci.h | 39 +++
1 file
Define ci_get_revision API to know the controller revision
information according to chipidea 1.1a, 2.0a and 2.5a spec.
Besides, add one entry at struct ci_hdrc to indicate revision
information, it can be used for adding different code for
revisions, eg kinds of errata.
Signed-off-by: Peter Chen
-
At chipidea revision 2.40a, there is a below errata:
9000531823 B2-Medium Adding a dTD to a Primed Endpoint May Not Get
Recognized
Title: Adding a dTD to a Primed Endpoint May Not Get Recognized
Impacted Configuration: All device mode configurations.
Description:
There is an issue wit
Hello.
On 12/17/2014 5:08 AM, Peter Chen wrote:
On the Renesas R8A7791 SoC based boards there's MAX3355 USB OTG chip and
mini-AB USB connector corresponding to USB port 0 driven either by EHCI/OHCI
or Renesas USBHS gadget controller. And we'd like the host/gadget drivers to
work based on the
On 12/17/2014 02:05 PM, Peter Chen wrote:
> Hi all,
>
> At the first two patches, I add identification registers APIs, we can get
> controller's revision by using this APIs. Since I don't have enough spec,
> if there are any errors, tell me.
>
> At the third patch, I implement an errata for revis
On Wed, Dec 17, 2014 at 05:31:40PM +0530, Sanchayan Maity wrote:
> On 12/17/2014 02:05 PM, Peter Chen wrote:
> > Hi all,
> >
> > At the first two patches, I add identification registers APIs, we can get
> > controller's revision by using this APIs. Since I don't have enough spec,
> > if there are
DWC2 module on Exynos SoCs is used only as peripheral controller (UDC),
so add support for selecting default initial state for dual-role mode. The
default init mode can be overridden by device tree 'dr_mode' property.
This patch enables to use usb gadget on Exynos SoCs, when DWC2 driver has
been co
Problem: up/dowlink UDP with iperf3 over GSM crashes Huawei E3276 USB
modem on 32-bit Debian-stable (wheezy) with 3.13 kernel and newer
kernels. Error also seen on 64-bit machines/Linux kernels.
Keywords: huawei_cdc_ncm, GSM, cdc-wdm, wwan0, netdev watchdog
Detailed problem description: Sending/r
>>
>> My configuration:
>> -
>>
>> Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
>> Linux
>> kernel: 2.6.31, using EHCI USB driver
>> Hub: 4-PORT USB 1.1 HUB (Texas Instruments PN: tusb2046b)
>> Devices: 4 USB 1.1 audio codecs (Texas Instruments PN: pcm2901
On Wednesday 17 December 2014 23:33:02 Sneeker. Yeh wrote:
> >
> >No need for playing games with child devices, just see how the other drivers
> >do
> >it.
>
> I am wondering if this is what you mentioned here? :
> Hcd21: f_usb20ho {
> compatible = "fujitsu,f_usb20ho";
> ...
>
On Tue, 16 Dec 2014, Tobias Jakobi wrote:
> Alan Stern wrote:
> > How about providing some information (system logs, etc.)?
> >
> > Alan Stern
>
> Hello,
>
> I've just added dmesg and lsusb output. If you need anything else,
> please let me know!
You didn't say which device was the one causing
On Mon, 15 Dec 2014, Michael Tessier wrote:
> Hi,
>
> I am dealing with a USB EHCI driver bug. Here is the info:
>
> My configuration:
> -
>
> Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
> Linux kernel: 2.6.31, using EHCI USB driver
As mentioned by othe
Alan Stern wrote:
> You didn't say which device was the one causing the problem. I assume
> it was the 4-3 device; that's the only thing which appears to be a
> USB-3 drive.
Correct, at the moment I'm using a USB3 enclosure with a JMicron ATA-USB
bridge. However the same problem already occured wi
Please use Reply-To-All so that your messages get sent to the mailing
list as well as to me.
On Thu, 11 Dec 2014, Rubén Herrero wrote:
> There you go.
>
> On Thu, Dec 11, 2014 at 8:22 PM, Alan Stern wrote:
> > On Tue, 9 Dec 2014, Rubén Herrero wrote:
> >
> >> With systemd 217, systemd-udevd co
On Sat, 13 Dec 2014, Udo van den Heuvel wrote:
> Hello,
>
> I noticed an usb related issue when recording from my airspy device;
> so I created a bug in the bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id=89671
>
> Please let me know what info I should add to help find the root cause.
W
On Wed, Dec 17, 2014 at 09:30:03AM +0100, Thierry Reding wrote:
> On Thu, Dec 04, 2014 at 01:06:07PM +0100, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > Commit 1290a958d48e ("usb: phy: propagate __of_usb_find_phy()'s error on
> > failure") broke platforms that rely on deferred probing t
On Wed, 17 Dec 2014, Tobias Jakobi wrote:
> Alan Stern wrote:
> > You didn't say which device was the one causing the problem. I assume
> > it was the 4-3 device; that's the only thing which appears to be a
> > USB-3 drive.
> Correct, at the moment I'm using a USB3 enclosure with a JMicron ATA-US
Hello.
On 12/17/2014 03:31 AM, Chanwoo Choi wrote:
MAX3355E chip integrates a charge pump and comparators to enable a system with
an integrated USB OTG dual-role transceiver to function as a USB OTG dual-role
device. In addition to sensing/controlling Vbus, the chip also passes thru the
ID sign
Hi,
I'm very sorry for the delayed response.
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Felipe Balbi
> Sent: Wednesday, November 05, 2014 8:01 AM
>
> Hi,
>
> On Wed, Nov 05, 2014 at 01:55:17AM +0300, Sergei Shtyl
On 2014-12-17 18:25, Alan Stern wrote:
> On Sat, 13 Dec 2014, Udo van den Heuvel wrote:
> What are we supposed to see? The lsusb output in the bug report lists
> a bunch of devices, but it's not clear which one is the airspy.
I did not program the tools. But the other devices are keyboard, webca
On Wed, Dec 17, 2014 at 10:04:35AM +0530, Sanchayan Maity wrote:
> On 12/17/2014 05:46 AM, Peter Chen wrote:
> > On Tue, Dec 16, 2014 at 04:15:08PM +0530, Sanchayan Maity wrote:
> >> On 12/16/2014 02:15 PM, Peter Chen wrote:
> >>> On Tue, Dec 16, 2014 at 10:50:59AM +0530, Sanchayan Maity wrote:
> >
On 2014-12-17 18:25, Alan Stern wrote:
>> Please let me know what info I should add to help find the root cause.
>
> What are we supposed to see? The lsusb output in the bug report lists
> a bunch of devices, but it's not clear which one is the airspy.
Perhaps bus 4, device 10?
Udo
--
To unsu
On 12/18/2014 10:24 AM, Peter Chen wrote:
> On Wed, Dec 17, 2014 at 10:04:35AM +0530, Sanchayan Maity wrote:
>> On 12/17/2014 05:46 AM, Peter Chen wrote:
>>> On Tue, Dec 16, 2014 at 04:15:08PM +0530, Sanchayan Maity wrote:
On 12/16/2014 02:15 PM, Peter Chen wrote:
> On Tue, Dec 16, 2014 at
On Thu, Dec 18, 2014 at 12:25:41PM +0530, Sanchayan Maity wrote:
> On 12/18/2014 10:24 AM, Peter Chen wrote:
> > On Wed, Dec 17, 2014 at 10:04:35AM +0530, Sanchayan Maity wrote:
> >> On 12/17/2014 05:46 AM, Peter Chen wrote:
> >>> On Tue, Dec 16, 2014 at 04:15:08PM +0530, Sanchayan Maity wrote:
> >
28 matches
Mail list logo
