On Wed, Feb 20, 2013 at 11:07:10PM -0500, Chao Xie wrote:
The patches are divied into 2 parts
snip
You do realize that we are currently in the middle of the merge window,
and don't have any time at all to look at these patches until 2 weeks
from now, at the earliest?
greg k-h
--
To unsubscribe
Hi,
On Thu, Feb 21, 2013 at 03:45:36AM +, Paul Zimmerman wrote:
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, February 20, 2013 1:20 AM
On Tue, Feb 19, 2013 at 06:50:06PM -0800, Paul Zimmerman wrote:
+#include linux/usb/hcd.h
Hi,
On Thu, Feb 21, 2013 at 03:34:56AM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, February 20, 2013 12:50 AM
On Tue, Feb 19, 2013 at 06:50:07PM -0800, Paul Zimmerman wrote:
This file contains the PCI bus interface glue for the DWC2
driver
Hi,
On Thu, Feb 21, 2013 at 03:22:54AM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, February 20, 2013 12:29 AM
On Tue, Feb 19, 2013 at 06:50:03PM -0800, Paul Zimmerman wrote:
Here is v4 of the DWC2 patch set. I made most of the changes you asked
Hi,
On Wed, Feb 20, 2013 at 03:16:04PM -0500, Alan Stern wrote:
We could just remove the warning. It was mostly put in to help me debug
the new bandwidth allocation code, and just in case there was a host
controller who accidentially mis-managed the endpoint context state.
No objection.
Hi Alex,
Do we have a chipidea repo which is queued for mainline?
We have several patchsets for chipidea these monthes, I
don't know their status. For me, I would like based
on your tree if it exists.
Thanks.
--
Best Regards,
Peter Chen
--
To unsubscribe from this list: send the line
Hi,
On Tue, Feb 19, 2013 at 06:50:05PM -0800, Paul Zimmerman wrote:
+#include linux/kernel.h
+#include linux/module.h
+#include linux/moduleparam.h
+#include linux/spinlock.h
+#include linux/interrupt.h
+#include linux/dma-mapping.h
+#include linux/debugfs.h
+#include linux/seq_file.h
Hi,
On Tue, Feb 19, 2013 at 06:50:04PM -0800, Paul Zimmerman wrote:
+static const char *dwc2_op_state_str(struct dwc2_hsotg *hsotg)
+{
+#ifdef DEBUG
+ switch (hsotg-op_state) {
+ case OTG_STATE_A_HOST:
+ return a_host;
+ case OTG_STATE_A_SUSPEND:
+
On Wed, 20 Feb 2013, Haribabu Narayanan wrote:
- Are EHCI_TUNE_CERR and QH_XACTERR_MAX applicable to exactly the same
set of bus-level errors (namely the single error: XactErr) ? Or in
other words, are only the errors that are retried in EHCI-software by
using QH_XACTERR_MAX benefiting
On Wed, 20 Feb 2013, Sarah Sharp wrote:
Of course, in your case this doesn't matter. In the memory image, the
timer is active. Hence it is still active when the system resumes,
even though xhci_suspend _was_ called.
Ah, I see now. So basically any memory changes in xhci_suspend will
On Wed, 20 Feb 2013, Dâniel Fraga wrote:
On Wed, 20 Feb 2013 10:20:07 -0500 (EST)
Alan Stern st...@rowland.harvard.edu wrote:
The important module does not contain usb in its name. :-(
Probably this is not a bug at all, but simply a failure to load the
ehci-pci module. If the USB
On 02/21/2013 10:46 AM, Alan Stern wrote:
On Wed, 20 Feb 2013, Sarah Sharp wrote:
Of course, in your case this doesn't matter. In the memory image, the
timer is active. Hence it is still active when the system resumes,
even though xhci_suspend _was_ called.
Ah, I see now. So basically any
On Wed, 20 Feb 2013 valdis.kletni...@vt.edu wrote:
On Wed, 20 Feb 2013 16:07:49 -0800, Greg Kroah-Hartman said:
PS-2 connectors can not normally handle hotplugging, the protocol
doesn't allow it, and for some unlucky devices, it could actually fry
the motherboard or the PS-2 device.
On Thu, 21 Feb 2013, Manjunath Goudar wrote:
On 20 February 2013 21:43, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 15 Feb 2013, Manjunath Goudar wrote:
Separate the SPEAr host controller driver from ehci-hcd host code
into its own driver module.
In V2:
Replaced
Hi Sarah,
Answering your question, yes, per our previous testing with our re-driver part,
all ports are subject to suffer of the failing condition (Compliance Mode)
after system resumes from Sleep/Hibernate no matter if ports entered to U0
before system suspension. That is why the original
On Thu, Feb 21, 2013 at 10:53:20AM -0500, Tony Camuso wrote:
On 02/21/2013 10:46 AM, Alan Stern wrote:
On Wed, 20 Feb 2013, Sarah Sharp wrote:
Of course, in your case this doesn't matter. In the memory image, the
timer is active. Hence it is still active when the system resumes,
even
On Thu, Feb 21, 2013 at 10:46:49AM -0500, Alan Stern wrote:
On Wed, 20 Feb 2013, Sarah Sharp wrote:
Of course, in your case this doesn't matter. In the memory image, the
timer is active. Hence it is still active when the system resumes,
even though xhci_suspend _was_ called.
Ah,
The following changes since commit 200e0d994d9d1919b28c87f1a5fb99a8e13b8a0f:
USB: storage: optimize to match the Huawei USB storage devices and support
new switch command (2013-02-04 10:41:40 -0800)
are available in the git repository at:
I trust you won't mind if I put this on the public mailing list. In
general, problems of this sort should be discussed in public. In
addition to creating a permanent record in the various mailing list
archives, it also gives other people a chance to learn about these
problems and to chime in if
On Thu, Feb 21, 2013 at 05:12:45PM +0800, Peter Chen wrote:
Hi Alex,
Do we have a chipidea repo which is queued for mainline?
We have several patchsets for chipidea these monthes, I
don't know their status. For me, I would like based
on your tree if it exists.
Yeah, I would like to know
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, February 21, 2013 12:58 AM
On Thu, Feb 21, 2013 at 03:22:54AM +, Paul Zimmerman wrote:
Building and validating a new FPGA image is a lengthy task. If I can make
things work by tweaking some module
On Wed, 20 Feb 2013, Ronald wrote:
Paul Hartman pointed me at the kernel cmdline option log_buf_len=16M.
It's kind of confusing that the compile time option is mentioning a
limit while the kernel cmdline option is limit free. I forgot about
those differences. Attached is a complete log
On Thu, Feb 21, 2013 at 07:33:45PM +, Paul Zimmerman wrote:
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, February 21, 2013 12:58 AM
On Thu, Feb 21, 2013 at 03:22:54AM +, Paul Zimmerman wrote:
Building and validating a new FPGA image is a
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, February 21, 2013 1:16 AM
On Tue, Feb 19, 2013 at 06:50:05PM -0800, Paul Zimmerman wrote:
+#ifdef DWC2_TRACK_MISSED_SOFS
+#warning Compiling code to track missed SOFs
+#define FRAME_NUM_ARRAY_SIZE 1000
+
+/* This function is
-Original Message-
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Thursday, February 21, 2013 11:43 AM
On Thu, Feb 21, 2013 at 07:33:45PM +, Paul Zimmerman wrote:
I can pare the user-visible module parameters down to 6, that would
give us most of
I highly doubt hot-insert and hot-remove of HDDs from the 4-bay
container (without removing the corresponding USB/eSATA adaptor) will
work.
The USB/eSATA adaptor does not have a way to inform the host that the
eSATA side has been disconnected from the HDD. That functionality
isn't in the
On Thu, Feb 21, 2013 at 10:40 AM, Greg KH gre...@linuxfoundation.org wrote:
USB patches for 3.9-rc1
Here's the big USB merge for 3.9-rc1
Nothing major, lots of gadget fixes, and of course, xhci stuff.
Ok, so there were a couple of conflicts with Thierry Reding's series
to convert
Dave == Dave Tubbs dave.tu...@portalislc.com writes:
Hi,
Dave From: Dave Tubbs
Dave Below is a patch that handles situations where TD's submitted to
Dave a c67x00 USB Host Controller may not be executed before being
Dave handled by the driver and given back to the URB. This can cause
Dave
On Thu, Feb 21, 2013 at 01:23:05PM -0500, Alan Stern wrote:
On Thu, 21 Feb 2013, Sarah Sharp wrote:
That's a good idea. Do you want to implement it? All it requires is
to add an extra argument to the hc_driver.pci_suspend method, modify
the PCI-based HCDs appropriately (there aren't
On 13-02-21 02:26 PM, Sarah Sharp wrote:
Cc-ing the SCSI and USB storage list.
Folks, does the attached picture look like a sane setup? I've never
used mini-SaS to eSATA adapter before, let alone with four eSATA to USB
3.0 adapters.
Well SAS to eSATA is okay (works for me: LSI SAS9212-4i4e
On Thu, Feb 21, 2013 at 05:12:45PM +0800, Peter Chen wrote:
Do we have a chipidea repo which is queued for mainline?
We have several patchsets for chipidea these monthes, I
don't know their status. For me, I would like based
on your tree if it exists.
Michael and Sascha do also have a bunch
Commit 71c731a2 (usb: host: xhci: Fix Compliance Mode on SN65LVPE502CP
Hardware) was a workaround for systems using the SN65LVPE502CP,
controller, but it introduced a bug in resume from hibernate.
The fix created a timer, comp_mode_recovery_timer, which is deleted from
a timer list when
Sarah,
Here it is. Just finished testing it.
The differences between this v4 patch and the v1 patch is an explanation
that incorporates the knowledge shared by Alan Stern concerning what is
actually happening.
I have omitted the cosmetic changes suggested by Sergei. There may be
one cosmetic
Hi Rafael,
I'm running into some issues with PCI D3 wakeup on the latest version of
the Lynx Point chipset. I can give you the stepping and BIOS version
privately if you need it.
Basically, I think PMEs are being lost somewhere in the ACPI or PCI
stack. I'm not sure how to further debug this
On Thu, Feb 21, 2013 at 07:57:14PM +, Paul Zimmerman wrote:
-Original Message-
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Thursday, February 21, 2013 11:43 AM
On Thu, Feb 21, 2013 at 07:33:45PM +, Paul Zimmerman wrote:
I can pare the
On Thu, Feb 21, 2013 at 12:25:24PM -0800, Linus Torvalds wrote:
On Thu, Feb 21, 2013 at 10:40 AM, Greg KH gre...@linuxfoundation.org wrote:
USB patches for 3.9-rc1
Here's the big USB merge for 3.9-rc1
Nothing major, lots of gadget fixes, and of course, xhci stuff.
Ok, so there were
On Thu, 21 Feb 2013, Tony Camuso wrote:
Commit 71c731a2 (usb: host: xhci: Fix Compliance Mode on SN65LVPE502CP
Hardware) was a workaround for systems using the SN65LVPE502CP,
controller, but it introduced a bug in resume from hibernate.
The fix created a timer, comp_mode_recovery_timer,
On Thu, 21 Feb 2013, Sarah Sharp wrote:
All right, this shouldn't be too big a job. I'll stick it on the
to-do list, just after getting rid of CONFIG_USB_SUSPEND.
Oh, that's going away? Interesting. Any particular reason why?
See
On Thu, Feb 21, 2013 at 03:48:42PM -0500, Douglas Gilbert wrote:
On 13-02-21 02:26 PM, Sarah Sharp wrote:
Cc-ing the SCSI and USB storage list.
Folks, does the attached picture look like a sane setup? I've never
used mini-SaS to eSATA adapter before, let alone with four eSATA to USB
3.0
On Thu, Feb 21, 2013 at 05:27:00PM -0300, Fabio David wrote:
On Thu, Feb 21, 2013 at 4:26 PM, Sarah Sharp sarah.a.sh...@linux.intel.com
wrote:
On Tue, Jan 29, 2013 at 12:56:02PM -0200, Fabio David wrote:
Do you have any suggestions?
A couple possible root causes come to mind:
1.
In many cases, documentation around composite drivers suggest
setting the idVendor and other module params as follows:
$ insmod g_ffs.ko idVendor=ID iSerialNumber=string
However, this won't work if the driver is not compiled in as a
module, as the module_param permissions are S_IRUGO.
Thus this
On Thu, Feb 21, 2013 at 05:04:49PM -0500, Alan Stern wrote:
On Thu, 21 Feb 2013, Tony Camuso wrote:
This patch avoids the problem by deleting the timer in xhci_resume()
when resuming from hibernate. Now xhci_resume() can safely make the
call to create a new instance of this timer, whether
On Thursday, February 21, 2013 01:41:45 PM Sarah Sharp wrote:
Hi Rafael,
Hi,
I'm running into some issues with PCI D3
Do you mean D3hot?
wakeup on the latest version of the Lynx Point chipset. I can give you the
stepping and BIOS version privately if you need it.
Basically, I think
On Thu, Feb 21 2013, John Stultz wrote:
In many cases, documentation around composite drivers suggest
setting the idVendor and other module params as follows:
$ insmod g_ffs.ko idVendor=ID iSerialNumber=string
However, this won't work if the driver is not compiled in as a
module, as the
On 02/21/2013 02:52 PM, Michal Nazarewicz wrote:
On Thu, Feb 21 2013, John Stultz wrote:
In many cases, documentation around composite drivers suggest
setting the idVendor and other module params as follows:
$ insmod g_ffs.ko idVendor=ID iSerialNumber=string
However, this won't work if the
On 02/21/2013 02:52 PM, Michal Nazarewicz wrote:
If the driver is not compiled as a module, setting those variables
won't work anyway. Or am I missing something?
On Fri, Feb 22 2013, John Stultz wrote:
Huh. It worked in my testing. But maybe that's only the first time its
set? I'll play
On Thursday, February 21, 2013 03:52:11 PM Sarah Sharp wrote:
On Thu, Feb 21, 2013 at 11:54:55PM +0100, Rafael J. Wysocki wrote:
On Thursday, February 21, 2013 01:41:45 PM Sarah Sharp wrote:
Hi Rafael,
Hi,
I'm running into some issues with PCI D3
Do you mean D3hot?
I
I contacted Digi about this issue and the tech rep indicated that he had no
record of the device number previously reported by me (0x0288).
I was provided with a file of Digi devices as far as he was aware. Shall I send
this file to linux-usb@vger.kernel.org or a particular address?
From this
On Mon, Feb 04, 2013 at 02:24:32PM +0100, Sascha Hauer wrote:
Even if a chipidea core is otg capable the board may not. This allows
to explicitly set the core to host/peripheral mode. Without these
flags the driver falls back to the old behaviour.
Signed-off-by: Sascha Hauer
In looking further at the Digi device file it looks like Digi may keep the same
product name (in this case Edgeport 4/i) across different product versions
under the hood.
Snipped from the Digi device file provided by tech support:
[Digi.NTAMD64]
; 1st Generation (930) VID/PIDs
On Thu, Feb 21, 2013 at 1:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 20 Feb 2013, Ronald wrote:
Paul Hartman pointed me at the kernel cmdline option log_buf_len=16M.
It's kind of confusing that the compile time option is mentioning a
limit while the kernel cmdline option is
On Thu, Feb 21, 2013 at 01:58:39PM -0800, Greg KH wrote:
On Thu, Feb 21, 2013 at 12:25:24PM -0800, Linus Torvalds wrote:
On Thu, Feb 21, 2013 at 10:40 AM, Greg KH gre...@linuxfoundation.org
wrote:
USB patches for 3.9-rc1
Here's the big USB merge for 3.9-rc1
Nothing major,
On Thu, Feb 21, 2013 at 1:42 PM, Alan Stern st...@rowland.harvard.edu wrote:
The output is all too clear. Both of you are using EHCI controllers
made by VIA, and they both exhibit this same problem -- which is
clearly caused by a silicon bug.
It's entirely possible that the NVIDIA
ping..
On Mon, Feb 4, 2013 at 2:57 PM, Bob Liu lliu...@gmail.com wrote:
This patch makes musb can work on blackfin bf60x series soc platform.
Bf60x uses MHDRC RTL version 2.0 musb ip core which don't need a lot of
blackfin specific anomalies anymore.
Signed-off-by: Bob Liu lliu...@gmail.com
From: Yuan-Hsin Chen yuan...@gmail.com
Due to fusb300 controller modification, stall clear procedure should be
modified consistantly. This patch also fixes software bugs: only
enter IDMA_RESET when the condition matched and disable corresponding
PRD interrupt in IDMA_RESET.
Signed-off-by:
55 matches
Mail list logo
