Re: Is this 32-bit NCM?

2014-11-27 Thread Bjørn Mork
Enrico Mioso writes: > I am sorry for the indecent capture - but I didn't manage to get a > better one till now. > We modified the driver: but I wanted to be sure ... is this 32-bit NCM? Yes, it looks OK to me. I have only looked at it manually, so I could have missed something. But the signa

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
So ... might be this is happening even in 16 bit mode? With our test device we are having no luck: the firmware now at least prints dsflowrpt messages, but we seem to not go farther than this. so - what should we try in your opinion? Go try with the 16 bit mode and try to fix the alignment issues

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
Ok - we can arrive to some ocnclusions regarding the E3272. First of all - the modem seems buggy enough to not be able to handle requests for different formats. You need to unplug and re-plug it, but this is onlyan impression and is reasonable. Then - the modem will accept to ndisdup the connect

Re: Is this 32-bit NCM?

2014-11-27 Thread Bjørn Mork
Enrico Mioso writes: > Ok - we can arrive to some ocnclusions regarding the E3272. > First of all - the modem seems buggy enough to not be able to handle requests > for different formats. You need to unplug and re-plug it, but this is onlyan > impression and is reasonable. > > Then - the modem

Re: [RFC] usb: gadget: libcomposite: provide usb_get_cdesc()

2014-11-27 Thread Andrzej Pietrasiewicz
Hi Sebastian, W dniu 25.11.2014 o 18:35, Sebastian Andrzej Siewior pisze: We have global descriptors. This is okay as long as we use them read-only. Writting the endpoint address is not *that* bad as long as two functions of the same kind are not used in parallel. Any suggestions, ideas?

Re: [PATCH v2] usb: core: buffer: smallest buffer should start at ARCH_DMA_MINALIGN

