On Thursday 11 October 2012 20:39:18 Ming Lei wrote:
Hi,
This patch set introduces 3 helpers for handling usb read, write
and write_async command, and replaces the low level's implemention
with the generic ones.
This patchset is a cleanup and about 300 lines code can be saved.
Also,
Sorry for the delay, I have been distracted by a number of things.
On Monday 24 of September 2012 15:10:36 Sarah Sharp wrote:
On Tue, Sep 25, 2012 at 12:09:06AM +0200, Rafael J. Wysocki wrote:
On Monday, September 24, 2012, Alan Stern wrote:
On Mon, 24 Sep 2012, Rafael J. Wysocki wrote:
When setting usb port's acpi power resource, there will be some xhci hub
requests.
This will cause dead lock since xhci-lock has been held before setting acpi
power
resource in the xhci_hub_control(). The usb_acpi_power_manageable() function
might
fall into sleep so release xhci-lock before
Struct usb_hub_descriptor.ss.DeviceRemovable has been defined as __le16
and (__force__ __u16) doesn't need.
Signed-off-by: Lan Tianyu tianyu@intel.com
---
drivers/usb/host/xhci-hub.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/host/xhci-hub.c
On 10/12/2012 06:39 PM, Fengguang Wu wrote:
Hi Sebastian,
Hi Fengguang,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
merge-result-for-greg
head: 23953bde3e4d6aa8780dc054f6ad9882ac63f4f4
commit: 721e2e91945bc2520d57d795dfe1b502ecec567c
On AM3517, tx and rx interrupt are detected together with
the disconnect event. This generates a kernel panic in musb_interrupt,
because rx / tx are handled after disconnect.
This issue was seen on a Technexion's TAM3517 SOM. Unplugging a device,
tx / rx interrupts together with disconnect are
On Monday 15 October 2012 13:14:19 Ming Lei wrote:
If one storage interface exists in the device, memory allocation
with GFP_KERNEL during usb_device_reset() might trigger I/O transfer
on the storage interface itself and cause deadlock because the
'us-dev_mutex' is held in .pre_reset() and the
On Sunday 14 October 2012 00:29:24 Nicolas Boullis wrote:
From: Nicolas Boullis nboul...@debian.org
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
Signed-off-by: Nicolas Boullis nboul...@debian.org
Acked-by: Oliver Neukum
On Friday 12 October 2012 11:29:49 Alan Stern wrote:
On Fri, 12 Oct 2012, Oliver Neukum wrote:
First we have workqueues. bas-gigaset is a good example.
The driver kills a scheduled work in pre_reset(). If this is done
synchronously
the driver may need to wait for a memory allocation
Hi,
this is a series of fixes for the disconnection races in USB-audio.
A couple of new patches to improve and cover more points since the
previous patch set.
Takashi
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More
Fix races at PCM disconnection:
- while a PCM device is being opened or closed
- while the PCM state is being changed without lock in prepare,
hw_params, hw_free ops
Signed-off-by: Takashi Iwai ti...@suse.de
---
sound/core/pcm.c| 7 ++-
sound/core/pcm_native.c | 16
Replace mutex with rwsem for codec-shutdown protection so that
concurrent accesses are allowed.
Also add the protection to snd_usb_autosuspend() and
snd_usb_autoresume(), too.
Signed-off-by: Takashi Iwai ti...@suse.de
---
sound/usb/card.c | 12
sound/usb/mixer.c| 12
Similar like the previous commit, cover with chip-shutdown_rwsem
and chip-shutdown checks.
Signed-off-by: Takashi Iwai ti...@suse.de
---
sound/usb/mixer_quirks.c | 58 ++--
1 file changed, 51 insertions(+), 7 deletions(-)
diff --git
On Sat, 2012-10-13 at 17:33 +0200, Johan Hovold wrote:
Thanks for the patch Jarkko. Your solution is nice, but I think it could
implemented in a slightly better way.
For starters, the subdrivers really shouldn't be poking around in the
generic driver's implementation details unless really
On Mon, Oct 15, 2012 at 5:34 PM, Oliver Neukum oneu...@suse.de wrote:
I think limiting this to devices which have a storage device is not
productive. What if you are using iSCSI or nbd? In the long run
You mean other non-mass storage or non-uas usb interfaces may
be involved in iSCSI or nbd?
On Fri, Oct 12, 2012 at 07:24:33PM +0530, Vikas Sajjan wrote:
Hi kishon,
On 12 October 2012 16:27, kishon kis...@ti.com wrote:
Hi,
On Wednesday 10 October 2012 07:35 PM, Vikas C Sajjan wrote:
From: Vikas Sajjan vikas.saj...@linaro.org
Adding the suspend and resume funtionality
Hi,
On Wed, Oct 10, 2012 at 07:18:45PM -0700, Kuninori Morimoto wrote:
renesas_usbhs can't handle scatter/gather type DMA.
Thus, return -EINVAL is better than WARNING() on mod_gadget
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
Hi,
On Thu, Oct 11, 2012 at 07:02:07PM -0700, Kuninori Morimoto wrote:
1st pos of __usbhs_for_each_pipe() was wrong.
Each pipe were pipe0, pipe2, pipe3 ...
This patch modifies it.
patch looks correct but I'm sure you can do much better on this commit
log.
cheers
Signed-off-by: Kuninori
On Thu, Oct 11, 2012 at 09:49:38PM -0700, Kuninori Morimoto wrote:
When interrupt happened, renesas_usbhs driver gets irq status
by usbhs_status_get_each_irq(), and cleared all status by using 0.
But, this method is incorrect,
since extra interrupt might occur between them.
This patch cleared
On Sat, Oct 13, 2012 at 06:40:23PM +0530, Vikas Sajjan wrote:
Adding the suspend and resume funtionality to DWC3 core.
typo - functionality.
Also this is quite lame as a commit log. I'm sure you can do better than
this.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by:
On Sat, Oct 13, 2012 at 06:40:24PM +0530, Vikas Sajjan wrote:
Adding the suspend and resume functionality for the XHCI driver
please do better on your commit log.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by: Vikas C Sajjan vikas.saj...@linaro.org
CC: Doug Anderson
On Sat, Oct 13, 2012 at 06:40:23PM +0530, Vikas Sajjan wrote:
Adding the suspend and resume funtionality to DWC3 core.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by: Vikas C Sajjan vikas.saj...@linaro.org
CC: Doug Anderson diand...@chromium.org
---
Hi,
On Sat, Oct 13, 2012 at 06:40:25PM +0530, Vikas Sajjan wrote:
Adding the suspend and resume functionality to exynos dwc3 driver
better commit log.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Signed-off-by: Vikas C Sajjan vikas.saj...@linaro.org
CC: Doug Anderson
On Sat, Oct 13, 2012 at 07:20:18PM +0530, Vivek Gautam wrote:
We do usb_phy_init() while doing core_init() in probe,
so adding usb_phy_shutdown() when we do core_exit()
while removing the device.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
I believe this needs to be sent to stable
Hi,
On Mon, Oct 08, 2012 at 09:34:51AM -0700, Tony Lindgren wrote:
* Philippe De Swert philippedesw...@gmail.com [121004 10:00]:
This patch is based on the discussion of a previous patch to fix an issue
where the omap2430 musb driver is not working for N9/N950.
Moving all the interrupt
Hi,
On Wed, Oct 10, 2012 at 07:17:58PM -0700, Kuninori Morimoto wrote:
This patch enabled dma mapping, and used dma transfer handler
on mod_host
Signed-off-by: Kuninori Morimoto kuninori.morimoto...@renesas.com
---
Felipe
I sent some patches before, and I guess it will go to v3.8
Hi,
On Wed, Oct 10, 2012 at 10:06:03AM +0530, Virupax Sadashivpetimath wrote:
Flush queued urbs on receiving device disconnect
interrupt. This is required for successful disconnect
and successive enumeration of the device.
In a failure case khubd hangs on usb-storage thread
for completion.
On Monday 15 October 2012 20:06:36 Ming Lei wrote:
On Mon, Oct 15, 2012 at 5:34 PM, Oliver Neukum oneu...@suse.de wrote:
I think limiting this to devices which have a storage device is not
productive. What if you are using iSCSI or nbd? In the long run
You mean other non-mass storage or
Hi,
On Mon, Oct 08, 2012 at 02:53:49PM +0530, Kishon Vijay Abraham I wrote:
This patch series adds dt support to dwc3 core and fixes few minor
stuff in dwc3-omap glue to get dwc3 working.
While at that it also uses *of_platform* to create the child device
(dwc3-core) and fixes to use
This message is an debugging message. It's useful for finding protocol
details but it's not necessarily an error.
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
---
drivers/usb/gadget/lpc32xx_udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The STOTG04 is an replacement for ISP1301.
Most of the registers on STOTG04 are the same as on ISP1301, but the
register ISP1301_I2C_OTG_CONTROL_2 (address 0x10) doesn't exist on the
ST part.
This is a work around for this by using the interrupt source register that
should behave the same on
Hi,
On Mon, Oct 15, 2012 at 09:47:35AM -0300, Alexandre Pereira da Silva wrote:
The STOTG04 is an replacement for ISP1301.
Most of the registers on STOTG04 are the same as on ISP1301, but the
register ISP1301_I2C_OTG_CONTROL_2 (address 0x10) doesn't exist on the
ST part.
This is a work
On Mon, Oct 15, 2012 at 8:30 PM, Oliver Neukum oneu...@suse.de wrote:
All network devices?
Good point, but I am wondering if there are guys who would like to
bring up iSCSI over usb network dongle, which should be
very slow at least with high speed. For super speed device,
looks there are few
Hi Felipe,
On Mon, Oct 15, 2012 at 5:44 PM, Felipe Balbi ba...@ti.com wrote:
On Sat, Oct 13, 2012 at 07:20:18PM +0530, Vivek Gautam wrote:
We do usb_phy_init() while doing core_init() in probe,
so adding usb_phy_shutdown() when we do core_exit()
while removing the device.
Signed-off-by:
This patch series adds dt support to dwc3 core and fixes few minor
stuff in dwc3-omap glue to get dwc3 working.
While at that it also uses *of_platform* to create the child device
(dwc3-core) and fixes to use runtime API's to enable clock and write
to SYSCONFIG register.
Changes from v3:
*
Used device_for_each_child() to handle child device (dwc3 core) removal
during devexit of dwc3 omap.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/dwc3-omap.c
On Mon, Oct 15, 2012 at 06:56:13PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Mon, Oct 15, 2012 at 5:44 PM, Felipe Balbi ba...@ti.com wrote:
On Sat, Oct 13, 2012 at 07:20:18PM +0530, Vivek Gautam wrote:
We do usb_phy_init() while doing core_init() in probe,
so adding usb_phy_shutdown()
Used of_platform_populate() to populate dwc3 core platform_device
from device tree data. Since now the allocation of unique device id is
handled by of_*, removed the call to dwc3_get_device_id.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 50
Includes few minor fixes in dwc3-omap like populating the compatible
string in a correct way, extracting the utmi-mode property properly and
changing the index of get_irq since irq of core is removed from hwmod
entry.
Also updated the documentation with dwc3-omap device tree binding
information.
Before accessing any register, runtime API's should be invoked to enable
the clocks. runtime API's are added here to prevent abort during register
access.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 11 +++
1 file changed, 11 insertions(+)
Add an API in the omap glue layer to write to the mailbox register which
can be used by comparator driver(twl). To pass the detection of the attached
device (signified by VBUS, ID) to the dwc3 core, dwc3 glue has to write
to the mailbox regiter.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
The runtime API's takes care of setting the SYSCONFIG register with
appropriate values. Hence explicit writes to SYSCONFIG register is
removed.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 26 --
1 file changed, 26 deletions(-)
Added dwc3 support for dwc3 core and update the documentation with
device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/dwc3.txt | 23 +++
drivers/usb/dwc3/core.c| 14
On Fri, Oct 12, 2012 at 03:45:34PM +0530, Praveen Paneri wrote:
platform_set_drvdata() required for driver's remove function, so adding
it back.
From v6:
Added TODO for phy bindings with controller
Dropped platform_set_drvdata() from driver probe
This driver uses usb_phy interface to
Hi,
On Thu, Oct 11, 2012 at 06:34:34PM +0200, Constantine Shulyupin wrote:
From: Constantine Shulyupin co...@makelinux.com
Sets USB PHY clock source to 24 MHz clock.
Tested with OTG configuration, usb gadget g_zero on DM365 EVM connected to PC.
To active the patch need to call
On Tue, Oct 09, 2012 at 01:05:46PM -0400, Alan Stern wrote:
On Tue, 9 Oct 2012, Greg KH wrote:
Ugh, that simple patch has turned up more bugs in drivers than
anything I know of in recent history.
It would be a good idea for someone to audit all the serial drivers.
The basic idea is
+ Tomasz Figa,
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
On Mon, Oct 15, 2012 at 10:28 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Oct 12, 2012 at 03:45:34PM +0530, Praveen Paneri wrote:
platform_set_drvdata() required for driver's remove function, so adding
it back.
From v6:
Fix port-data memory leak by allocating and freeing port data in
port_probe/remove rather than in attach/release, and by introducing
serial private data to store the device type which is interface rather
than port specific.
Since commit 0998d0631001288 (device-core: Ensure drvdata = NULL when no
Fix port data memory leak by replacing port private data with serial
private data.
Since commit 0998d0631001288 (device-core: Ensure drvdata = NULL when no
driver is bound) the port private data is no longer freed at
release.
The private data is used to store the control interface number, but as
Hi,
On Mon, Oct 15, 2012 at 6:54 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Oct 15, 2012 at 06:56:13PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Mon, Oct 15, 2012 at 5:44 PM, Felipe Balbi ba...@ti.com wrote:
On Sat, Oct 13, 2012 at 07:20:18PM +0530, Vivek Gautam wrote:
We do
Fix missing and superfluous whitespace.
Fix misplaced brackets.
Fix indentation.
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/cp210x.c | 31 ++-
1 file changed, 14 insertions(+), 17 deletions(-)
diff --git a/drivers/usb/serial/cp210x.c
Remove driver version as it is the kernel version that matters.
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/cp210x.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
index 1264173..176d9d1
On Mon, 15 Oct 2012, Ming Lei wrote:
This patch applies the introduces tsk_memalloc_forbid_io() and
tsk_memalloc_allow_io() to force memory allocation with no I/O
during runtime_resume callback.
Cc: Alan Stern st...@rowland.harvard.edu
Cc: Oliver Neukum oneu...@suse.de
Cc: Rafael J.
On 10/15/2012 02:47 PM, Alexandre Pereira da Silva wrote:
The STOTG04 is an replacement for ISP1301.
Most of the registers on STOTG04 are the same as on ISP1301, but the
register ISP1301_I2C_OTG_CONTROL_2 (address 0x10) doesn't exist on the
ST part.
This is a work around for this by using
On 10/15/2012 02:47 PM, Alexandre Pereira da Silva wrote:
This message is an debugging message. It's useful for finding protocol
details but it's not necessarily an error.
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
Acked-by: Roland Stigge sti...@antcom.de
Was also
On Mon, 15 Oct 2012, Oliver Neukum wrote:
On Friday 12 October 2012 11:29:49 Alan Stern wrote:
On Fri, 12 Oct 2012, Oliver Neukum wrote:
First we have workqueues. bas-gigaset is a good example.
The driver kills a scheduled work in pre_reset(). If this is done
synchronously
the
On 10/15/2012 03:01 PM, Felipe Balbi wrote:
On Mon, Oct 15, 2012 at 09:47:35AM -0300, Alexandre Pereira da
Silva wrote:
The STOTG04 is an replacement for ISP1301.
Most of the registers on STOTG04 are the same as on ISP1301, but
the register ISP1301_I2C_OTG_CONTROL_2 (address 0x10) doesn't
On Mon, 15 Oct 2012, Ming Lei wrote:
This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of
'struct task_struct'), so that the flag can be set by one task
to avoid doing I/O inside memory allocation in the task's context.
The patch trys to solve one deadlock problem caused
On Mon, Oct 15, 2012 at 10:14 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 15 Oct 2012, Ming Lei wrote:
This patch applies the introduces tsk_memalloc_forbid_io() and
tsk_memalloc_allow_io() to force memory allocation with no I/O
during runtime_resume callback.
Cc: Alan Stern
On Mon, Oct 15, 2012 at 10:33 PM, Alan Stern st...@rowland.harvard.edu wrote:
Instead of allow/forbid, the API should be save/restore (like
local_irq_save and local_irq_restore). This makes nesting much easier.
Good point.
Also, do we really the p argument? This is not at all likely to be
Hi. I am using linux-3.6.2 kernel with gentoo patches and I have been
having problems with the usb3 enclosure made by Roseweil. If I boot
with the drive plugged in, in this kernel, I cannot really boot because
it spits out continuous error messages -- something about code -71 maybe
cannot
On Tue, 9 Oct 2012 13:00:23 -0400 (EDT), Alan Stern st...@rowland.harvard.edu
wrote :
On Tue, 9 Oct 2012, Anisse Astier wrote:
How about matching any BIOS from Lucid, regardless of the board name?
I was just being conservative. Lucid is a common english word, and you
never know how
On Mon, Oct 15, 2012 at 01:14:17PM +0800, Ming Lei wrote:
This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of
'struct task_struct'), so that the flag can be set by one task
to avoid doing I/O inside memory allocation in the task's context.
The patch trys to solve one
On Monday 15 October 2012 21:21:13 Ming Lei wrote:
On Mon, Oct 15, 2012 at 8:30 PM, Oliver Neukum oneu...@suse.de wrote:
All network devices?
Good point, but I am wondering if there are guys who would like to
bring up iSCSI over usb network dongle, which should be
LTE, UMTS. Those
Fix NULL-pointer dereference at release by replacing attach and release
with port_probe and port_remove.
Since commit 0998d0631001288 (device-core: Ensure drvdata = NULL when no
driver is bound) the port private data is NULL when release is called.
Compile-only tested.
Cc:
Fix port-data memory leak by replacing attach and release with
port_probe and port_remove.
Since commit 0998d0631001288 (device-core: Ensure drvdata = NULL when no
driver is bound) the port private data is no longer freed at release as
it is no longer accessible.
Note that the write waitqueue
Fix port-data memory leak by replacing attach and release with
port_probe and port_remove.
Since commit 0998d0631001288 (device-core: Ensure drvdata = NULL when no
driver is bound) the port private data is no longer freed at release as
it is no longer accessible.
Note that the write waitqueue
On Mon, Oct 15, 2012 at 09:49:20AM +0200, Sebastian Andrzej Siewior wrote:
On 10/12/2012 06:39 PM, Fengguang Wu wrote:
Hi Sebastian,
Hi Fengguang,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
merge-result-for-greg
head:
On Mon, Oct 15, 2012 at 09:21:13PM +0800, Ming Lei wrote:
On Mon, Oct 15, 2012 at 8:30 PM, Oliver Neukum oneu...@suse.de wrote:
All network devices?
Good point, but I am wondering if there are guys who would like to
bring up iSCSI over usb network dongle, which should be
very slow at
On Mon, Oct 15, 2012 at 08:06:36PM +0800, Ming Lei wrote:
On Mon, Oct 15, 2012 at 5:34 PM, Oliver Neukum oneu...@suse.de wrote:
I think limiting this to devices which have a storage device is not
productive. What if you are using iSCSI or nbd? In the long run
You mean other non-mass
From: Constantine Shulyupin co...@makelinux.com
Previous names of init and exit functions init and cleanup are
unconventional and are not friendly for source navigation with tags.
New names ccg_init and ccg_exit are conveninal and source navigation
friendly.
Signed-off-by: Constantine
On Mon, Oct 15, 2012 at 11:28:34AM +0530, ankit patel wrote:
Hi Sarah,
Hi Ankit, thanks for the bug report.
We have found some problems during inserting device. It shows the error
like
- [ 85.694152] xhci_hcd :01:00.0: Endpoint 0x84 not halted,
refusing to reset.
-
On Sat, Oct 13, 2012 at 03:27:00PM +0200, Sergio Callegari wrote:
Dear Sarah Sharp,
please take my apologize in advance if this message should have
been sent elsewhere rather than your email.
From the 'Reporting bugs' doc I got the feeling that bugs should be
reported to subsystem
Greetings,
I am having a problem with usbserial and ftdi_sio kernel loadable modules.
I am working on an embedded board using RHEL 6.0. The board has 2 FTDI
chips each with quad serial interface for a total of 8 serial ports.
In addition, we have a WiFi module that behaves as a USB to Serial
Hey Linux Usb Forum ,
Do you have any bugs or work that a Linux kernel
newbie can do?
Nick --
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Takashi,
Takashi Iwai a écrit :
At Fri, 12 Oct 2012 17:42:19 +0200,
Matthieu CASTET wrote:
Hi,
Takashi Iwai a écrit :
[Added Daniel and Clemens in the loop]
I don't think this is needed.
So... the below is a quick hack I did without testing at all.
Hopefully this can give some
Hi,
I have some severe issues with USB on a new system. This is
an Acer Aspire S5 (i7, Ivybridge) and the scanner can be mostly
classified as non working.
Symptoms:
1.) Start a scan application (e.g. simple-scan)
2.) Scan a page
3.) Exit the app
4.) Start a scan application (e.g. simple-scan)
On Mon, Oct 15, 2012 at 01:15:05PM -0400, Mostafa Kassem wrote:
Greetings,
I am having a problem with usbserial and ftdi_sio kernel loadable modules.
I am working on an embedded board using RHEL 6.0.
Wait right there. If you are using RHEL, you need to get support from
Red Hat for it,
On Mon, Oct 15, 2012 at 11:11:26AM -0700, Greg KH wrote:
On Mon, Oct 15, 2012 at 01:15:05PM -0400, Mostafa Kassem wrote:
Greetings,
I am having a problem with usbserial and ftdi_sio kernel loadable modules.
I am working on an embedded board using RHEL 6.0.
Wait right there. If you
On Mon, 15 Oct 2012, Holger Freyther wrote:
Hi,
I have some severe issues with USB on a new system. This is
an Acer Aspire S5 (i7, Ivybridge) and the scanner can be mostly
classified as non working.
Symptoms:
1.) Start a scan application (e.g. simple-scan)
2.) Scan a page
3.) Exit the
Alan Stern stern@... writes:
What is the bugzilla report number?
it is #48801.
It's notable that the pcap file does not show any data being sent from
the scanner to the computer, only from the computer to the scanner.
Did I use usbmom/wireshark incorrectly?
The necessary support
Hi,
On Mon, Oct 15, 2012 at 09:29:14AM -0700, Greg KH wrote:
On Mon, Oct 15, 2012 at 09:49:20AM +0200, Sebastian Andrzej Siewior wrote:
On 10/12/2012 06:39 PM, Fengguang Wu wrote:
Hi Sebastian,
Hi Fengguang,
FYI, kernel build failed on
tree:
hi,
On Mon, Oct 15, 2012 at 12:16:36PM -0600, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
Almost nothing from this file is used, and the file will hopefully be
deleted soon. Copy the tiny portions that are used directly into
tegra_usb_phy.c. I believe that Venu Byravarasu
On Sat, Oct 13, 2012 at 12:18:57PM -0400, Alan Stern wrote:
On Fri, 12 Oct 2012, Yuliya T wrote:
Hi Alan,
Thank you for the suggestion. We independently ended up with the same
workaround, but still weren't happy with it. The problem is we don't
want to relinquish access to the
Holger Freyther holger@... writes:
Debian unstable switched to libusbx but kept the package name at
libusb. I have tested this with version 1.0.12.Okay, I see that there
has been some usb 3.0 changes in 1.0.13 and 1.0.14 and I am going to
test again.
I have tested with 38e6eb86b2 (two
On Mon, Oct 15, 2012 at 2:18 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 15, 2012 at 11:11:26AM -0700, Greg KH wrote:
On Mon, Oct 15, 2012 at 01:15:05PM -0400, Mostafa Kassem wrote:
Greetings,
I am having a problem with usbserial and ftdi_sio kernel loadable modules.
I am
On Mon, 15 Oct 2012, Holger Freyther wrote:
Holger Freyther holger@... writes:
Debian unstable switched to libusbx but kept the package name at
libusb. I have tested this with version 1.0.12.Okay, I see that there
has been some usb 3.0 changes in 1.0.13 and 1.0.14 and I am going to
On Mon, 15 Oct 2012, Sarah Sharp wrote:
I double checked, and calling usb_set_interface for the same alternate
setting that is currently installed will cause the xHCI driver to drop
and re-add the current endpoints. This should cause the toggle to be
reset for the endpoints.
I suppose the
Hi Alan,
I am seeing an odd panic with uhci when a 160 cpu box panics and starts
running a kdump kernel (which is the same exact image as the boot kernel)
for our RHEL-6 (2.6.32) kernel. Now I understand 2.6.32 is not something
upstream supports.
However, my question is what is expected to
On 10/15/2012 01:22 PM, Felipe Balbi wrote:
hi,
On Mon, Oct 15, 2012 at 12:16:36PM -0600, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
Almost nothing from this file is used, and the file will
hopefully be deleted soon. Copy the tiny portions that are used
directly into
On Mon, 15 Oct 2012, Don Zickus wrote:
Hi Alan,
I am seeing an odd panic with uhci when a 160 cpu box panics and starts
running a kdump kernel (which is the same exact image as the boot kernel)
for our RHEL-6 (2.6.32) kernel. Now I understand 2.6.32 is not something
upstream supports.
Mostafa Kassem wrote:
the Wifi module is this one from connectone:
http://www.connectone.com/?page_id=233
This may be the dumbest USB wifi module I have seen.
Have you already developed a software stack which depends on the
proprietary vendor protocol that they call AT+i?
If no, I would
From: Nicolas Boullis nboul...@debian.org
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
Signed-off-by: Nicolas Boullis nboul...@debian.org
Acked-by: Oliver Neukum oneu...@suse.de
---
diff --git a/drivers/usb/class/cdc-acm.c
On Mon, Oct 15, 2012 at 11:47:23PM +0200, Peter Stuge wrote:
Mostafa Kassem wrote:
the Wifi module is this one from connectone:
http://www.connectone.com/?page_id=233
This may be the dumbest USB wifi module I have seen.
Have you already developed a software stack which depends on the
Greg KH wrote:
But, if Mostafa is stuck at RHEL 6, there's nothing that we can do
here to help out at all, sorry.
Maybe he can help test a driver on an up-to-date kernel.org release,
and then perhaps he can ask RH to backport the driver. It should also
not be very much effort.
Mostafa, can
On Tue, Oct 16, 2012 at 1:09 AM, Nick Krause nickkra...@sympatico.ca wrote:
Hey Linux Usb Forum ,
Do you have any bugs or work that a Linux kernel
newbie can do?
Instead of the linux kernel USB subsystem, are you interested
in improving the user space library libusb (or the libusbx fork)?
The possibility of removing retry and cancelation came up a few times
plumbers this year. I finally gave it a try.
Removing retry is a good iea. It's of little value because retry
happens in a kernel thread, not in the submitter's task.
I'm ambivalent about removing cancelation. The code is
Signed-off-by: Zach Brown z...@redhat.com
---
include/linux/aio.h | 24
1 file changed, 24 deletions(-)
diff --git a/include/linux/aio.h b/include/linux/aio.h
index 31ff6db..b46a09f 100644
--- a/include/linux/aio.h
+++ b/include/linux/aio.h
@@ -9,44 +9,22 @@
#include
use_mm() is used in more places than just aio. There's no need to
mention callers when describing the function.
Signed-off-by: Zach Brown z...@redhat.com
---
mm/mmu_context.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/mm/mmu_context.c b/mm/mmu_context.c
index 3dcfaf4..8a8cd02 100644
This removes the only in-tree user of aio retry and cancellation. This
will let us remove code from the aio core.
Removing retry is relatively easy as the USB gadget wasn't using it to
retry IOs at all. It always fully submitted the IO in the context of
the initial io_submit() call. It only
1 - 100 of 110 matches
Mail list logo
