On Sun, Jun 01, 2014 at 10:45:59AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Jun 01, 2014 at 11:32:17AM +0200, Johan Hovold wrote:
> > Remove the remaining two obsolete usb-serial subdriver entries from
> > MAINTAINERS, which were missed in the recent purge by commit
> > f896b7968b62 ("USB: Mainta
Hi,
Johan Hovold:
> > > -USB OPTION-CARD DRIVER
> > > -M: Matthias Urlichs
> > > -L: linux-usb@vger.kernel.org
> > > -S: Maintained
> > > -F: drivers/usb/serial/option.c
> >
> > Why are we taking away the maintainership of these individual drivers
> > from these developer
On 5/31/2014 5:35 AM, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, May 30, 2014 4:42 PM
On Fri, May 23, 2014 at 11:39:24AM -0700, Paul Zimmerman wrote:
Newer DWC3 controllers can be built for USB 2.0-only mode, where
most of the USB 3.0 circuitry is left out. To
On Sun, 1 Jun 2014, Daniel Kamil Kozar wrote:
> The device which identifies itself as a "USB Keykoard" (no typo) with
> VID:PID 1a2c:0023 does not seem to be handling the reports initialization
> very well. This results in a "usb_submit_urb(ctrl) failed: -1" message
> from the kernel when conne
Hello.
On 02-06-2014 7:31, Kuninori Morimoto wrote:
From: Kuninori Morimoto
Current usbhs gadget driver didn't complete STATUS stage after receiving.
It wasn't problem for us before, because some USB class doesn't use
DATA OUT stage in control transfer.
But, it is required on some device.
On Mon, 2014-05-26 at 13:17 +0200, Martin Rudhart wrote:
> Thank your for your reply,
>
> A summary of my Bugreport at Launchpad:
> My usb-Webcam Logitech c920 doesn't work when connected to my usb 3.0
> Host Controller (Etron EJ168a). When connected to a usb 2.0 Host
> Controller it works perfe
Hi Julius,
On Thu, May 29, 2014 at 4:07 AM, Julius Werner wrote:
> We originally tried using this driver on ChromiumOS and never got it
> to work reliably. IIRC the issue was that if the hub had already been
> initialized by firmware, the USB stack might enumerate it before the
> usb3503 driver
From: Oliver Neukum
grep must work, not matter the line length.
Signed-off-by: Oliver Neukum
---
drivers/usb/host/xhci.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 3008369..c
hi Greg:
2014-05-31 0:02 GMT+08:00 Greg KH :
> On Fri, May 30, 2014 at 11:28:36PM +0800, che-chun Kuo wrote:
>> We found when we plug in/out usb3.0 device for stress testing, once
>> usb_get_device_descriptor fail in hub_port_init, we will call
>> hub_port_disable.
>> Then usb3.0 device may not r
>> The SLOT ID for reset device command completion TRB's isn't very well
>> documented.
>> If VIA chose to set it to zero we should use what works best, e.g. dig out
>> the
>> SLOT ID from the queued command TRB. This has been working previously.
>
> For Reset Device in Section 4.6.1, it says:
>
On Mon, 2 Jun 2014, vichy wrote:
> hi Greg:
>
> 2014-05-31 0:02 GMT+08:00 Greg KH :
> > On Fri, May 30, 2014 at 11:28:36PM +0800, che-chun Kuo wrote:
> >> We found when we plug in/out usb3.0 device for stress testing, once
> >> usb_get_device_descriptor fail in hub_port_init, we will call
> >> h
On Mon, Jun 02, 2014 at 10:25:39AM -0400, Mike Remski wrote:
> Please CC me as not subscribed to list.
> Third party device, with FTDI chip on it. Get this when plugging device
> in. Discovered in kernel 2.6.32
Wow, that kernel is ancient. Please upgrade to a more recent kernel such
as v3.14.5,
On Fri, 30 May 2014, Leandro Liptak wrote:
> Adjunct is the output of dmidecode (:
> I didn't try setting "try_handoff" to 0, but I think behavior is
> predictable since in that case the kernel will never reach the
> pci_write in question. I found a kernel compiling option named "Enable
> PCI quir
On Sat, 31 May 2014, Pantelis Koukousoulas wrote:
> When dummy_hcd is created as a SuperSpeed controller (configurable via
> a module parameter) dummy_start() is called twice, once to make the
Not to "make" the hcds, but to start them running. The hcd structures
are created in dummy_hcd_probe().
On Sat, 31 May 2014, Pantelis Koukousoulas wrote:
> dummy_hcd uses jiffies and seems to assume that HZ=1000 and no
> tickless behavior. This makes its emulation not very faithful,
> especially for typical distro desktop kernels (HZ=250, tickless
> which means that e.g., when dummy_hcd asks for a d
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest version it's showing is 3.14. It appears that the ftdi_sio code
is largely the same as in 2.6.32, particularly in the
ftdi_set_max_packet_
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> over on
> http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
> latest version it's showing is 3.14. It appears
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions. Also, the unnecesary labels are removed and linux/device.h is
added to make sure the devm_*() routine declarations are unambiguously
available.
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest vers
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest vers
On Mon, Jun 02, 2014 at 12:09:36PM -0400, Mike Remski wrote:
> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> >[ Please avoid top-posting. ]
> >
> >On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> >>Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> >>over on
>
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> > [ Please avoid top-posting. ]
> >
> > On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> >> Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> >> over o
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross refere
On 06/02/2014 12:23 PM, Greg KH wrote:
On Mon, Jun 02, 2014 at 12:09:36PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions. Also, a label is done away with and clk_get is replaced by it
corresponding devm version and the clk_puts are done away with. The
labels are re
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
> On 06/02/2014 12:20 PM, Johan Hovold wrote:
> > On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> >> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> >>> [ Please avoid top-posting. ]
> >>>
> >>> On Mon, Jun 02, 2014 at 11:16:
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon,
> Ok, there was already a patch posted by you for this[1], which had
> quite a much discussion
> on it.
> Would you like to give some pointers based on that ?
> One that Olof had suggested was to use gpio-reset driver which is yet
> to make to mainline.
> But i think with that too we need to take c
The variable err is not initialized here, this patch uses it
to store an eventual error value from devm_clk_get().
Signed-off-by: Emil Goode
---
drivers/usb/misc/usb3503.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/mi
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
> On 06/02/2014 12:49 PM, Johan Hovold wrote:
> > On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
> >> On 06/02/2014 12:20 PM, Johan Hovold wrote:
> >>> On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> On 0
On 06/02/2014 01:46 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -040
On Mon, 2014-06-02 at 13:47, Oliver Neukum wrote:
Parameter error.
Please switch on xhci dynamic debugging.
But whatever you do, never ever mutilate a bug report like this.
Never ever grep around and drop parts of the report. And don't
put things on an external server one cannot access with all
From: Aleksander Morgado
Date: Thu, 29 May 2014 13:51:36 +0200
> This interface is unusable, as the cdc-wdm character device doesn't reply to
> any QMI command. Also, the out-of-tree Sierra Wireless GobiNet driver fully
> skips it.
>
> Signed-off-by: Aleksander Morgado
Applied.
--
To unsubscri
From: Aleksander Morgado
Date: Thu, 29 May 2014 13:44:45 +0200
> A set of new VID/PIDs retrieved from the out-of-tree GobiNet/GobiSerial
> Sierra Wireless drivers.
>
> Signed-off-by: Aleksander Morgado
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body
Changes since v1 [1]:
1/ Deleted "usb: fix hub_handle_remote_wakeup() only exists for
CONFIG_PM=y" in favor of the full refactoring of hub.c into
hub.c/hub_pm.c
2/ Added "usb: introduce usb_set_reset_resume" as its own patch as
suggested by Alan. [2]
3/ Added "usb: move hub power manage
Resuming a powered down port sometimes results in the port state being
stuck in the training sequence.
hub 3-0:1.0: debounce: port 1: total 2000ms stable 0ms status 0x2e0
port1: can't get reconnection after setting port power on, status -110
hub 3-0:1.0: port 1 status .02e0 after resume, -
In preparation for moving hub power management logic to its own file and
removing instances of #ifdef CONFIG_PM in hub.c, introduce a
usb_set_reset_resume() helper.
Signed-off-by: Dan Williams
---
drivers/usb/core/hub.c |5 ++---
include/linux/usb.h| 11 +++
2 files changed, 13
From: Lan Tianyu
describe the mechanisms for controlling port power policy and
discovering the port power state.
[oliver]: fixes, clarification of wakeup vs port-power-control
[sarah]: wordsmithing
[djbw]: updates for peer port changes
[alan]: review and fixes
Cc: Oliver Neukum
Acked-by: Alan S
On Mon, Jun 02, 2014 at 02:49:57PM -0700, Dan Williams wrote:
> Changes since v1 [1]:
>
> 1/ Deleted "usb: fix hub_handle_remote_wakeup() only exists for
>CONFIG_PM=y" in favor of the full refactoring of hub.c into
>hub.c/hub_pm.c
Now that the merge window is open, I'd really not like to
On Mon, Jun 2, 2014 at 3:02 PM, Greg KH wrote:
> On Mon, Jun 02, 2014 at 02:49:57PM -0700, Dan Williams wrote:
>> Changes since v1 [1]:
>>
>> 1/ Deleted "usb: fix hub_handle_remote_wakeup() only exists for
>>CONFIG_PM=y" in favor of the full refactoring of hub.c into
>>hub.c/hub_pm.c
>
> N
The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:
Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.15-rc8
for you to fetch changes up to 5dc2808c4729bf08048
From: Bjørn Mork
Date: Fri, 30 May 2014 09:31:02 +0200
> After considering the comments received after the ethtool coalesce
> support was commited, I have ended up concluding that we should
> remove it again, while we can, before it hits a release. The idea
> was not well enough thought through,
Hi Sergei
> > + /*
> > +* Transmission end
> > +*/
> > + if (*is_done) {
> > + if (usbhs_pipe_is_dcp(pipe))
>
> Why not collapse these into single *if*? That would decrease the
> indentation level...
This is same style with TX case
--
To unsubscribe from this list: s
The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:
Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.16-rc1
for you to fetch changes up to 4a95b1fce97756d0333
44 matches
Mail list logo
