* Robert ABEL ra...@cit-ec.uni-bielefeld.de [150227 08:00]:
These are the changes I proposed in these patch series: [1], [2], [3], [4]
rebased to 3.19 as well as new changes for little bugs I noticed while
preparing this patch series as well as changes introduced via comments.
1. DEBUG was
* Robert Abel ra...@cit-ec.uni-bielefeld.de [150303 05:03]:
Hi Roger,
On Tue, Mar 3, 2015 at 1:55 PM, Roger Quadros rog...@ti.com wrote:
I'm OK with this version.
Tony, after you ACK these I will queue them for v4.1.
Please use v4 of my patches. The DTS output has been changed and the
On 03/05/2015 09:17 PM, Kenneth Johansson wrote:
On 2015-03-05 03:23, Lu, Baolu wrote:
Hi Kenneth Johansson,
Did you still get the bandwidth error when testing it with longer time?
no I have not seen it on any 3.19 kernel I have used so far. But It
could take a week to see it before so
Instead of iterate to find usb_udc according to usb_gadget, this
way is easier.
Alan Stern suggests this way too:
http://marc.info/?l=linux-usbm=142168496528894w=2
Acked-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Peter Chen peter.c...@freescale.com
---
It can move all pullup/pulldown operation control to udc-core
through usb_gadget_connect/usb_gadget_disconnect according to
vbus status.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/udc.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
This commit updates udc core vbus status, and try to connect
or disconnect gadget.
Signed-off-by: Peter Chen peter.c...@freescale.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/gadget/udc/udc-core.c | 34 +-
include/linux/usb/gadget.h|
Changes for v2:
- Keep the placement of struct usb_udc definition unchanging
- Add Alan's Ack for patch 1/3
Hi Felipe Alan:
It is the follow-up:
http://marc.info/?l=linux-usbm=142301743123434w=2
In the first patch, I follow Alan's suggestion that store usb_udc
pointer in struct usb_gadget, it
On Wed, 2015-03-04 at 22:00 -0500, Rick Farina wrote:
On 03/04/15 13:01, Greg KH wrote:
And again, a kernel patch is the real way to fix it for everyone.
Okay, got a lot of things figured out and have everything working now.
Glad I spent the extra time because I found some neat things on
Hi Greg,
Here's my first set of fixes for 4.0. All have been in linux-next for a while
now.
Please pull.
Thanks,
Johan
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
On 04.03.2015 15:27, Alistair Grant wrote:
Hi Mathias,
On Tue, Mar 3, 2015 at 8:40 PM, Alistair Grant akgrant0...@gmail.com wrote:
Hi Mathias,
On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman
mathias.ny...@linux.intel.com wrote:
On 28.02.2015 09:16, Alistair Grant wrote:
...
* 3.19.0
On Thu, 5 Mar 2015, Peter Chen wrote:
Instead of iterate to find usb_udc according to usb_gadget, this
way is easier.
Alan Stern suggests this way too:
http://marc.info/?l=linux-usbm=142168496528894w=2
Signed-off-by: Peter Chen peter.c...@freescale.com
Pretty much okay, but ...
---
On Thu, Mar 05, 2015 at 02:47:44PM +0100, Johan Hovold wrote:
Hi Greg,
Here's my first set of fixes for 4.0. All have been in linux-next for a while
now.
Please pull.
Thanks,
Johan
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1
Hi Mathias,
On Thu, Mar 5, 2015 at 4:25 PM, Mathias Nyman
mathias.ny...@linux.intel.com wrote:
On 04.03.2015 15:27, Alistair Grant wrote:
On Tue, Mar 3, 2015 at 8:40 PM, Alistair Grant akgrant0...@gmail.com wrote:
On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman
mathias.ny...@linux.intel.com
The IRQF_DISABLED is a NOOP and has been scheduled for removal since
Linux v2.6.36 by commit 6932bf37bed4 (genirq: Remove IRQF_DISABLED from
core code).
According to commit e58aa3d2d0cc (genirq: Run irq handlers with
interrupts disabled) running IRQ handlers with interrupts enabled can
cause
This commit updates udc core vbus status, and try to connect
or disconnect gadget.
Signed-off-by: Peter Chen peter.c...@freescale.com
Acked-by: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/gadget/udc/udc-core.c | 31 ++-
include/linux/usb/gadget.h| 7
Hi Felipe Alan:
It is the follow-up:
http://marc.info/?l=linux-usbm=142301743123434w=2
In the first patch, I follow Alan's suggestion that store usb_udc
pointer in struct usb_gadget, it will help to find usb_udc according
to usb_gadget easlier (Using iterates usb_udc list way will meet lock
Instead of iterate to find usb_udc according to usb_gadget, this
way is easier.
Alan Stern suggests this way too:
http://marc.info/?l=linux-usbm=142168496528894w=2
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/udc-core.c | 51
It can move all pullup/pulldown operation control to udc-core
through usb_gadget_connect/usb_gadget_disconnect according to
vbus status.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/udc.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
On Wed, Feb 25, 2015 at 03:40:31PM -0800, Bjorn Andersson wrote:
Any comments on this?
I'm going to propose a patch to the mmc framework calling this api, so
it would be good to know before I add another consumer of the api.
Please don't send content free nags. They just add to the volume
On 05/03/15 10:49, Laurent Pinchart wrote:
Hi Sudeep,
Thank you for the patch.
On Wednesday 04 March 2015 17:07:57 Sudeep Holla wrote:
Use spin_{un,}lock_irq{save,restore} in isp1760_udc_{start,stop} to
prevent following potentially deadlock scenario between
isp1760_udc_{start,stop} and
Hi Sudeep,
On Wednesday 04 March 2015 17:04:43 Sudeep Holla wrote:
On 04/03/15 16:11, Laurent Pinchart wrote:
Hi Sudeep,
On Wednesday 04 March 2015 15:56:12 Sudeep Holla wrote:
[...]
Also I don't see any message on the host side. Let me know if there's
something wrong in my config
Hi Sudeep,
Thank you for the patch.
On Wednesday 04 March 2015 17:07:57 Sudeep Holla wrote:
Use spin_{un,}lock_irq{save,restore} in isp1760_udc_{start,stop} to
prevent following potentially deadlock scenario between
isp1760_udc_{start,stop} and isp1760_udc_irq :
On 03/04/2015 04:39 AM, Johan Hovold wrote:
Remove incorrect and redundant wait_until_sent operation, which waits
for the driver buffer rather than any hardware buffers to drain,
something which is already taken care of by the tty layer (and
chars_in_buffer).
Reviewed-by: Peter Hurley
On 03/04/2015 04:39 AM, Johan Hovold wrote:
Fix overflow bug in tty_wait_until_sent on 64-bit machines, where an
infinite timeout (0) would be passed to the underlying tty-driver's
wait_until_sent-operation as a negative timeout (-1), causing it to
return immediately.
Wow, that is a nasty
The IRQF_DISABLED is a NOOP and has been scheduled for removal since
Linux v2.6.36 by commit 6932bf37bed4 (genirq: Remove IRQF_DISABLED from
core code).
According to commit e58aa3d2d0cc (genirq: Run irq handlers with
interrupts disabled) running IRQ handlers with interrupts enabled can
cause
On 03/04/2015 04:39 AM, Johan Hovold wrote:
Currently tty_wait_until_sent may take up to twice as long as the
requested timeout while waiting for driver and hardware buffers to
drain.
Fix this by taking the remaining number of jiffies after waiting for
driver buffers to drain into account
The usb core automatically sets the status to -EREMOTEIO when giving back the
URB to the driver if the transfer was short, and URB_SHORT_NOT_OK was set in the
transfer_flags and the status is equal to 0 (see __usb_hcd_giveback_urb()).
So, avoid the redundant checks in the xhci logic; instead the
On Thu, Mar 05, 2015 at 01:59:39PM +0100, Valentin Rothberg wrote:
diff --git a/drivers/mtd/nand/hisi504_nand.c b/drivers/mtd/nand/hisi504_nand.c
index 289ad3ac3e80..7f9f9c827c1d 100644
--- a/drivers/mtd/nand/hisi504_nand.c
+++ b/drivers/mtd/nand/hisi504_nand.c
@@ -758,8 +758,7 @@ static int
On 03/05/2015 01:59 PM, Valentin Rothberg wrote:
The IRQF_DISABLED is a NOOP and has been scheduled for removal since
Linux v2.6.36 by commit 6932bf37bed4 (genirq: Remove IRQF_DISABLED from
core code).
According to commit e58aa3d2d0cc (genirq: Run irq handlers with
interrupts disabled)
On Thu, Mar 5, 2015 at 2:08 PM, Dan Carpenter dan.carpen...@oracle.com wrote:
On Thu, Mar 05, 2015 at 01:59:39PM +0100, Valentin Rothberg wrote:
diff --git a/drivers/mtd/nand/hisi504_nand.c
b/drivers/mtd/nand/hisi504_nand.c
index 289ad3ac3e80..7f9f9c827c1d 100644
---
On 2015-03-05 03:23, Lu, Baolu wrote:
Hi Kenneth Johansson,
Did you still get the bandwidth error when testing it with longer time?
no I have not seen it on any 3.19 kernel I have used so far. But It
could take a week to see it before so it's hard to say that I'm 100%
sure it's gone. But so
On Thu, Mar 5, 2015 at 2:11 PM, Hannes Reinecke h...@suse.de wrote:
On 03/05/2015 01:59 PM, Valentin Rothberg wrote:
The IRQF_DISABLED is a NOOP and has been scheduled for removal since
Linux v2.6.36 by commit 6932bf37bed4 (genirq: Remove IRQF_DISABLED from
core code).
According to commit
When dwc2 controller detects a disconnect interrupt,
dwc2_hcd_disconnect() should be called immediately to do clean-up
jobs and set port_connect_status_change flag to notify usb hub
driver disconnect status.
Signed-off-by: Yunzhi Li l...@rock-chips.com
---
drivers/usb/dwc2/core_intr.c | 3 +++
1
ping?
(2015/01/16 19:10), yoshihiro shimoda wrote:
Hi Iwamatsu-san,
INTSTS1 and INTENB1 register of renesas_usbhs can access only Host mode.
This adds process of accessing INTSTS1 and INTENB1 only when renesas_usbhs
is Host mode.
Signed-off-by: Nobuhiro
34 matches
Mail list logo