2014-11-27 Thread Sebastian Andrzej Siewior
On 11/27/2014 04:50 AM, Greg Kroah-Hartman wrote: >> @@ -171,8 +172,11 @@ struct usb_hcd { >> struct usb_hcd *shared_hcd; >> struct usb_hcd *primary_hcd; >> >> - >> -#define HCD_BUFFER_POOLS4 >> +#if ARCH_KMALLOC_MINALIGN <= 64 >> +#define HCD_BUFFER_POOLS

[PATCH] mfd: dln2: add suspend/resume functionality

2014-11-27 Thread Octavian Purdila
Without suspend/resume functionality in the USB driver the USB core will disconnect and reconnect the DLN2 port and because the GPIO framework does not yet support removal of an in-use controller a suspend/resume operation will result in a crash. This patch provides suspend, resume and reset_resum

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
On Thu, 27 Nov 2014, Alex Strizhevsky wrote: ==Date: Thu, 27 Nov 2014 13:36:37 ==From: Alex Strizhevsky ==To: Bjørn Mork , shaojunmidge@audiocodes.com, ==mingying@audiocodes.com ==Cc: Enrico Mioso , you...@gmail.com, ==linux-usb@vger.kernel.org, net...@vger.kernel.org, ==eli

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
By the chance - a cdc_ncm driver for 32-bit devices tthat might be buggy as hell and that works but only with my device (that works in both 16 and 32 bit mode) is: http://www.gstorm.eu/cdc_ncm.c On Thu, 27 Nov 2014, Alex Strizhevsky wrote: ==Date: Thu, 27 Nov 2014 13:36:37 ==From: Alex Strizh

[PATCH 2/4] xhci: clear extra bits from slot context when setting max exit latency

2014-11-27 Thread Mathias Nyman
If we need to change the max exit latency with a Evaluate Context command, we copy the old output slot context and use it as input context for the command. This also copies the dev_state bits which are supposed to be zero in the input slot context. Signed-off-by: Mathias Nyman --- drivers/usb/ho

[PATCH 0/4] xhci features for usb-next

2014-11-27 Thread Mathias Nyman
Hi Greg These xhci patches for v3.19 merge window are based on top of four xhci patches in your usb-linus tree. I'm not sure how you usually do it when features for usb-next depend on code only in usb-linus. Just pulling usb-linus to usb-next should work. The usb-linus patches these are done on t

[PATCH 1/4] xhci: cleanup finish_td function

2014-11-27 Thread Mathias Nyman
Remove unnecessary else after return, dropping extra indentation depth. No functional changes. Signed-off-by: Mathias Nyman --- drivers/usb/host/xhci-ring.c | 105 --- 1 file changed, 49 insertions(+), 56 deletions(-) diff --git a/drivers/usb/host/xhci-ri

[PATCH 4/4] usb: xhci: fix comment for PORT_DEV_REMOVE

2014-11-27 Thread Mathias Nyman
From: Lu Baolu According to xHCI specification, PORT_DEV_REMOVE(bit 30) in PORTSC true means "Device is non-removable". Reported-by: Juro Bystricky Signed-off-by: Lu Baolu Signed-off-by: Mathias Nyman --- drivers/usb/host/xhci.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --g

[PATCH 3/4] xhci: don't use the same variable for stopped and halted rings current TD

2014-11-27 Thread Mathias Nyman
Endpoints halted on errors, and endpoints stopped manually both used the same ep->stopped_td to store the halted or stopped td. this causes confusion and possible races. There is no longer a need to use the ep->stopped_td variable to store the halted TD. A halted endpoint is handled immediately an

Re: Suspected (out of tree) HCI issue

2014-11-27 Thread Alan Stern
On Thu, 27 Nov 2014, Vincent Pelletier wrote: > > If it does, it means there's a bug in the HCD: It isn't calling > > usb_hcd_link_urb_to_ep() properly. > > Indeed, no trace of this function being called. If the Synopsys driver hasn't been updated since before that function was added to the USB

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
What I suspect, is that all this mess started when Huawei introduce new firmware releases that changed something in the IPV6 support. Bjorn - do you remember when a guy called Thomas reported us a problem about an LTE huawei modem that wasn't working with huawei_cdc_ncm? And you then discovered t

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
To be clearer - then you fixed cdc_ncm magistrally I remember, adding also sysfs attrs then. But I was curious - so that we might understand if Thomas's problem was related to the firmware or what else. On Thu, 27 Nov 2014, Alex Strizhevsky wrote: ==Date: Thu, 27 Nov 2014 13:36:37 ==From: Alex

USB EHCI DVB bug

2014-11-27 Thread Joe Bryant
Hello - I've been advised to alert the group to this bug that seems to affect USB DVB devices in kernel 3.13 onwards. I would certainly appreciate any help in solving this problem. https://bugzilla.kernel.org/show_bug.cgi?id=72891 Thank you in advance - Joe Bryant -- To unsubscribe from this li

[PATCH] usb: musb: Fix a few off-by-one lengths

2014-11-27 Thread Rasmus Villemoes
!strncmp(buf, "force host", 9) is true if and only if buf starts with "force hos". This was obviously not what was intended. The same error exists for "force full-speed", "force high-speed" and "test packet". Using strstarts avoids the error-prone hardcoding of the prefix length. For consistency,

[PATCH] USB / PM: Drop CONFIG_PM_RUNTIME from the USB core

2014-11-27 Thread Rafael J. Wysocki
From: Rafael J. Wysocki After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so quite a few #ifdef blocks depending on CONFIG_PM_RUNTIME may now be changed to depend on CONFIG_PM (or even dropped in some cases). Replace CONFIG_PM_

Re: [PATCH] USB / PM: Drop CONFIG_PM_RUNTIME from the USB core

2014-11-27 Thread Rafael J. Wysocki
On Thursday, November 27, 2014 11:45:15 PM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is > selected) PM_RUNTIME is always set if PM is set, so quite a few > #ifdef blocks depending on CONFIG_PM_RUNTIME may now be chang

[Update][PATCH] USB / PM: Drop CONFIG_PM_RUNTIME from the USB core

