On Fri, Oct 25, 2013 at 09:07:12PM +0400, Valentine Barshak wrote:
> Add missing USB UGCTRL2 register offset.
>
> Signed-off-by: Valentine Barshak
This seems reasonable to me.
Acked-by: Simon Horman
Felipe, please consider applying this change.
> ---
> drivers/usb/phy/phy-rcar-gen2-usb.c |
On Thu, Oct 10, 2013 at 02:14:47AM +0400, Valentine Barshak wrote:
> This adds USBHS PHY and registers USBHS device if the driver is enabled.
>
> Signed-off-by: Valentine Barshak
> Acked-by: Kuninori Morimoto
Thanks,
I notice that Felipe Balbi's has merged the first patch of this series and
th
On Thu, Oct 10, 2013 at 02:14:46AM +0400, Valentine Barshak wrote:
> This adds USBHS clock support.
>
> Signed-off-by: Valentine Barshak
> Acked-by: Kuninori Morimoto
> ---
> arch/arm/mach-shmobile/clock-r8a7790.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/mach-shmob
From: Hayes Wang
Date: Mon, 28 Oct 2013 19:58:09 +0800
> These could fix some driver issues.
>
> Hayes Wang (5):
> net/usb/r8152: fix tx/rx memory overflow
> net/usb/r8152: make sure the tx checksum setting is correct
> net/usb/r8152: modify the tx flow
> net/usb/r8152: fix incorrect typ
From: "Du, Changbin"
In cdc_ncm_bind() function, it call cdc_ncm_bind_common() to setup usb.
But cdc_ncm_bind_common() may meet error and cause usbnet_disconnect()
be called which calls free_netdev(net). Thus usbnet structure(alloced
with net_device structure) will be freed,too.
So we cannot call
On Mon, Oct 28, 2013 at 10:37:52AM -0400, Alan Stern wrote:
> On Mon, 28 Oct 2013, Peter Chen wrote:
>
> > > > Just like you said:
> > > > > The physical wakeup setting is controlled by both the controller
> > > > > driver
> > > > > and the platform driver.
> > > > But currently, it is controlled
On Sat, Oct 26, 2013 at 7:40 AM, Alan Stern wrote:
> On Fri, 25 Oct 2013, Dan Williams wrote:
>> > This patch set makes a large number of significant changes to important
>> > and subtle aspects of the USB stack. It would be a lot easier to
>> > discuss in pieces; I can't possibly review the whol
Hi,
when tried to activate the USB-OTG or USBH2 with the FDT the system oops
[1.034403] ehci-mxc: Freescale On-Chip EHCI Host driver
[1.041158] Unable to handle kernel NULL pointer dereference at virtual
address
[1.049406] pgd = c0004000
[1.052219] [] *pgd=000
DWC3 requires buffer size to be aligned to maxpacketsize of an out
endpoint. ffs_epfile_io() needs to pad epout buffer to match above
condition if DWC3 controller is used.
This patch solves an specific situation but a more generic solution
should be found.
Signed-off-by: David Cohen
---
drivers
Hi,
These patches are a proposal to workaround f_fs when using DWC3 controller.
Since DWC3 requires epout buffer size to be aligned to maxpacketsize, f_fs
needs to pad buffer size to match the above case.
This change is necessary to make Android's adbd service to work with f_fs
instead of out-of-
gadget_is_dwc3() is necessary to check whether we are running on
Desineware USB3 DRD controller.
This macro was previously removed by commit
ed9cbda63d45638b69ce62412e3a3c7b00644835 due to it wasn't needed
anymore. We're adding it again as things have changed.
Signed-off-by: David Cohen
---
dri
Hello,
This patch series, based on v3.12-rc7, prepares various Renesas SH-Mobile,
R-Mobile and R-Car drivers for migration to CCF by adding clock prepare and
unprepare support.
The patches are pretty straightforward. Most of the drivers called
clk_enable and clk_disable in sleepable context, I've
Turn clk_enable() and clk_disable() calls into clk_prepare_enable() and
clk_disable_unprepare() to get ready for the migration to the common
clock framework.
Cc: Greg Kroah-Hartman
Cc: Yoshihiro Shimoda
Cc: linux-usb@vger.kernel.org
Signed-off-by: Laurent Pinchart
---
drivers/usb/host/r8a66597
Turn clk_enable() and clk_disable() calls into clk_prepare_enable() and
clk_disable_unprepare() to get ready for the migration to the common
clock framework.
Cc: Felipe Balbi
Cc: linux-usb@vger.kernel.org
Signed-off-by: Laurent Pinchart
---
drivers/usb/gadget/r8a66597-udc.c | 6 +++---
1 file c
Some MBIM devices send back-to-back USB_CDC_NOTIFY_RESPONSE_AVAILABLE
notifications
when sending a message over multiple fragments or when there are unsolicited
messages available.
Count up the number of USB_CDC_NOTIFY_RESPONSE_AVAILABLE notifications received
and decrement the count and submit t
https://bugzilla.kernel.org/show_bug.cgi?id=63961
Kernel version 3.10.15
[1774469.764676] usb 2-1: new SuperSpeed USB device number 73 using xhci_hcd
[1774469.777435] usb 2-1: Parent hub missing LPM exit latency info. Power
management will be impacted.
[1774469.779805] usb 2-1: New USB device f
Hi
I tried resetting usb device when it gets ETIMEDOUT during get
descriptor. On second retry, I don't see timeout. Please see this
patch:
Index: linux-3.4/drivers/usb/core/hub.c
===
--- linux-3.4.orig/drivers/usb/core/hub.c
+++ linu
Hi Kamil,
On Monday 28 of October 2013 14:52:19 Kamil Debski wrote:
> Hi Kishon,
>
> Thank you for your review! I will answer your comments below.
[snip]
> > > +
> > > + switch (drv->cfg->cpu) {
> > > + case TYPE_EXYNOS4210:
> >
> > > + case TYPE_EXYNOS4212:
> > Lets not add such cpu checks insi
Mika Westerberg has reported that the fixed+improved divisor based baud rate
encoding method doesn't work anymore with his HXD device.
So until we've found out what's going on, reintroduce the old encoding algorithm
and use it for this and all newer chips for baud rates > 115200 baud.
Also switch
> > We are seeing complete lockups of the transmit side when using
> > the smsc95xx driver connected to a USB3 port on an i7 (Ivybridge) cpu.
> > These errors are very intermittent - less than once a day, and
> > it isn't actually clear that they are related to traffic load.
...
> I would suggest y
Am 28.10.2013 09:27, schrieb Mika Westerberg:
> On Fri, Oct 25, 2013 at 03:43:03PM +0200, Frank Schäfer wrote:
>> Am 25.10.2013 15:17, schrieb Mika Westerberg:
>>> On Fri, Oct 25, 2013 at 03:01:37PM +0200, Frank Schäfer wrote:
> Tried few other baudrates > 115200 and they don't work either.
>>>
On Mon, 28 Oct 2013, Huang Rui wrote:
> Hi all,
>
> The following patches implement Binary Device Object Store (BOS) descriptor
> set tests in section 9.6.2 of USB 3.0 SPEC. At current usbtest module, it
> only supports USB 2.0 chapter 9 tests, so this updates extend the testing
> scope to cover
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
Container ID descriptor is one of the generic device-level capbility
descriptors which added in section 9.6.2.3 of USB 3.0 spec.
This patch adds to support getting Container ID descriptor test scenario
for USB 3.0.
S
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times. This patch adds to support getting bos descriptor test scenario for
USB 3.0.
Signed-off-by: Huang Rui
---
drivers/usb/misc/usbtest.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/usb/misc
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
USB2.0 Extension descriptor is one of the generic device-level capbility
descriptors which added in section 9.6.2.1 of USB 3.0 spec.
This patch adds to support getting usb2.0 extension descriptor test
scenario for USB
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
SuperSpeed USB Device Capability descriptor is one of the generic
device-level capbility descriptors which added in section 9.6.2.2 of USB
3.0 spec.
This patch adds to support getting SuperSpeed USB Device Capability
Hi all,
The following patches implement Binary Device Object Store (BOS) descriptor
set tests in section 9.6.2 of USB 3.0 SPEC. At current usbtest module, it
only supports USB 2.0 chapter 9 tests, so this updates extend the testing
scope to cover the USB 3.0 new descriptors.
Changes from v1 -> v2
Hi Gustavo,
Patch has been applied to bluetooth.git. Thanks.
Hmm, I'm not seeing this in 3.12 yet, not only should this be added
to 3.12 asap, it should also really get added to 3.11.x soon.
The regression this patch fixes is breaking btusb for lots of users, see:
https://bugs.launchpad.net/u
Be aware that the mailing list doesn't like HTML. Plain-text only,
please.
On Mon, 28 Oct 2013, zouid abdelhamid wrote:
> Hi folks,
>
>
>
> I am
> testing a USB MSC, device mode, using USBCV2.0 .
>
> The device
> is an ARM based platform with a USB DRD that is running 3.4 kernel, the USB
>
On Mon, Oct 28, 2013 at 10:44:19AM -0400, Alan Stern wrote:
> On Mon, 28 Oct 2013, Huang Rui wrote:
>
> > In Test 9 of usbtest module, it is used for performing chapter 9 tests N
> > times.
> >
> > USB2.0 Extension descriptor is one of the generic device-level capbility
> > descriptors which adde
On Mon, 28 Oct 2013, Huang Rui wrote:
> In Test 9 of usbtest module, it is used for performing chapter 9 tests N
> times.
>
> USB2.0 Extension descriptor is one of the generic device-level capbility
> descriptors which added in section 9.6.2.1 of USB 3.0 spec.
>
> This patch adds to support gett
Hi Kishon,
On Fri, Oct 25, 2013 at 9:13 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
>> Add support for Exynos 5250. This is work-in-progress commit. Not
>> for merging.
>>
>> Signed-off-by: Kamil Debski
>> Signed-off-by: Kyungmin Park
>>
On Mon, 28 Oct 2013, Peter Chen wrote:
> > > Just like you said:
> > > > The physical wakeup setting is controlled by both the controller driver
> > > > and the platform driver.
> > > But currently, it is controlled (or affected) by hcd layer.
> >
> > It is _initialized_ by the HCD layer. The pl
Hi Kamil,
On Mon, Oct 28, 2013 at 7:23 PM, Kamil Debski wrote:
> Hi Vivek,
>
>> From: Vivek Gautam [mailto:gautamvivek1...@gmail.com]
>> Sent: Saturday, October 26, 2013 11:41 AM
>>
>> Hi Kamil,
>>
>>
>> On Fri, Oct 25, 2013 at 7:45 PM, Kamil Debski
>> wrote:
>> > Change the phy provider used f
Hi Vivek,
> From: Vivek Gautam [mailto:gautamvivek1...@gmail.com]
> Sent: Saturday, October 26, 2013 11:41 AM
>
> Hi Kamil,
>
>
> On Fri, Oct 25, 2013 at 7:45 PM, Kamil Debski
> wrote:
> > Change the phy provider used from the old usb phy specific to a new
> > one using the generic phy framewo
Hi Kishon,
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Friday, October 25, 2013 5:44 PM
>
> Hi,
>
> On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> > Add support for Exynos 5250. This is work-in-progress commit. Not for
> > merging.
> >
> > Signed-off-by: Kamil Debski
Hi Kumar Gala,
> From: Kumar Gala [mailto:ga...@codeaurora.org]
> Sent: Friday, October 25, 2013 11:36 PM
>
> On Oct 25, 2013, at 9:15 AM, Kamil Debski wrote:
>
> > Add a new driver for the Exynos USB PHY. The new driver uses the
> > generic PHY framework. The driver includes support for the Exy
Hi Jingoo,
> From: Jingoo Han [mailto:jg1@samsung.com]
> Sent: Saturday, October 26, 2013 3:27 AM
>
> On Friday, October 25, 2013 11:15 PM, Kamil Debski wrote:
> >
> > Change the phy provider used from the old usb phy specific to a new
> > one using the generic phy framework.
> >
> > Signed-o
Hi Kishon,
Thank you for your review! I will answer your comments below.
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Friday, October 25, 2013 5:40 PM
>
> Hi,
>
> On Friday 25 October 2013 07:45 PM, Kamil Debski wrote:
> > Add a new driver for the Exynos USB PHY. The new driver
On 2013-10-01 16:19, Felipe Balbi wrote:
+static void gr_finish_request(struct gr_ep *ep, struct gr_request *req,
+ int status)
+{
+ struct gr_udc *dev;
+
+ list_del_init(&req->queue);
+
+ if (likely(req->req.status == -EINPROGRESS))
+ r
On 2013-10-28 12:29, Robert Hodaszi wrote:
On 2013-10-28 10:30, Robert Hodaszi wrote:
On 2013-10-26 19:44, Greg KH wrote:
On Fri, Oct 25, 2013 at 05:14:58PM +0200, Robert Hodaszi wrote:
Hi,
I'm using a Telit modem with an i.mx28 processor. I'm currently running
a 2.6.35 kernel on that (I kno
Let rtl8152_start_xmit() to queue packet only, and tx_bottom() would
send all of the packets. This simplify the code and make sure all the
packet would be sent by the original order.
Support stopping and waking tx queue. The maximum tx queue length
is 60.
Signed-off-by: Hayes Wang
---
drivers/n
Clear the checksum setting before checking the necessary of hardware
checksum.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 5dbfe50..815d890 100644
--- a/drivers/net/usb/r8152.c
+
The tx/rx would access the memory which is out of the desired range.
Modify the method of checking the end of the memory to avoid it.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/drivers
These could fix some driver issues.
Hayes Wang (5):
net/usb/r8152: fix tx/rx memory overflow
net/usb/r8152: make sure the tx checksum setting is correct
net/usb/r8152: modify the tx flow
net/usb/r8152: fix incorrect type in assignment
net/usb/r8152: code adjust
drivers/net/usb/r8152.c
-Remove rtl8152_get_stats()
-Fix the wrong name
-Something else
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 46 +-
1 file changed, 21 insertions(+), 25 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 90
Correct some declaration.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index a711025..90bc105 100644
--- a/drivers/net/usb/r8152.c
+++ b/drivers/net/u
On 2013-10-28 10:30, Robert Hodaszi wrote:
On 2013-10-26 19:44, Greg KH wrote:
On Fri, Oct 25, 2013 at 05:14:58PM +0200, Robert Hodaszi wrote:
Hi,
I'm using a Telit modem with an i.mx28 processor. I'm currently running
a 2.6.35 kernel on that (I know, it's pretty old, and on an other
thread,
On 10/18/2013 11:03 AM, Daniel Mack wrote:
> Hi Sebastian,
>
> On 10/17/2013 04:36 PM, Sebastian Andrzej Siewior wrote:
>> On 10/17/2013 04:23 PM, Daniel Mack wrote:
Daniel, could please look if this solves your suspend / resume warnings?
>
> Looking very good :)
>
>> dma: cppi41: add suppo
On 10/18/2013 11:59 AM, Sebastian Andrzej Siewior wrote:
> On 10/18/2013 11:39 AM, Daniel Mack wrote:
>> v3 of my musb_dsps suspend patches.
>>
>> With these patches applied, I can successfully bring an AM335x board
>> to suspend with a USB media connected, and access it again after
>> resume.
>>
>
Dear Hector Palacios,
> Dear Peter,
>
> On 10/25/2013 08:02 AM, Peter Chen wrote:
> > According to Freescale imx28 Errata, "ENGR119653 USB: ARM to USB
> > register error issue", All USB register write operations must
> > use the ARM SWP instruction. So, we implement special hw_write
> > and hw_te
Dear Peter,
On 10/25/2013 08:02 AM, Peter Chen wrote:
According to Freescale imx28 Errata, "ENGR119653 USB: ARM to USB
register error issue", All USB register write operations must
use the ARM SWP instruction. So, we implement special hw_write
and hw_test_and_clear for imx28.
Discussion for it
On 2013-10-26 19:44, Greg KH wrote:
On Fri, Oct 25, 2013 at 05:14:58PM +0200, Robert Hodaszi wrote:
Hi,
I'm using a Telit modem with an i.mx28 processor. I'm currently running
a 2.6.35 kernel on that (I know, it's pretty old, and on an other
thread, I'm working on the v3 also). The modem is us
Hi Shawn,
> On Sun, Oct 27, 2013 at 05:25:36PM +0100, Marek Vasut wrote:
> > > +static const struct of_device_id ci_hdrc_imx_dt_ids[] = {
> > > + { .compatible = "fsl,imx28-usb", .data = &imx28_usb_data},
> > > + { .compatible = "fsl,imx27-usb", .data = &imx27_usb_data},
> >
> > Just a nit-pick,
Thomas Schäfer writes:
> Hi Bjørn,
>
>
> I tested your patch with the K5150 in mbim-mode
>
> with ipv6 only - ok.
> with Ipv4 only - ok.
Yes, I was pretty sure of that since I am able to test IPv4 myself and
the IPv6 solution is based on simply turning of the IFF_NOARP flag.
But I realized tha
On Fri, Oct 25, 2013 at 02:02:19PM +0800, Peter Chen wrote:
> According to Freescale imx28 Errata, "ENGR119653 USB: ARM to USB
> register error issue", All USB register write operations must
> use the ARM SWP instruction. So, we implement a special ehci_write
> for imx28.
>
> Discussion for it at
On Tue, Oct 22, 2013 at 01:58:34PM +0800, Peter Chen wrote:
> Hi Felipe,
Hi Felipe, would you please give any comments for this patchset?
My another patchset chipidea's PM support also depends on this.
Thanks.
Peter
>
>The serial adds power management support for MXS PHY, it includes:
>
>
On Fri, Oct 25, 2013 at 03:43:03PM +0200, Frank Schäfer wrote:
> Am 25.10.2013 15:17, schrieb Mika Westerberg:
> > On Fri, Oct 25, 2013 at 03:01:37PM +0200, Frank Schäfer wrote:
> >>> Tried few other baudrates > 115200 and they don't work either.
> >> Urgh... has this device ever been working at ba
58 matches
Mail list logo