At Fri, 12 Oct 2012 17:42:19 +0200,
Matthieu CASTET wrote:
>
> Hi,
>
>
> Takashi Iwai a écrit :
> > [Added Daniel and Clemens in the loop]
> >
> >
> > I don't think this is needed.
> >
> > So... the below is a quick hack I did without testing at all.
> > Hopefully this can give some advance.
The handling of large output bulk transfers is broken; the same user
page is read over and over again. Fixed with this patch.
Cc: sta...@kernel.org
Acked-by: Peter Stuge
Acked-by: Hans de Goede
Acked-by: Alan Stern
Signed-off-by: Henrik Rydberg
---
Hi Greg,
Here is the formal and third versio
Changes from v1:
- Reverted back the code movements in core.c and also reverted
dwc3_core_reset()
- Removed the pdata dependency for phy init and exit from dwc3-exynos.c
Based on 'usb-next' of greg's tree.
Tested USB detection and enumeration across multiple cycles of
suspend/resume using 2.0
Adding the suspend and resume funtionality to DWC3 core.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/dwc3/core.c | 54 +++
1 files changed, 54 insertions(+), 0 deletions(-)
diff --git a/drivers/u
Adding the suspend and resume functionality for the XHCI driver
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/host/xhci-plat.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/drivers/usb
Adding the suspend and resume functionality to exynos dwc3 driver
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/dwc3/dwc3-exynos.c | 39 +++
1 files changed, 39 insertions(+), 0 deletions(-)
diff --git a/d
This patchset adds support to parse the dwc3-exynos device
using device tree. It also removes the platform data and phy_init()
or phy_exit() calls which is no longer needed.
Based and tested on 'usb-next' branch of greg's tree.
Vivek Gautam (2):
USB: dwc3-exynos: Add support for device tree
U
This patch adds support to parse probe data for
dwc3 driver for exynos using device tree
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3-exynos.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-exynos.c b/drivers/usb/dwc3
We are removing plat data which was used till now to init and
exit phy. We no longer need this since dwc3-core takes care of
initializing and shutting-down the phy using usb_phy_init()
and usb_phy_shutdown().
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3-exynos.c | 16
We do usb_phy_init() while doing core_init() in probe,
so adding usb_phy_shutdown() when we do core_exit()
while removing the device.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/core.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/driv
Hi,
On Saturday 13 October 2012 07:17 PM, Vivek Gautam wrote:
This patch adds support to parse probe data for
dwc3 driver for exynos using device tree
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3-exynos.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions
I'm trying to apply:
commit b63f4053cc8aa22a98e3f9a97845afe6c15d0a0d
Author: Elric Fu
Date: Wed Jun 27 16:55:43 2012 +0800
xHCI: handle command after aborting the command ring
to 3.2.y. A simple cherry-pick doesn't compile because the inc_deq()
function requires a 3rd argument ('consumer
On Thu, Oct 11, 2012 at 04:57:11AM +0900, Greg KH wrote:
> On Wed, Oct 10, 2012 at 03:05:09PM +0200, Jarkko Huijts wrote:
> > On Tue, 2012-10-09 at 07:59 -0700, Greg KH wrote:
> > > On Tue, Oct 09, 2012 at 12:21:56PM +0200, Jarkko Huijts wrote:
> > > > I have e-mailed FTDI's support to ask whether
Export generic chars_in_buffer implementation so it can be used in
subdrivers in combination with checks of any hardware buffers.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/generic.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/generic.c b/drivers/usb/serial/gen
These patches clean up tiocmget, fix leaks of USB internal error codes to
userspace from the tiocmget/set, and implements checking of hardware buffers in
chars_in_buffer by refactoring the retrieval of modem-control status.
Johan Hovold (5):
USB: ftdi_sio: fix tiocmget indentation
USB: ftdi_si
Refactor modem-control status retrieval.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/ftdi_sio.c | 38 +++---
1 file changed, 35 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index 6d1a755..3312d7a
Make sure hardware buffers are empty before returning 0.
This fixes a problem reported by Jarkko Huijts who noted that port close
returns before all data has been transferred.
Based on a solution proposed by Jarkko Huijts.
Reported-by: Jarkko Huijts
Signed-off-by: Johan Hovold
---
drivers/usb
Align the modem-control status operands as was originally indented.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/ftdi_sio.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index f906b3a..5fc2f1f 10064
Make sure we do not return USB-internal error codes to userspace.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/ftdi_sio.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index 5fc2f1f..6d1a755 100644
---
On Fri, 12 Oct 2012, Yuliya T wrote:
> Hi Alan,
>
> Thank you for the suggestion. We independently ended up with the same
> workaround, but still weren't happy with it. The problem is we don't
> want to relinquish access to the device, but to do set-interface, you
> have to do release interface
On Sat, Oct 13, 2012 at 01:20:43PM +0200, Constantine Shulyupin wrote:
> Hi,
>
> I wonder what is the current status of Android USB, ccg drivers?
> Is it need only to change sysfs interface to configfs?
> Are there further tasks?
Isn't that a big enough task to work on at the moment? :)
greg k-
Am 13.10.2012 05:01, schrieb Ming Lei:
> On Sat, Oct 13, 2012 at 6:11 AM, Tilman Schmidt wrote:
>>
>> There are two cases I have to worry about:
>> (1) a reset triggered by int_in_work()
>> (2) a reset triggered by some other source external to the driver
>>
>> In case (1) the current design will
Hi Ben,
Ben Hutchings wrote:
> I'm trying to apply:
>
> commit b63f4053cc8aa22a98e3f9a97845afe6c15d0a0d
[...]
> to 3.2.y. A simple cherry-pick doesn't compile because the inc_deq()
> function requires a 3rd argument ('consumer')
In v3.4-rc1~184^2~21^2~9 (xHCI: store ring's type, 2012-03-05)
con
On Tue, Oct 09, 2012 at 02:30:48PM +0100, David Howells wrote:
> Can you merge the following branch into the usb tree please.
>
> This is to complete part of the Userspace API (UAPI) disintegration for which
> the preparatory patches were pulled recently. After these patches, userspace
> headers
From: Nicolas Boullis
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
Signed-off-by: Nicolas Boullis
---
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 981f213..194fa8b 100644
--- a/drivers/usb/class/cdc-
Device-tree probed devices don't get a dev.dma_mask set. This patch
sets a default 32bit mask on platforms using devicetree.
Without this patch, arch-vt8500 cannot detect uhci attached devices.
Signed-off-by: Tony Prisk
---
drivers/usb/host/uhci-platform.c |9 +
1 file changed, 9 in
Greg KH,
Can we get these in before -rc1 as most arch-vt8500 users rely
on USB to boot, and with both EHCI & UHCI missing dma_masks, neither
works.
Regards
Tony P
v2: corrected copy/paste mistake in uhci-platform.c
Tony Prisk (2):
usb: Missing dma_mask in uhci-platform.c when probed from devi
Device-tree probed devices don't get a dev.dma_mask set. This patch
sets a default 32bit mask on arch-vt8500 when using devicetree.
Without this patch, arch-vt8500 cannot detect ehci attached devices.
Signed-off-by: Tony Prisk
---
drivers/usb/host/ehci-vt8500.c | 10 ++
1 file changed
28 matches
Mail list logo
