On Fri, Mar 21, 2014 at 4:58 AM, Pratyush Anand wrote:
> How is your image sensor driver implemented?
> If it is in v4l2 framework, then you can send your data to USB host
> using uvc framework. See: drivers/usb/gadget/webcam.c
>
> The above would be be the standard way of doing such application.
On Thu, 2014-03-20 at 16:53 -0700, Julius Werner wrote:
> >> Can you please explain why we need to check if the waitqueue is active?
> >
> > and add a comment that answers the above question.
>
> Oh the braces!!! Well, that's just mean...
Yes, I was unsure about this, but so it is.
>
On Thu, 2014-03-20 at 14:19 -0700, Grant Grundler wrote:
> On Thu, Mar 20, 2014 at 9:35 AM, Grant Grundler wrote:
> > On Thu, Mar 20, 2014 at 12:15 AM, Oliver Neukum wrote:
> > ...
> >> I have an idea. Could you test this patch?
> > ...
> >> - if (dev->wait) {
> > ..
> >> + if (waitqu
On Wed, Mar 19, 2014 at 10:06:28PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 03/19/2014 01:01 PM, Li Jun wrote:
>
> >Init otg_port number of otg capable host to be 1 at host start.
>
> >Signed-off-by: Li Jun
> >---
> > drivers/usb/chipidea/host.c |7 ++-
> > 1 file changed, 6 inser
Hi Sarah,
I have to implement dynamic U1/U2 initiation on a dwc3 based xhci
platform. I can see that my host starts sending LGO_U1 (when idle) by
enabling XHCI_LPM_SUPPORT & XHCI_INTEL_HOST quirk in xhci_plat_quirks
and using xhci_enable/disable_usb3_lpm_timeout in
xhci_plat_xhci_driver. But offc
changes since v3:
* Use GFP_ATOMIC in xhci_stop_device() because we hold a spinlock
* Don't queue commands if host is dying.
* Flush command queue when host is dying (delete all commands in queue, call
pending completions/free commands).
changes since v2:
squash first 7
Use one timer to control command timeout.
start/kick the timer every time a command is completed and a
new command is waiting, or a new command is added to a empty list.
If the timer runs out, then tag the current command as "aborted", and
start the xhci command abortion process.
Previously each
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb/
Create a list to store command structures, add a structure to it every time
a command is submitted, and remove it from the list once we get a
command completion event matching the command.
Callers that wait for completion will free their command structures themselves.
The other command structures
To create a global command queue we require that each command put on the
command ring is submitted with a command structure.
Functions that queue commands and wait for completion need to allocate a command
before submitting it, and free it once completed. The following command queuing
functions ne
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's mini-desktop, the Intense-PC2.
The bug can be av
Hi, (ever so awesome and we are all super unworthy) - Kernel peoples!
I have found this dmesg error message which appears to be written in
the xHCI host controller. (or maybe it originated in EHCI, i don't
know.)
None the less the issue is: "Not enough host controller resources for
new device sta
On Thu, 20 Mar 2014, Aaro Koskinen wrote:
> octeon-hcd will crash the kernel when SLOB is used. This usually happens
> after the 18-byte control transfer when a device descriptor is read.
> The DMA engine is always transfering full 32-bit words and if the
> transfer is shorter, some random garba
I want to resume the usb device on some event, so i want to check if
it is suspended. I think by above method i can check if the device is
already suspended, but may be i will miss to resume the device if it
is suspending. Is there any way through which i can check if device is
suspending?
On Thu,
On 03/21/2014 12:01 PM, Denis Turischev wrote:
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's
On Fri, 2014-03-21 at 17:17 +0530, Jagdish Gedia wrote:
> I want to resume the usb device on some event, so i want to check if
> it is suspended. I think by above method i can check if the device is
> already suspended, but may be i will miss to resume the device if it
> is suspending. Is there any
On 03/20/2014 11:10 PM, Sarah Sharp wrote:
On Sun, Mar 16, 2014 at 07:52:30PM +0100, Martin Dauskardt wrote:
Hi Sarah,
I lost track on this issue. Is there a final patch? Is it ready for
integration into the kernel? Is there any kernel version that
includes a fix? Is there any timeline?
Mathi
On Thu, 20 Mar 2014, James Bottomley wrote:
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index 771c16b..c52bfb2 100644
> --- a/drivers/scsi/scsi_error.c
> +++ b/drivers/scsi/scsi_error.c
> @@ -145,14 +145,14 @@ scmd_eh_abort_handler(struct work_struct *work)
>
On Fri, Mar 21, 2014 at 08:09:09AM -0700, Sarah Sharp wrote:
> The following changes since commit 1d10255c1c496557a5674e651c4ebbe0f61279f2:
>
> USB: disable reset-resume when USB_QUIRK_RESET is set (2014-03-19 14:00:32
> -0700)
>
> are available in the git repository at:
>
> git://git.kerne
I'm transitioning maintainership of the xHCI driver to my colleague,
Mathias Nyman. The xHCI driver is in good shape, and it's time for me
to move on to the next shiny thing. :)
There's a few known outstanding bugs that we have plans for how to fix:
1. Clear Halt issue that means some USB scanne
The following changes since commit 1d10255c1c496557a5674e651c4ebbe0f61279f2:
USB: disable reset-resume when USB_QUIRK_RESET is set (2014-03-19 14:00:32
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
tags/for-usb-next-adventure
f
[ Adding Mathias Nyman as CC. ]
On Thu, Mar 20, 2014 at 01:52:16PM -0700, Benjamin West wrote:
> On Tue, Mar 18, 2014 at 1:10 AM, Johan Hovold wrote:
> > On Mon, Mar 17, 2014 at 11:58:57PM -0700, Benjamin West wrote:
> >> On Mon, Mar 17, 2014 at 11:40 AM, Johan Hovold wrote:
> >> >> issues. It'
On Thu, Mar 20, 2014 at 02:24:30PM -0700, Benjamin West wrote:
> Johan and other usb-serial/ftdi maintainers,
Thanks for the patch! A couple of minor issues below.
> Here is a small patch for you which adds the PID for Asante Snap
> Pump's FTDI data cable to the device list. The Asante Snap pum
On 03/21/2014 11:35 AM, Mathias Nyman wrote:
+void xhci_handle_command_timeout(unsigned long data)
+{
+ struct xhci_hcd *xhci;
+ int ret;
+ unsigned long flags;
+ xhci = (struct xhci_hcd *) data;
+ /* mark this command to be cancelled */
+ spin_lock_irqsave
Cc-ing Mathias Nyman, who is taking over as xHCI driver maintainer.
On Fri, Mar 21, 2014 at 02:37:22PM +0530, Pratyush Anand wrote:
> Hi Sarah,
>
> I have to implement dynamic U1/U2 initiation on a dwc3 based xhci
> platform. I can see that my host starts sending LGO_U1 (when idle) by
> enabling
On Fri, Mar 21, 2014 at 1:33 AM, Oliver Neukum wrote:
...
> Very well. Thorough testing is good. I'll wait for the result. Could
> you notify me of the final outcome?
Ceratinly. Bad news is I had to restart my workstation that was
driving the test due to completely different issue (loopbacks hung
Cc-ing Mathias Nyman, who is taking over as xHCI maintainer.
On Fri, Mar 21, 2014 at 11:22:07AM +0800, Rick Chen wrote:
> Hi Sarah,
>
> I use linux 3.13.6 to test Logitech C310 web cam but encounter the
> following message and usb controller is disabled and all usb device freeze.
>
> [51237.0450
On Sat, Mar 08, 2014 at 04:42:24PM +0100, Steinar H. Gunderson wrote:
> I'm using a Sundtek DVB-C USB stick (with their userspace driver which works
> over usbfs, as I understand it), and when I w_scan, after ~10 minutes or so
> this happens:
Hi,
Did anyone have a chance to look at this?
/* Stei
On Fri, Mar 21, 2014 at 08:09:09AM -0700, Sarah Sharp wrote:
> The following changes since commit 1d10255c1c496557a5674e651c4ebbe0f61279f2:
>
> USB: disable reset-resume when USB_QUIRK_RESET is set (2014-03-19 14:00:32
> -0700)
>
> are available in the git repository at:
>
> git://git.kerne
There is timeout error during initialization:
kernel: [ 14.167086] hid-multitouch 0003:2512:5003.0001: usb_submit_urb(ctrl)
failed: -1
kernel: [ 14.167135] hid-multitouch 0003:2512:5003.0001: timeout initializing
reports
kernel: [ 14.167407] input: RNDPLUS Co., LTD PULSEIR TSR4601 as
/de
$ uname -a
Linux hellcat 3.13.6-gentoo #1 SMP PREEMPT Tue Mar 18 15:37:31 MDT 2014 x86_64
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz GenuineIntel GNU/Linux
$ dmesg
[90294.076903] usb 4-4.3.3: new SuperSpeed USB device number 19 using xhci_hcd
[90294.199632] usb-storage 4-4.3.3:1.0: USB Mass Storage
On Fri, Mar 21, 2014 at 3:39 PM, Yufeng Shen wrote:
> There is timeout error during initialization:
> kernel: [ 14.167086] hid-multitouch 0003:2512:5003.0001:
> usb_submit_urb(ctrl) failed: -1
> kernel: [ 14.167135] hid-multitouch 0003:2512:5003.0001: timeout
> initializing reports
> kernel:
Hi Mathias,
On Tue, Feb 18, 2014 at 11:04:12AM -0800, David Cohen wrote:
> On Tue, Feb 18, 2014 at 12:47:41PM -0600, Felipe Balbi wrote:
> > On Tue, Feb 18, 2014 at 10:00:30AM -0800, David Cohen wrote:
> > > Hi Sarah,
> > >
> > > On Mon, Jan 06, 2014 at 07:02:19PM -0800, David Cohen wrote:
> > >
Sorry, I keep forgetting how bad gmail is in handling patches...
Here is a retransmit in plain-text format (really).
The patch is relative to linux-next.
The Maxim MAX3421E is a USB-over-SPI chip that can operate either in
peripheral or host mode. This driver adds support for the host-mode
only
On Fri, Mar 21, 2014 at 6:08 PM, Yufeng Shen wrote:
>
>
> On Fri, Mar 21, 2014 at 4:58 PM, Benjamin Tissoires
> wrote:
>>
>> On Fri, Mar 21, 2014 at 3:39 PM, Yufeng Shen wrote:
>> > There is timeout error during initialization:
>> > kernel: [ 14.167086] hid-multitouch 0003:2512:5003.0001:
>> >
2014-02-06 20:25 GMT+01:00 Ivaylo Dimitrov :
> From: Felipe Balbi
This patch, which is present in 3.14-rc4 as 30a70b026 ("usb: musb: fix
obex in g_nokia.ko causing kernel panic"), breaks USB gadget support
on my Pandaboard. Bisecting points to this commit, reverting it makes
USB gadget support w
Hi,
In my linux kernel USB 3.0 pendrive is not getting detected some time.For
the same usb port usb2.0 works perfectly.
Here is the error message i am getting
[ 161.808889] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 161.87] usb 2-1: New USB device found, idVendor=0951,
Felipe,
Thanks for your feedback, I'll take that into consideration.
On Fri, Mar 21, 2014 at 9:44 PM, Felipe Balbi wrote:
>> + max3421_hcd->spi_thread = kthread_run(max3421_spi_thread, hcd,
>> + "max3421_spi_thread");
>
> why do you need this kthrea
This revision incorporates virtually all of Felipe's feedback.
David Mosberger (1):
usb: host: Add HCD for MAX3421E chip.
drivers/usb/Makefile |1 +
drivers/usb/host/Kconfig | 11 +
drivers/usb/host/Makefile |1 +
drivers/usb/host/max3421-hcd.c | 1857 +++
39 matches
Mail list logo
