> -Original Message-
> From: Nikhil Badola [mailto:nikhil.bad...@freescale.com]
> Sent: Monday, August 17, 2015 9:54 AM
> To: linux-ker...@vger.kernel.org; devicet...@vger.kernel.org; linux-
> u...@vger.kernel.org
> Cc: ba...@ti.com; Badola Nikhil-B46172
> Subject: [PATCH 1/3][v2] Document
From: Alan Stern
With this change, the host and gadget doesn't need to agree with transfer
length for comparing the data, since they doesn't know each other's
transfer size, but know max packet size.
Signed-off-by: Peter Chen
Acked-by: Michal Nazarewicz
(Fixed the 'line over 80 characters warn
For ctrl out test, it needs length > vary, so in order to run it with
default parameters, we do this change.
Acked-by: Michal Nazarewicz
Cc: Michal Nazarewicz
Signed-off-by: Peter Chen
---
tools/usb/testusb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/usb/tes
The element of urbs array will be initialized at below code
at once.
for (i = 0; i < param->sglen; i++) {
urbs[i] = iso_alloc_urb(udev, pipe, desc,
param->length, offset);
Acked-by: Michal Nazarewicz
Signed-off-by: Peter Chen
---
Since the host and gadget can't agree with transfer length before
each transfer, but they agree with max packet size for each
endpoint, we use max packet size to format data pattern.
Acked-by: Michal Nazarewicz
Signed-off-by: Peter Chen
---
drivers/usb/gadget/function/f_sourcesink.c | 6 --
Using the same data format "buf[j] = (u8)(i + j)" among
write, compare buf, and console output stage.
Acked-by: Michal Nazarewicz
Signed-off-by: Peter Chen
---
drivers/usb/misc/usbtest.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/misc/usbtest.c b/drive
The 'length' is the transfer length, not the packet size, so
change the help text.
Acked-by: Michal Nazarewicz
Cc: Michal Nazarewicz
Signed-off-by: Peter Chen
---
tools/usb/testusb.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/usb/testusb.c b/tools/usb/tes
Allocate the size of urb pointer array according to testusb's
parameter sglen, and limits the length of sglen as MAX_SGLEN
(128 currently).
Acked-by: Michal Nazarewicz
Signed-off-by: Peter Chen
---
drivers/usb/misc/usbtest.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff -
Changes for v2:
- Add le16_to_cpu to read descriptor value [Patch 5/7]
- Add MAX_SGLEN (128 currently) for maximum sglen [Patch 1/7]
- Using local variable to save max macket size value, in case
some compiler create more code for dereferences all the pointers
at every iteration. [Patch 5/7]
H
I am sorry, I forget to remove them. It is generated by git and I send the
patch with outlook.
I will use git-send-email instead next time if my email account work.
Regards
Du, Changbin
> -Original Message-
> From: 'Greg Kroah-Hartman' [mailto:gre...@linuxfoundation.org]
> Sent: Monday,
On Mon, Aug 31, 2015 at 09:49:51AM -0500, Nathan Sullivan wrote:
> Due to having hardware tx buffers less than 512 bytes in size, streaming
> must be enabled on the Zynq for the udc to work at all. Add platform data
> specific to the Zynq udc, which does not set the CI_HDRC_DISABLE_STREAMING
> fla
On Mon, Aug 31, 2015 at 03:17:06PM +0200, Oliver Neukum wrote:
> On Mon, 2015-08-31 at 13:01 +0200, Michal Nazarewicz wrote:
> > On Fri, Aug 28 2015, Peter Chen wrote:
> > > Allocate the size of urb pointer array according to testusb's
> > > parameter sglen.
> > >
> > > Signed-off-by: Peter Chen
>
From: Dave Hansen
I have a .config with CONFIG_PM disabled. I get the following
whenever compiling the xhci driver:
drivers/usb/host/xhci-pci.c:192:13: warning: âxhci_pme_quirkâ defined but
not used [-Wunused-function]
Looks like we just need to move xhci_pme_quirk() to be underneath
the
On 01/06/2015 03:58 AM, Bjørn Mork wrote:
> Johan Hovold writes:
>
>> Ok, let's move the PID to option and if it turns out that more of these
>> devices require the modem-control signals (e.g. with more recent
>> firmware) we can consider moving it back after adding such support to
>> qcserial.
>>
Hello.
On 08/31/2015 07:48 PM, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä
This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
As it breaks g_ether on my Baytrail FFRD8 device. Everything starts out
fine, but after a bit of data has been transferred it just stops
flowi
On Thu, Aug 20, 2015 at 12:38 PM, Duc Dang wrote:
> The xhci platform driver needs to work on systems that
> either only support 64-bit DMA or only support 32-bit DMA.
> Attempt to set a coherent dma mask for 64-bit DMA, and
> attempt again with 32-bit DMA if that fails.
>
> [dhdang: regenerate th
Hi,
On Mon, Aug 31, 2015 at 01:50:10PM -0500, Felipe Balbi wrote:
> > > > From: Ville Syrjälä
> > > >
> > > > This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
> > > >
> > > > As it breaks g_ether on my Baytrail FFRD8 device. Everything starts out
> > > > fine, but after a bit of da
Hi,
On Mon, Aug 31, 2015 at 08:25:10PM +0300, Ville Syrjälä wrote:
> On Mon, Aug 31, 2015 at 11:54:13AM -0500, Felipe Balbi wrote:
> > On Mon, Aug 31, 2015 at 07:48:28PM +0300, ville.syrj...@linux.intel.com
> > wrote:
> > > From: Ville Syrjälä
> > >
> > > This reverts commit 8f2c9544aba63613430
Other Sierra Wireless MC73xx devices exist, with different USB IDs.
Cc: Bjørn Mork
Signed-off-by: David Ward
---
drivers/usb/serial/option.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 876423b..cc3e1c7
On Mon, Aug 31, 2015 at 11:54:13AM -0500, Felipe Balbi wrote:
> On Mon, Aug 31, 2015 at 07:48:28PM +0300, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
> >
> > As it breaks g_ether on my Baytrail FFRD8 device. E
On Mon, Aug 31, 2015 at 07:48:28PM +0300, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
>
> As it breaks g_ether on my Baytrail FFRD8 device. Everything starts out
> fine, but after a bit of data has been transferred
From: Ville Syrjälä
This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
As it breaks g_ether on my Baytrail FFRD8 device. Everything starts out
fine, but after a bit of data has been transferred it just stops
flowing.
Note that I do get a bunch of these "NOHZ: local_softirq_pending 08
This patch contains a fix for a real world interop problem found
when using the Synopsis DWC2 USB controller with isochronous audio as
detailed in the commit message.
Changes from v1:
- Address code review comments as per previous responses:
- renamed parity_set to has_correct_parity and reorder
From: Roman Bacik
USB OTG driver in isochronous mode has to set the parity of the receiving
microframe. The parity is set to even by default. This causes problems for
an audio gadget, if the host starts transmitting on odd microframes.
This fix uses Incomplete Periodic Transfer interrupt to togg
Hi Felipe,
On ven., août 21 2015, Gregory CLEMENT
wrote:
>> According to the OTG specification after a timeout of
>> OTG_TIME_A_WAIT_VRISE (the maximum value is 100ms) the driver must
>> move from the state a_wait_vrise to the state a_wait_bcon. However,
>> the dsps version of musb does not ha
Hi,
This series add support to DWC3 core to conserve
power during system sleep by setting the USB
DRVVBUS line to a lower power consuming state.
Tested to make sure USB host and device works on
AM437x with v4.2. Tested for power savings on v4.1
kernel where there is an implementation of suspend-
Add support for USB DRVVBUS pinctrl state change during
suspend/resume. This helps is conserving power during
system sleep.
Signed-off-by: Sekhar Nori
---
drivers/usb/dwc3/core.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index ff577
From: Dave Gerlach
Add pinctrl default and sleep states for each usb device.
The only pin that can be controlled is USB_DRVVBUS, this
must be set to MUX_MODE7 (gpio) during sleep to conserve
power.
Signed-off-by: Dave Gerlach
[nsek...@ti.com: move pins to core dwc3]
Signed-off-by: Sekhar Nori
On Mon, Aug 31, 2015 at 06:03:17PM +0300, Mathias Nyman wrote:
> It's in 4.2-rc6.
> I understood you were running 4.2-rc8, so it should be there.
Yes, the error was with 4.2-rc8.
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To unsubscribe from this list: send the line "unsubscribe linux-u
The "ERROR Transfer event TRB DMA ptr not part of curren..." errors are a bit
worrying.
I was hoping these would no longer occur after the last off by one fix:
commit 7895086afde2a05fa24a0e410d8e6b75ca7c8fdd
xhci: fix off by one error in TRB DMA address boundary check
That's in 3.12? Th
Due to having hardware tx buffers less than 512 bytes in size, streaming
must be enabled on the Zynq for the udc to work at all. Add platform data
specific to the Zynq udc, which does not set the CI_HDRC_DISABLE_STREAMING
flag.
Based on a patch by the same name from the Xilinx vendor tree.
Signe
Document the binding for the zynq specific chipidea UDC binding.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b/Documentation/devicetree/bin
> -Original Message-
> From: Robert Baldyga [mailto:r.bald...@samsung.com]
> Sent: Monday, August 31, 2015 4:46 PM
> To: Kaukab, Yousaf; linux-usb@vger.kernel.org; ba...@ti.com;
> john.y...@synopsys.com
> Cc: Herrero, Gregory; he...@sntech.de; diand...@chromium.org;
> dingu...@opensource.al
On 08/28/2015 12:27 PM, Mian Yousaf Kaukab wrote:
> Hi,
> This series consists of various bug fixes for both host and gadget
> sides. All patches are verified on dwc2 v3.0a with dedicated fifos.
> It would be good to get some Tested-bys for other platforms.
>
> It is based on testing/next branch i
On Mon, Aug 31, 2015 at 05:28:10PM +0300, Mathias Nyman wrote:
> The max exit latency should tell how long it can maximum take for the entire
> link between host
> and device to wake up and be fully functional. Isoc transfer will send a PING
> TP max exit
> latency before the first data transfer
> -Original Message-
> From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
> Sent: Friday, August 28, 2015 11:50 PM
> To: Kaukab, Yousaf; linux-usb@vger.kernel.org; ba...@ti.com;
> john.y...@synopsys.com
> Cc: Herrero, Gregory; he...@sntech.de; diand...@chromium.org;
> r.bald
On 29.08.2015 17:06, Steinar H. Gunderson wrote:
On Sat, Aug 29, 2015 at 12:17:25AM +0200, Steinar H. Gunderson wrote:
I've noticed (with the CONFIG_PM=y kernel) that sometimes this comes up when
inserting the device:
[ 136.370917] usb 3-2: Set SEL for device-initiated U2 failed.
I don't know
On Fri, 28 Aug 2015, Peter Chen wrote:
> Since the host and gadget can't agree with transfer length before
> each transfer, but they agree with max packet size for each
> endpoint, we use max packet size to format data pattern.
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/gadget/function/f
On Mon, Aug 31, 2015 at 04:51:22AM +, Du, Changbin wrote:
> >From 08df419517694c4dd9ff328f5644b46a99c2999e Mon Sep 17 00:00:00 2001
> From: "Du, Changbin"
> Date: Thu, 23 Jul 2015 20:08:04 +0800
> Subject: [PATCH v2] usb/gadget: make composite gadget meet usb compliance for
> vbus draw
What
On Mon, 2015-08-31 at 13:01 +0200, Michal Nazarewicz wrote:
> On Fri, Aug 28 2015, Peter Chen wrote:
> > Allocate the size of urb pointer array according to testusb's
> > parameter sglen.
> >
> > Signed-off-by: Peter Chen
>
> Acked-by: Michal Nazarewicz
>
> I vaguely recall that LLVM fans got m
On Fri, Aug 28 2015, Peter Chen wrote:
> From: Alan Stern
>
> With this change, the host and gadget doesn't need to agree with transfer
> length for comparing the data, since they doesn't know each other's
> transfer size, but know max packet size.
>
> (Fixed the 'line over 80 characters warning'
On Fri, Aug 28 2015, Peter Chen wrote:
> For ctrl out test, it needs length > vary, so in order to run it with
> default parameters, we do this change.
>
> Cc: Michal Nazarewicz
Acked-by: Michal Nazarewicz
> Signed-off-by: Peter Chen
> ---
> tools/usb/testusb.c | 4 ++--
> 1 file changed, 2 i
On Fri, Aug 28 2015, Peter Chen wrote:
> The 'length' is the transfer length, not the packet size, so
> change the help text.
>
> Cc: Michal Nazarewicz
I sure touched weird things when I was young. :P Anyway:
Acked-by: Michal Nazarewicz
> Signed-off-by: Peter Chen
> ---
> tools/usb/testusb.
On Fri, Aug 28 2015, Peter Chen wrote:
> Since the host and gadget can't agree with transfer length before
> each transfer, but they agree with max packet size for each
> endpoint, we use max packet size to format data pattern.
>
> Signed-off-by: Peter Chen
Acked-by: Michal Nazarewicz
> ---
>
On Fri, Aug 28 2015, Peter Chen wrote:
> Using the same data format "buf[j] = (u8)(i + j)" among
> write, compare buf, and console output stage.
>
> Signed-off-by: Peter Chen
Acked-by: Michal Nazarewicz
> ---
> drivers/usb/misc/usbtest.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletio
On Fri, Aug 28 2015, Peter Chen wrote:
> The element of urbs array will be initialized at below code
> at once.
>
> for (i = 0; i < param->sglen; i++) {
> urbs[i] = iso_alloc_urb(udev, pipe, desc,
> param->length, offset);
>
> Signed-off-by:
On Fri, Aug 28 2015, Peter Chen wrote:
> Allocate the size of urb pointer array according to testusb's
> parameter sglen.
>
> Signed-off-by: Peter Chen
Acked-by: Michal Nazarewicz
I vaguely recall that LLVM fans got mad last time I used dynamically
sized local arrays though. Not sure though, I
>
> Since a_alt_hnp_support is obsolete in OTG 2.0, HNP capable host should send
> this set feature request only if the otg device is connecting to a non-HNP
> port
> and it's compliant with OTG 1.x revision. This is done by checking its otg
> descriptor length, OTG 2.0 uses usb_otg20_descripto
31.08.2015 10:32, Bjørn Mork пишет:
Eugene Shatokhin writes:
28.08.2015 11:55, Bjørn Mork пишет:
I guess you are right. At least I cannot prove that you are not :)
There is a bit too much complexity involved here for me...
:-)
Yes, it is quite complex.
I admit, it was easier for me to f
On 08/28/2015 10:29 AM, Peter Chen wrote:
..
> Would you supply below:
> 1. The u-boot.bin which you use to reproduce it
Hi Peter,
Thank you for looking into this issue.
I attached u-boot.imx to the ticket for you [1].
Due to the environment boot paths being tuned to my setup I can only
recomme
Since a_alt_hnp_support is obsolete in OTG 2.0, HNP capable host should
send this set feature request only if the otg device is connecting to a
non-HNP port and it's compliant with OTG 1.x revision. This is done by
checking its otg descriptor length, OTG 2.0 uses usb_otg20_descriptor
which has diff
Eugene Shatokhin writes:
> 28.08.2015 11:55, Bjørn Mork пишет:
>
>> I guess you are right. At least I cannot prove that you are not :)
>>
>> There is a bit too much complexity involved here for me...
>
> :-)
>
> Yes, it is quite complex.
>
> I admit, it was easier for me to find the races in usbn
52 matches
Mail list logo