2014-11-27 Thread Rafael J. Wysocki
From: Rafael J. Wysocki Subject: USB / PM: Drop CONFIG_PM_RUNTIME from the USB core After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so quite a few #ifdef blocks depending on CONFIG_PM_RUNTIME may now be changed to depend on CO

Re: [PATCH 2/2] usb: gadget: uvc: configfs support in uvc function

2014-11-27 Thread Laurent Pinchart
Hi Andrzej, Thank you for the patch. On Wednesday 24 September 2014 15:26:43 Andrzej Pietrasiewicz wrote: > Add support for using the uvc function as a component of USB gadgets > composed with configfs. > > Signed-off-by: Andrzej Pietrasiewicz > --- > Documentation/ABI/testing/configfs-usb-gad

Re: [PATCH V2 1/2] pinctrl: exynos: Add BUS1 pin controller for exynos7

2014-11-27 Thread Vivek Gautam
Hi Alim, On Wed, Nov 26, 2014 at 7:03 PM, Alim Akhtar wrote: > Hi Vivek, > > On Mon, Nov 24, 2014 at 6:32 PM, Vivek Gautam > wrote: >> USB and Power regulator on Exynos7 require gpios available >> in BUS1 pin controller block. >> So adding the BUS1 pinctrl support. >> >> Signed-off-by: Naveen

Re: [PATCH V2 1/2] pinctrl: exynos: Add BUS1 pin controller for exynos7

2014-11-27 Thread Vivek Gautam
Hi Linus, On Fri, Nov 28, 2014 at 9:05 AM, Vivek Gautam wrote: > Hi Alim, > > > On Wed, Nov 26, 2014 at 7:03 PM, Alim Akhtar wrote: >> Hi Vivek, >> >> On Mon, Nov 24, 2014 at 6:32 PM, Vivek Gautam >> wrote: >>> USB and Power regulator on Exynos7 require gpios available >>> in BUS1 pin control

Re: [PATCH V2 2/2] arm64: exynos: Add bus1 pinctrl node on exynos7

2014-11-27 Thread Vivek Gautam
Hi Kukjin, On Wed, Nov 26, 2014 at 6:59 PM, Alim Akhtar wrote: > Hi Vivek, > > On Mon, Nov 24, 2014 at 6:36 PM, Vivek Gautam > wrote: >> BUS1 pinctrl provides gpios for usb and power regulator >> available on exynos7-espresso board. So add relevant device >> node for pinctrl-bus1. >> >> Signed

[PATCH V2] usb: {ohci,ehci}-platform: Use new OF big-endian helper function

2014-11-27 Thread Kevin Cernekee
This handles the existing "big-endian" case, and in addition, it also does the right thing when "native-endian" is specified. Signed-off-by: Kevin Cernekee Acked-by: Alan Stern --- Documentation/devicetree/bindings/usb/usb-ehci.txt | 2 ++ Documentation/devicetree/bindings/usb/usb-ohci.txt | 2

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
Hello to everyone. Can you guys try to compare what happens withe standard, and 32-bit version of the driver, with the E3276, so that we see what happens and what are the differences? And it would be very nice if you look what happens with the standard 16-bit driver to confirm what Bjorn suspect

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
And... a precisation: when I talk about the 32-bit mode driver, I am not referring to the windows one, but to the Linux one I and Alessio "implemented", modifying the standard cdc_ncm.c driver. This version of the driver should be available here: On Thu, 27 Nov 2014, Alex Strizhevsky wrote: htt

Re: Is this 32-bit NCM?

2014-11-27 Thread Enrico Mioso
Ok. On Fri, 28 Nov 2014, Kevin Zhu wrote: ==Date: Fri, 28 Nov 2014 07:24:49 ==From: Kevin Zhu ==To: Alex Strizhevsky , Bjørn Mork , ==Midge Shaojun Tan ==Cc: Enrico Mioso , "you...@gmail.com" , =="linux-usb@vger.kernel.org" , =="net...@vger.kernel.org" , ==Eli Britstein ==Subj