Re: Strange behaviour...

2014-12-24 Thread Peter Chen
On Wed, Dec 24, 2014 at 01:51:32PM +0100, gianluca wrote: > On 12/23/2014 01:12 AM, Peter Chen wrote: > >Ok, then just try to get the working version, and find the difference. > >>From my mind, it should be PLL related. > > > > Here I am again ;-) > > The following log is taken by an automatic-sc

Re: [PATCH 2/3] usb: chipidea: Add chipidea revision information

2014-12-24 Thread Peter Chen
On Wed, Dec 24, 2014 at 05:22:44PM +0100, Stefan Agner wrote: > On 2014-12-19 10:55, Sanchayan Maity wrote: > > Define ci_get_revision API to know the controller revision > > information according to chipidea 1.1a, 2.0a, 2.4 and 2.5a > > spec. Besides, add one entry in struct ci_hdrc to indicate >

Re: [PATCH 1/3] usb: chipidea: Add identification registers access APIs

2014-12-24 Thread Sanchayan Maity
On 12/25/2014 07:43 AM, Peter Chen wrote: > On Wed, Dec 24, 2014 at 09:45:31PM +0530, Sanchayan Maity wrote: >> On 12/24/2014 09:30 PM, Stefan Agner wrote: >>> On 2014-12-19 10:55, Sanchayan Maity wrote: Using hw_write_id_reg and hw_read_id_reg to write and read identification registers c

Re: [PATCH 1/3] usb: chipidea: Add identification registers access APIs

2014-12-24 Thread Peter Chen
On Wed, Dec 24, 2014 at 09:45:31PM +0530, Sanchayan Maity wrote: > On 12/24/2014 09:30 PM, Stefan Agner wrote: > > On 2014-12-19 10:55, Sanchayan Maity wrote: > >> Using hw_write_id_reg and hw_read_id_reg to write and read > >> identification registers contents. This can be used to get > >> control

Re: [PATCH 1/3] usb: chipidea: Add identification registers access APIs

2014-12-24 Thread Peter Chen
On Wed, Dec 24, 2014 at 05:00:05PM +0100, Stefan Agner wrote: > On 2014-12-19 10:55, Sanchayan Maity wrote: > > Using hw_write_id_reg and hw_read_id_reg to write and read > > identification registers contents. This can be used to get > > controller information, change some system configurations > >

Re: [RFC/PATCH] extcon: otg_gpio: add driver for USB OTG port controlled by GPIO(s)

2014-12-24 Thread David Cohen
On Wed, Dec 24, 2014 at 11:08:52AM +0800, Peter Chen wrote: > On Tue, Dec 23, 2014 at 11:40:23AM -0800, David Cohen wrote: > > Hi Peter, > > > > Thanks for the review. > > > > On Tue, Dec 23, 2014 at 09:25:18AM +0800, Peter Chen wrote: > > > On Mon, Dec 22, 2014 at 02:43:37PM -0800, David Cohen w

Re: [RFC/PATCH] extcon: otg_gpio: add driver for USB OTG port controlled by GPIO(s)

2014-12-24 Thread David Cohen
Hi Felipe, Thanks replying. On Tue, Dec 23, 2014 at 06:29:04PM -0600, Felipe Balbi wrote: > Hi, > > On Mon, Dec 22, 2014 at 02:43:37PM -0800, David Cohen wrote: > > Some platforms have an USB OTG port fully (or partially) controlled by > > GPIOs: > > > > (1) USB ID is connected directly to GPIO

Re: Query regarding root hub reset

2014-12-24 Thread Alan Stern
On Wed, 24 Dec 2014, Peter Chen wrote: > On Tue, Dec 23, 2014 at 03:15:45PM -0500, Alan Stern wrote: > > On Tue, 23 Dec 2014, Peter Chen wrote: > > > > > > The Linux USB stack supports turning off port power only under a very > > > > limited > > > > set of conditions. For example, if the port i

Re: [PATCH 2/3] usb: chipidea: Add chipidea revision information

2014-12-24 Thread Stefan Agner
On 2014-12-19 10:55, Sanchayan Maity wrote: > Define ci_get_revision API to know the controller revision > information according to chipidea 1.1a, 2.0a, 2.4 and 2.5a > spec. Besides, add one entry in struct ci_hdrc to indicate > revision information. This can be used for adding different > code for

