W dniu 16.07.2014 16:45, Felipe Balbi pisze:
On Wed, Jul 16, 2014 at 09:58:31AM +0200, Sebastian Andrzej Siewior wrote:
On 07/14/2014 12:36 PM, Andrzej Pietrasiewicz wrote:
Since target and its userland tool (targetcli) is available for
sometime now, maybe a look on those will give an idea
Hi Felipe,
On Wed, Jul 16, 2014 at 12:45:13PM -0500, Felipe Balbi wrote:
> On Tue, Jul 15, 2014 at 04:39:08PM +0200, Antoine Ténart wrote:
> >
> > [1] https://www.mail-archive.com/linux-usb@vger.kernel.org/msg43471.html
>
> Since this has a dependency on the other series which hasn't showed up
>
tested-by: Prakash Burla
This driver tested on AP806X with USB MSM-PHY Driver.
From: Srinivas Kandagatla
Date: Mon, Jun 30, 2014 at 10:59 PM
Subject: [PATCH v1 3/3] usb: phy: msm: Do not do runtime pm if the phy
is not idle
To:
17 lip 2014 09:13 "Andrzej Pietrasiewicz" napisał(a):
>
> W dniu 16.07.2014 16:45, Felipe Balbi pisze:
>>
>> On Wed, Jul 16, 2014 at 09:58:31AM +0200, Sebastian Andrzej Siewior wrote:
>>>
>>> On 07/14/2014 12:36 PM, Andrzej Pietrasiewicz wrote:
>
>
>
>
>>> Since target and its userland tool (targ
Section 4.4.7.2 of the USB3.0 spec says:
A zero-length data payload is a valid transfer and may be useful for
some implementations.
So, extend the logic of allowing URB_ZERO_PACKET to interrupt urbs too.
Otherwise, the kernel throws error of BOGUS transfer flags.
Signed-off-by: Am
From: Felipe Balbi
> On Wed, Jul 16, 2014 at 09:32:21PM +, Paul Zimmerman wrote:
> > > From: dingu...@altera.com [mailto:dingu...@altera.com]
> > > Sent: Wednesday, July 16, 2014 1:33 PM
> > >
> > > Update dwc2_handle_common_intr() to handle both hcd and gadget interrupts.
> > >
> > > Signed-of
Hi Alan,
On Wed, Jul 16, 2014 at 10:05:57PM +0800, Alan Stern wrote:
> On Wed, 16 Jul 2014, Pratyush Anand wrote:
>
> > Hu..May be this solution is not perfect. Have been reported with
> > at least one device which failed with this patch too. A print of
> > link_state for that device(sleep ch
From: Pratyush Anand
...
> Only side effect of long timeout: If a device was connected before
> suspend, and was removed while system was asleep, then the penalty
> would be the timeout ie 2000 ms. I do not see a way to handle this. I
> can put a FIXME note for this in patch.
...
Can't you use the
Hi David,
On Thu, Jul 17, 2014 at 05:37:44PM +0800, David Laight wrote:
> From: Pratyush Anand
> ...
> > Only side effect of long timeout: If a device was connected before
> > suspend, and was removed while system was asleep, then the penalty
> > would be the timeout ie 2000 ms. I do not see a way
Hi Andrzej,
On Thu, Jul 17, 2014 at 2:54 PM, Andrzej Pietrasiewicz
wrote:
>> Would you please help to test the v4 patch (delay work for NAPI disabling)
>> works on your platform? Thanks!
>>
>> Best regards,
>> Weinn Jheng
>>
> Sorry about the delay, I've been quite busy these days.
>
> Which bran
On Thursday 17 July 2014 01:20:54 Peter Chen wrote:
> Thanks, arnd.
>
> For chipidea generic glue layer case, if there are three devices who use this
> driver, and all devices have 32-bit bus, some devices have less 32 address
> lines.
> For example:
>
> - the device_a doesn't need to use dma_ma
Hi,
On Mon, Jun 30, 2014 at 9:33 PM, Andy Gross wrote:
> From: "Ivan T. Ivanov"
>
> These drivers handles control and configuration of the HS
> and SS USB PHY transceivers. They are part of the driver
.
[snip]
.
> +#include
> +
> +/**
> + * USB QSCRATCH Hardware registers
> + */
unused defi
Hi,
On 07/17/2014 10:47 AM, Amit Virdi wrote:
> Section 4.4.7.2 of the USB3.0 spec says:
> A zero-length data payload is a valid transfer and may be useful for
> some implementations.
>
> So, extend the logic of allowing URB_ZERO_PACKET to interrupt urbs too.
> Otherwise, the kernel t
On Thu, Jul 17, 2014 at 12:21:56PM +0200, Arnd Bergmann wrote:
> On Thursday 17 July 2014 01:20:54 Peter Chen wrote:
> > Thanks, arnd.
> >
> > For chipidea generic glue layer case, if there are three devices who use
> > this
> > driver, and all devices have 32-bit bus, some devices have less 32 a
Add two device IDs found in an out-of-tree driver downloadable
from Netgear.
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index c4638c67f6b9..22756db53dca 100644
--- a/driver
Huawei's usage of the subclass and protocol fields is not 100%
clear to us, but there appears to be a very strict system.
A device with the "shared" device ID 12d1:1506 and this NCM
function was recently reported (showing only default altsetting):
Interface Descriptor:
bLength
On Thursday 17 July 2014 19:19:15 Peter Chen wrote:
>
> Currently, we are designing a generic driver, we don't know what's the
> hardware architecture, we are trying to find a solution how to set
> dma mask for all possible devices which will use this driver, Antoine's
> this patch is trying to co
Hi Greg,
Currently, the gadget driver will handle ZLP, abbas's patch
disables the hardware ZLP at udc driver to avoid sending ZLP twice
at some cases.
Abbas Raza (1):
usb: chipidea: udc: Disable auto ZLP generation on ep0
drivers/usb/chipidea/udc.c |4 ++--
1 files changed, 2 insertions(+
From: Abbas Raza
There are 2 methods for ZLP (zero-length packet) generation:
1) In software
2) Automatic generation by device controller
1) is implemented in UDC driver and it attaches ZLP to IN packet if
descriptor->size < wLength
2) can be enabled/disabled by setting ZLT bit in the QH
Whe
On Fri, Jul 11, 2014 at 02:29:34PM +0200, Markus Pargmann wrote:
> -ENODEV is interpreted by the generic driver probing function as a
> non-matching driver. This leads to a missing probe failure message.
>
> Also a missing USB PHY is more of an invalid configuration of the usb
> driver because it
On Thu, Jul 17, 2014 at 07:19:15PM +0800, Peter Chen wrote:
> Currently, we are designing a generic driver, we don't know what's the
> hardware architecture, we are trying to find a solution how to set
> dma mask for all possible devices which will use this driver, Antoine's
> this patch is trying
The preparation for configfs has been sent as a separate
series:
www.spinics.net/lists/linux-usb/msg110639.html
like Laurent suggests.
This series is rebased onto Felipe's testing/next with
gadget directory cleanup series applied.
I'm sending this series again basically in order for it to be
ea
When configfs is integrated, to_f_uvc_opts() is expected to be defined
with struct config_item pointer as argument. to_f_uvc_opts() in u_uvc.h
takes a different argument, so rename it to avoid conflicts.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/usb/gadget/function/f_uvc.c | 6 +++---
dri
configfs.h depends on some definitions from linux/usb/composite.h.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/usb/gadget/configfs.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/configfs.h b/drivers/usb/gadget/configfs.h
index a14ac79..d23e189 100644
--- a/drivers/
Hi Srini,
On Thu, Jul 17, 2014 at 6:19 PM, wrote:
> From: Srinivas Kandagatla
>
> This patch makes the phy reset clk and reset line optional as this clk
> is not available on boards like IFC6410 with APQ8064.
>
.
[snip]
.
>
> pdata->mode = of_usb_get_dr_mode(node);
> if (pdata->
On 17/07/14 13:54, pramod gurav wrote:
Hi Srini,
On Thu, Jul 17, 2014 at 6:19 PM, wrote:
From: Srinivas Kandagatla
This patch makes the phy reset clk and reset line optional as this clk
is not available on boards like IFC6410 with APQ8064.
.
[snip]
.
pdata->mode = of_usb_get_
When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller
[1022:7814], the second hotplugging will experience the USB 3.0 pen
drive is recognized as high-speed device. After bisecting the kernel,
I found the commit number 41e7e056cdc662f704fa9262e5c6e213b4ab45dd
(USB: Allow USB 3.0 ports
As the discussion in http://comments.gmane.org/gmane.linux.usb.general/107011,
I found that [AMD] FCH USB XHCI Controller [1022:7814] the USB 3.0 disk
can't work in SuperSpeed after several times of hotplug. After doing some
experiments and bisection, I found the bug is caused by
41e7e056cdc662
Hi,
On Thu, Jul 17, 2014 at 02:14:15PM +0100, Srinivas Kandagatla wrote:
> On 17/07/14 13:54, pramod gurav wrote:
> >Hi Srini,
> >
> >On Thu, Jul 17, 2014 at 6:19 PM, wrote:
> >>From: Srinivas Kandagatla
> >>
> >>This patch makes the phy reset clk and reset line optional as this clk
> >>is not
On 17/07/14 15:39, Felipe Balbi wrote:
Hi,
On Thu, Jul 17, 2014 at 02:14:15PM +0100, Srinivas Kandagatla wrote:
On 17/07/14 13:54, pramod gurav wrote:
Hi Srini,
On Thu, Jul 17, 2014 at 6:19 PM, wrote:
From: Srinivas Kandagatla
This patch makes the phy reset clk and reset line optional
Gadget function files have been moved to a "function" subdirectory.
Signed-off-by: Andrzej Pietrasiewicz
---
Documentation/DocBook/gadget.tmpl | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/DocBook/gadget.tmpl
b/Documentation/DocBook/gadget.tmpl
ind
Hi,
On Thu, Jul 17, 2014 at 12:07:26PM +0530, Amit Virdi wrote:
> >>can you send some logs of this patchset working ? What output should we
> >>expect ? How to run it ?
> >>
> >>(sure, we could just read the source code and figure it out, but it's
> >>good 'documentation' to put on the commit log)
On Thu, 17 Jul 2014, Pratyush Anand wrote:
> I got one sony usb stick (054C:05B8) which does not take 2S but
> certainly it takes more than 400 ms. I took the analyzer log with this
> device..and it tells me that this device is not behaving the right
> way. See the attached snapshot:
>
> -- Host
On Thu, 17 Jul 2014, Amit Virdi wrote:
> Section 4.4.7.2 of the USB3.0 spec says:
> A zero-length data payload is a valid transfer and may be useful for
> some implementations.
>
> So, extend the logic of allowing URB_ZERO_PACKET to interrupt urbs too.
> Otherwise, the kernel throws e
On Thu, 17 Jul 2014, David Laight wrote:
> From: Pratyush Anand
> ...
> > Only side effect of long timeout: If a device was connected before
> > suspend, and was removed while system was asleep, then the penalty
> > would be the timeout ie 2000 ms. I do not see a way to handle this. I
> > can put
On Thu, 17 Jul 2014, Gavin Guo wrote:
> When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller
> [1022:7814], the second hotplugging will experience the USB 3.0 pen
> drive is recognized as high-speed device. After bisecting the kernel,
> I found the commit number 41e7e056cdc662f704fa
On Mon, Jun 30, 2014 at 09:59:57PM -0700, Greg KH wrote:
> On Mon, Jun 30, 2014 at 01:40:35PM -0500, Felipe Balbi wrote:
> > Hi Greg,
> >
> > Here's my second set of fixes. Note the revert of the patch Michal
> > asked to revert.
> >
> > Please consider merging to your usb-linus branch. Let me kn
On Thu, Jul 17, 2014 at 10:08:56AM -0500, Felipe Balbi wrote:
> On Mon, Jun 30, 2014 at 09:59:57PM -0700, Greg KH wrote:
> > On Mon, Jun 30, 2014 at 01:40:35PM -0500, Felipe Balbi wrote:
> > > Hi Greg,
> > >
> > > Here's my second set of fixes. Note the revert of the patch Michal
> > > asked to re
Hi all,
It has cost me quite some time to get to the bottom of this (which is
not even the real bottom).
When I generate heavy-io (make -j4 modules or cp -pr a git clone
of the kernel), urbs start completing with EPROTO errors when using a
Renesas uPD720231 chipset usb-3 uas to sata bridge with a
On Thu, Jul 17, 2014 at 08:26:57AM -0700, Greg KH wrote:
> On Thu, Jul 17, 2014 at 10:08:56AM -0500, Felipe Balbi wrote:
> > On Mon, Jun 30, 2014 at 09:59:57PM -0700, Greg KH wrote:
> > > On Mon, Jun 30, 2014 at 01:40:35PM -0500, Felipe Balbi wrote:
> > > > Hi Greg,
> > > >
> > > > Here's my secon
When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller
[1022:7814], the second hotplugging will experience the USB 3.0 pen
drive is recognized as high-speed device. After bisecting the kernel,
I found the commit number 41e7e056cdc662f704fa9262e5c6e213b4ab45dd
(USB: Allow USB 3.0 ports
As the discussion in http://comments.gmane.org/gmane.linux.usb.general/107011,
I found that [AMD] FCH USB XHCI Controller [1022:7814] the USB 3.0 disk
can't work in SuperSpeed after several times of hotplug. After doing some
experiments and bisection, I found the bug is caused by
41e7e056cdc662
This patch provides mechanism for subordinate devices to check
whether the DWC3 core probed successfully or otherwise. Useful
if PHYs are required to configure controllers, but aren't yet
available. The DWC3 core driver will defer probe if PHYs are
unavailable, however subordinate DWC3 drivers cu
Hi,
On Thu, Jul 17, 2014 at 06:13:33PM +0100, Lee Jones wrote:
> This patch provides mechanism for subordinate devices to check
> whether the DWC3 core probed successfully or otherwise. Useful
> if PHYs are required to configure controllers, but aren't yet
> available. The DWC3 core driver will
Hi,
On Thu, Jul 17, 2014 at 10:03:02AM +0200, Antoine Ténart wrote:
> Hi Felipe,
>
> On Wed, Jul 16, 2014 at 12:45:13PM -0500, Felipe Balbi wrote:
> > On Tue, Jul 15, 2014 at 04:39:08PM +0200, Antoine Ténart wrote:
> > >
> > > [1] https://www.mail-archive.com/linux-usb@vger.kernel.org/msg43471.h
On Thu, Jul 17, 2014 at 7:55 AM, Alan Stern wrote:
>
> I can't say this is actually wrong, but have you ever encountered a
> situation where this would be needed? How often does anyone need to do
> a multi-packet transfer over an interrupt endpoint?
>
Hi Alan,
I did some testing with multi inter
Julius, I have done the testing; sorry for one day delay. I bought
some new hardware and was busy assembling test rigs; the end result is
that I was able to test four USB 3.0 controllers : Intel (Z97
chipset), NEC uPD720200 and two Asmedia. I tested two kernel versions:
3.2.61 and 3.16.0-rc5, both
Tested-by: Maciej Puzio
On Tue, Jul 8, 2014 at 2:01 PM, Julius Werner wrote:
> Commit 1f81b6d22 "usb: xhci: Prefer endpoint context dequeue pointer
> over stopped_trb" changed the logic in xhci_find_new_dequeue_state() to
> only use the Endpoint Context's TR Dequeue Pointer instead of the last
>
On Thu, Jul 17, 2014 at 06:30:24AM -0400, kiran.pad...@smartplayin.com wrote:
> Hi,
>
> On Mon, Jun 30, 2014 at 9:33 PM, Andy Gross wrote:
> > From: "Ivan T. Ivanov"
> >
> > These drivers handles control and configuration of the HS
> > and SS USB PHY transceivers. They are part of the driver
>
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Maciej Puzio
> Sent: Thursday, July 17, 2014 11:25 AM
>
> Tested-by: Maciej Puzio
>
> On Tue, Jul 8, 2014 at 2:01 PM, Julius Werner wrote:
> > Commit 1f81b6d22 "usb: xhci: Prefer endpoint context de
On Thu, 17 Jul 2014, Steve Calfee wrote:
> On Thu, Jul 17, 2014 at 7:55 AM, Alan Stern wrote:
> >
> > I can't say this is actually wrong, but have you ever encountered a
> > situation where this would be needed? How often does anyone need to do
> > a multi-packet transfer over an interrupt endpo
When a host controller dies, we don't need to wait for a driver to
time out. We can shut down its URBs immediately. Without this
change, we can end up waiting 30 seconds for a mass-storage transfer
to time out.
Signed-off-by: Alan Stern
---
[as1761]
drivers/usb/core/driver.c |7 --
> Hmm. Wouldn't it be safer to have a quirk for this, and only enable
> the workaround if the Asmedia controller is detected? This code is so
> complicated that it is difficult to see whether this could have a
> harmful effect on controllers without the bug.
Sorry for making it complicated, but it
This patch makes the phy reset clk and reset line optional as this clk
is not available on boards like IFC6410 with APQ8064.
phy-reset clk is only used as argument to the mach level callbacks, so
this patch adds condition before clk_get calls so that the driver
wouldn't fail on SOCs which do not h
Apparently nobody ever remembered to add Scatter-Gather support to
ohci-hcd. This patch adds it.
Signed-off-by: Alan Stern
---
[as1760]
drivers/usb/host/ohci-hcd.c | 38 ++
drivers/usb/host/ohci-q.c | 54 +---
2 file
The debug routine fill_async_buffer() in ohci-hcd is buggy: It never
produces any output because it forgets to initialize the output buffer
size. Also, the debug routine ohci_dump() has an unused argument.
This patch adds the correct initialization and removes the unused
argument.
Signed-off-by:
This patch fixes a bug in ohci-hcd. When an URB is unlinked, the
corresponding Endpoint Descriptor is added to the ed_rm_list and taken
off the hardware schedule. Once the ED is no longer visible to the
hardware, finish_unlinks() handles the URBs that were unlinked or have
completed. If any URBs
On Thu, Jul 17, 2014 at 12:32 PM, Alan Stern wrote:
> On Thu, 17 Jul 2014, Steve Calfee wrote:
>
>> Hi Alan,
>>
>> I did some testing with multi interrupt transfers some time ago. You
>> can get allocated a guaranteed 3x1024 time slot per uframe for an
>> interval of your choice on usb 2.0. So zlp
On Thu, Jul 17, 2014 at 04:32:26PM -0400, Alan Stern wrote:
> The debug routine fill_async_buffer() in ohci-hcd is buggy: It never
> produces any output because it forgets to initialize the output buffer
> size. Also, the debug routine ohci_dump() has an unused argument.
>
> This patch adds the c
From: Bjørn Mork
Date: Thu, 17 Jul 2014 13:33:51 +0200
> Add two device IDs found in an out-of-tree driver downloadable
> from Netgear.
>
> Signed-off-by: Bjørn Mork
Applied and queued up for -stable.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
From: Bjørn Mork
Date: Thu, 17 Jul 2014 13:34:09 +0200
> Huawei's usage of the subclass and protocol fields is not 100%
> clear to us, but there appears to be a very strict system.
>
> A device with the "shared" device ID 12d1:1506 and this NCM
> function was recently reported (showing only defa
On Mon, Jul 14, 2014 at 10:47:55PM +0200, Oliver Neukum wrote:
> On Mon, 2014-07-14 at 11:04 -0400, Alan Stern wrote:
> > On Mon, 14 Jul 2014, Oliver Neukum wrote:
> >
> > > On Mon, 2014-07-14 at 07:50 -0700, Greg KH wrote:
> > >
> > > > So if I have hubs with the same "broken" port, I'll only ge
On Tuesday, July 01, 2014 1:04 AM, Felipe Balbi wrote:
>
> From: "Ivan T. Ivanov"
>
> DWC3 glue layer is hardware layer around Synopsys DesignWare
> USB3 core. Its purpose is to supply Synopsys IP with required
> clocks, voltages and interface it with the rest of the SoC.
>
> Signed-off-by: Iva
On Thu, Jul 17, 2014 at 05:55:22PM +0800, Pratyush Anand wrote:
> Hi David,
>
> On Thu, Jul 17, 2014 at 05:37:44PM +0800, David Laight wrote:
> > From: Pratyush Anand
> > ...
> > > Only side effect of long timeout: If a device was connected before
> > > suspend, and was removed while system was as
I am assuming this is a stupid question but since I am new I will ask it anyway.
Can the usb_bus structure be Null? If can I will send it a patch removing the
fix mes on lines 854 and 878 of hcd.c .
Cheers Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body o
Following sparse warnings were reported by kbuild test bot
drivers/usb/misc/lvstest.c:314:28: sparse: incorrect type in assignment
(different base types)
drivers/usb/misc/lvstest.c:314:28:expected unsigned short [unsigned]
[usertype] portchange
drivers/usb/misc/lvstest.c:314:28:got
On 7/17/2014 8:06 PM, Felipe Balbi wrote:
that's good, thanks. But my tree is now closed for v3.17, once v3.17-rc1
is out I'll start queueing for v3.18.
No probs!
I'll send the patch with updated commit msg.
BTW, I think you mean you'll queue for kernel v3.17 (v3.16 is yet to be
released as v
67 matches
Mail list logo