Re: [PATCH 1/3] usb: chipidea: Add identification registers access APIs

2014-12-24 Thread Sanchayan Maity
On 12/24/2014 09:30 PM, Stefan Agner wrote: > On 2014-12-19 10:55, Sanchayan Maity wrote: >> Using hw_write_id_reg and hw_read_id_reg to write and read >> identification registers contents. This can be used to get >> controller information, change some system configurations >> and so on. > > Check

Re: USB Creative Soundcard non-functioning on 3.13 kernel and above

2014-12-24 Thread Alan Stern
On Tue, 23 Dec 2014 robton...@gmail.com wrote: > On Tuesday 23 December 2014 15:06:17 Alan Stern wrote: > > On Mon, 22 Dec 2014 robton...@gmail.com wrote: > > > Ok I tried that kernel option first, and that actually worked without > > > issue. I then tried your patch without that kernel option set

Re: [PATCH 0/3] usb: chipidea: add one errata for revision 2.40a

2014-12-24 Thread Stefan Agner
On 2014-12-22 02:18, Peter Chen wrote: > On Fri, Dec 19, 2014 at 03:25:26PM +0530, Sanchayan Maity wrote: >> The first two patches add identification register API's. These can >> be used to get controller's revision. >> >> The third patch implements an errata for revision 2.40a. Not sure >> which o

Re: [PATCH v5] usb: gadget: f_fs: add "no_disconnect" mode

2014-12-24 Thread Michal Nazarewicz
On Thu, Dec 18 2014, Robert Baldyga wrote: > Since we can compose gadgets from many functions, there is the problem > related to gadget breakage while FunctionFS daemon being closed. FFS > function is userspace code so there is no way to know when it will close > files (it doesn't matter what is th

Re: [PATCH v3] usb: gadget: ffs: Fix sparse error

2014-12-24 Thread Michal Nazarewicz
On Wed, Dec 24 2014, Rohith Seelaboyina wrote: > This patch fixes the sparse error in functionfs > driver. > > drivers/usb/gadget/function/f_fs.c:400:44: error: bad > constant experssion. > > Dynamic memory allocation through kcalloc is more safer > than declaring variable array size, Fix this erro

Re: Strange behaviour...

2014-12-24 Thread gianluca
On 12/23/2014 01:12 AM, Peter Chen wrote: Ok, then just try to get the working version, and find the difference. From my mind, it should be PLL related. Here I am again ;-) The following log is taken by an automatic-script during bootup (rc.local). the smtp_device.c throw a time out, so th

[PATCH v3] usb: gadget: ffs: Fix sparse error

2014-12-24 Thread Rohith Seelaboyina
This patch fixes the sparse error in functionfs driver. drivers/usb/gadget/function/f_fs.c:400:44: error: bad constant experssion. Dynamic memory allocation through kcalloc is more safer than declaring variable array size, Fix this error by using kcalloc for memory allocation, Check if memory all

Re: 3.18 / 3.19-rc1: ehci scheduling bug?

2014-12-24 Thread Russell King - ARM Linux
On Wed, Dec 24, 2014 at 12:00:00PM +0100, Frank Schäfer wrote: > See > https://bugzilla.kernel.org/show_bug.cgi?id=72891 > > Solved by > http://www.spinics.net/lists/linux-usb/msg118366.html Thanks, that seems to solve it. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up

Re: [PATCH v2] usb: gadget: ffs: Fix sparse error

2014-12-24 Thread Joe Perches
On Wed, 2014-12-24 at 14:48 +0530, Rohith Seelaboyina wrote: > Dynamic memory allocation through kcalloc is more safer > than declaring variable array size, Fix this error by > using kcalloc for memory allocation, Check if memory > allocation is successful and return -ENOMEM on failure. > > Signed

Re: 3.18 / 3.19-rc1: ehci scheduling bug?

2014-12-24 Thread Frank Schäfer
Am 24.12.2014 um 11:51 schrieb Russell King - ARM Linux: > While testing an EM28xx based USB DVB stick which I've recently acquired, > I find that occasionally the driver stops responding after it returns > -EFBIG from one of its ioctls. I've no idea whether there's a previous > kernel version wh

3.18 / 3.19-rc1: ehci scheduling bug?

2014-12-24 Thread Russell King - ARM Linux
While testing an EM28xx based USB DVB stick which I've recently acquired, I find that occasionally the driver stops responding after it returns -EFBIG from one of its ioctls. I've no idea whether there's a previous kernel version which works. Finding the EFBIG return in ehci-sched.c, I decided to

[PATCH 2/2] USB: ehci-platform: Support ehci reset after resume quirk

2014-12-24 Thread Wu Liang feng
The Rockchip rk3288 EHCI controller doesn't properly detect the case when a device is removed during suspend. Specifically, when usb resume from suspend, the EHCI controller maintaining the USB state (FLAG_CF is 1, Current Connect Status is 1), but a USB device (like a USB camera on rk3288) may hav

[PATCH v2 0/2] Support EHCI reset after resume quirk

2014-12-24 Thread Wu Liang feng
[PATCH v2 1/2]: Add an optional property "needs-reset-on-resume" in usb-ehci dt-bingdings. [PATCH v2 2/2]: modify ehci-platform driver to support ehci reset after resume quirk if necessary. Wu Liang feng (2): dt-bindings: usb-ehci: Add an optional property

[PATCH 1/2] dt-bindings: usb-ehci: Add an optional property "needs-reset-on-resume"

2014-12-24 Thread Wu Liang feng
Add device-tree bindings for EHCI so we can use "needs-reset-on-resume" property to force EHCI reset after resume if necessary. This is necessary on platforms like rk3288 that need a reset after resume to detect if a device has been disconnected during suspend time. Signed-off-by: Wu Liang feng R

[PATCH] usb: host: ehci-tegra: request deferred probe when failing to get phy

2014-12-24 Thread Vince Hsu
The commit 1290a958d48e ("usb: phy: propagate __of_usb_find_phy()'s error on failure") changed the condition to return -EPROBE_DEFER to host driver. Originally the Tegra host driver depended on the returned -EPROBE_DEFER to get the phy device later when booting. Now we have to do that explicitly.

RE: [PATCH v2] renesas_usbhs: fix platform init error message

2014-12-24 Thread yoshihiro shimoda
Hi Felipe-san, Sergei-san, > -Original Message- > From: Felipe Balbi [mailto:ba...@ti.com] > Sent: Wednesday, December 24, 2014 4:17 AM > > On Fri, Dec 19, 2014 at 03:46:41PM +0300, Sergei Shtylyov wrote: > > Hello. > > > > On 12/19/2014 4:33 AM, yoshihiro shimoda wrote: > > > > [...] > >

Re: [PATCH 0/3] usb: chipidea: add one errata for revision 2.40a

2014-12-24 Thread Sanchayan Maity
On 12/24/2014 02:30 PM, Peter Chen wrote: > >> >> On 12/23/2014 05:39 AM, Peter Chen wrote: >>> On Mon, Dec 22, 2014 at 06:39:42PM +0530, Sanchayan Maity wrote: On 12/22/2014 06:48 AM, Peter Chen wrote: > On Fri, Dec 19, 2014 at 03:25:26PM +0530, Sanchayan Maity wrote: >> The first t

[PATCH v2] usb: gadget: ffs: Fix sparse error

2014-12-24 Thread Rohith Seelaboyina
This patch fixes the sparse error in functionfs driver. drivers/usb/gadget/function/f_fs.c:400:44: error: bad constant experssion. Dynamic memory allocation through kcalloc is more safer than declaring variable array size, Fix this error by using kcalloc for memory allocation, Check if memory all

RE: [PATCH 0/3] usb: chipidea: add one errata for revision 2.40a

2014-12-24 Thread Peter Chen
> > On 12/23/2014 05:39 AM, Peter Chen wrote: > > On Mon, Dec 22, 2014 at 06:39:42PM +0530, Sanchayan Maity wrote: > >> On 12/22/2014 06:48 AM, Peter Chen wrote: > >>> On Fri, Dec 19, 2014 at 03:25:26PM +0530, Sanchayan Maity wrote: > The first two patches add identification register API's.