Hi, list.
I have a problem with usbip and etoken. Matt Mooney didn't reply me.
Greg Kroah-Hartman seems to be too busy. So, i doesn't know who can
help me with my problem. May be anybody know what the cause of the problem?
I have a usb etoken that doesn't want to work with usbip from
On Wednesday 18 July 2012 15:07:14 Sarah Sharp wrote:
On Wed, Jul 18, 2012 at 09:03:59PM +0200, Oliver Neukum wrote:
No, now that I think about it an attribute for the drivers is necessary.
Like drivers have supports_autosuspend they also should have
supports_power_off. In addition it is
On 2012年07月19日 14:37, Oliver Neukum wrote:
On Wednesday 18 July 2012 15:07:14 Sarah Sharp wrote:
On Wed, Jul 18, 2012 at 09:03:59PM +0200, Oliver Neukum wrote:
No, now that I think about it an attribute for the drivers is necessary.
Like drivers have supports_autosuspend they also should
This is to reduce the overhead of dma programming for zero byte
transmit as same can be done using pio mode.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
drivers/usb/musb/musb_host.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git
musb-gadget_driver is not getting reset to NULL after the gadget
driver is removed.
Fixing the same by resetting the musb-gadget_driver to NULL when
gadget driver is removed.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
This set of four patches are musb bugfix and created against
On Thu, Jul 19, 2012 at 01:31:07AM +0200, Michael Grzeschik wrote:
This patch removes the limitation of having only one
instance of the ci13xxx-imx. Each instance of the ci13xxx-imx
could have different flags to be configured with, so we also
move this settings to the devicetree properties.
On 2012年07月19日 14:37, Oliver Neukum wrote:
On Wednesday 18 July 2012 15:07:14 Sarah Sharp wrote:
On Wed, Jul 18, 2012 at 09:03:59PM +0200, Oliver Neukum wrote:
No, now that I think about it an attribute for the drivers is necessary.
Like drivers have supports_autosuspend they also should
Hi,
On Thu, Jul 19, 2012 at 11:11 AM, Ajay Kumar Gupta ajay.gu...@ti.com wrote:
Currently we have one single nop transceiver support as same is
defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
This need to be changed to support multiple otg controller each
using nop
Hi,
On Thu, Jul 19, 2012 at 11:11 AM, Ajay Kumar Gupta ajay.gu...@ti.com wrote:
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
Hi,
Currently we have one single nop transceiver support as same is
defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
This need to be changed to support multiple otg controller each
using nop transceiver on a platform such as am335x.
Signed-off-by: Ajay Kumar Gupta
On Thu, Jul 12, 2012 at 12:11 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Wed, Jul 11, 2012 at 7:53 PM, Kevin Hilman khil...@ti.com wrote:
Munegowda, Keshava keshava_mgo...@ti.com writes:
On Wed, Jul 11, 2012 at 3:59 PM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Keshava, Kevin,
Hi,
On Thu, Jun 21, 2012 at 07:12:12PM +0530, Keshava Munegowda wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails in beagle XM
causeing NFS not functional. This affects the core
On Thursday 19 July 2012 15:42:37 Lan Tianyu wrote:
On 2012年07月19日 14:37, Oliver Neukum wrote:
But this leaves me with a question. Has anybody ever measured the additional
power savings compared to a suspended state for devices? Or are you doing
this only as a prelude to become able to
Hi,
Here's the fourth version of the Logitech UVC devices RESET_RESUME quirk
patches. Compared to v3, the usb_detect_interface_quirks() has been moved to
usb_enumerate_device().
Laurent Pinchart (2):
usb: Add quirk detection based on interface information
usb: Add USB_QUIRK_RESET_RESUME for
On Thu, Jul 19, 2012 at 5:33 PM, Oliver Neukum oneu...@suse.de wrote:
On Thursday 19 July 2012 16:21:38 Lan Tianyu wrote:
On 2012年07月19日 14:37, Oliver Neukum wrote:
Unloading the driver is a user space issue.
But you are right there is a missing case
hi all:
I have a question About
Added device tree data for usbss on am33xx. There are two musb controllers
on am33xx platform so have port0_mode and port1_mode additional data.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 11 +++
1 files changed, 11 insertions(+), 0
AM33xx has two musb controller and they have one NOP PHY each.
Added the device tree data for NOP PHY.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
AM335x and TI81xx platform has dual musb controller so updating the
musb_dspc.c to support the same.
Changes:
- Moved otg_workaround timer to glue structure
- Moved static local variable last_timer to glue structure
- PHY on/off related cleanups
Signed-off-by: Ajay Kumar
As NOP device node is now added in am33xx tree so remove the call
which creates the NOP platform_device.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
drivers/usb/musb/musb_dsps.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c
Added NOP PHY phandle to usbss device node as same will be used
to get the phy from otg framework.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
.../devicetree/bindings/usb/am33xx-usb.txt |3 +++
drivers/usb/otg/nop-usb-xceiv.c
Moved global variable musb_debugfs_root and static variable
old_state to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable orig_dma_mask and filled the
dev-dma_mask with parent device's dma_mask.
Signed-off-by: Ajay
On Thu, Jul 19, 2012 at 3:50 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Thu, Jun 21, 2012 at 07:12:12PM +0530, Keshava Munegowda wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails
Hi Wolfram,
On Thu, Jul 19, 2012 at 10:28:56AM +0200, Wolfram Sang wrote:
On Thu, Jul 19, 2012 at 01:31:07AM +0200, Michael Grzeschik wrote:
This patch removes the limitation of having only one
instance of the ci13xxx-imx. Each instance of the ci13xxx-imx
could have different flags to be
Hi,
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
drivers/usb/musb/omap2430.c| 55
2 files changed, 88 insertions(+), 1 deletions(-)
diff --git
On Wed, Jul 18, 2012 at 11:56 AM, Sebastian Andrzej Siewior
sebast...@breakpoint.cc wrote:
On Mon, Jul 16, 2012 at 02:50:29PM +0200, Fabio Porcedda wrote:
PROBLEM:
1.
usb: gadget: at91_udc: kernel oops regression when connecting the usb cable
2.
Every time i connect the usb cable the kernel
Resend because sent to maillist failed.
2012/7/19 Oliver Neukum oneu...@suse.de
On Thursday 19 July 2012 16:21:38 Lan Tianyu wrote:
On 2012年07月19日 14:37, Oliver Neukum wrote:
Unloading the driver is a user space issue.
But you are right there is a missing case
hi all:
I have a
On Wed, 18 Jul 2012, Oliver Neukum wrote:
On Wednesday 18 July 2012 12:40:38 Alan Stern wrote:
Oliver, you seem to be arguing both sides of this discussion. You
But there are more than two sides in this discussion.
point out the the power-off operation is too dangerous in general
Hi,
On Thu, Jul 19, 2012 at 6:51 PM, Gupta, Ajay Kumar ajay.gu...@ti.com wrote:
Hi,
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 -
drivers/usb/musb/omap2430.c| 55
On 07/19/2012 03:22 PM, Gupta, Ajay Kumar wrote:
There is no need to call read_fifo for zero byte length.
The same as there's no need to write, and not only here?
Yes, it applies to write also but seems write is taken care
for zero byte length.
Frankly speaking, I don't see it. And
On Thu, 19 Jul 2012, loody wrote:
You didn't look at usb_serial_probe. At the end of that function there
I found what you mentioned.
for (i = 0; i num_ports; ++i) {
retval = device_add(port-dev);
...
Yes, that's it.
is a loop which
On Thu, 19 Jul 2012, Laurent Pinchart wrote:
Hi,
Here's the fourth version of the Logitech UVC devices RESET_RESUME quirk
patches. Compared to v3, the usb_detect_interface_quirks() has been moved to
usb_enumerate_device().
Laurent Pinchart (2):
usb: Add quirk detection based on
On Thu, 19 Jul 2012, Andreas Mohr wrote:
Hi,
Yesterday I was surprised to see that with *another* external USB disk
happening to be connected before boot,
the system booted with root partition device sdb1 assigned rather than sda1.
Not thinking much, I then proceeded putting the system
On Thu, 19 Jul 2012, Felipe Balbi wrote:
Hi,
On Thu, Jun 21, 2012 at 07:12:12PM +0530, Keshava Munegowda wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails in beagle XM
Hello Alan, John,
I had this question from the embedded perspective. printk on occasions
seems to have some overhead which actually dilutes the issue occurrence
frequency. So, just wanted to know if this was not included by choice.
Many Thanks,
~Bala
On 07/19/2012 12:12 AM, Alan Stern
Hi,
On Thu, Jul 19, 2012 at 11:11:50AM -0400, Alan Stern wrote:
On Thu, 19 Jul 2012, Andreas Mohr wrote:
Hi,
Yesterday I was surprised to see that with *another* external USB disk
happening to be connected before boot,
the system booted with root partition device sdb1 assigned
On Thu, Jul 19, 2012 at 10:00:12PM +0530, Balakumar wrote:
Hello Alan, John,
I had this question from the embedded perspective. printk on
occasions seems to have some overhead which actually dilutes the
issue occurrence frequency. So, just wanted to know if this was not
included by choice.
On Thu, 19 Jul 2012, Andreas Mohr wrote:
Hi,
On Thu, Jul 19, 2012 at 11:11:50AM -0400, Alan Stern wrote:
On Thu, 19 Jul 2012, Andreas Mohr wrote:
Hi,
Yesterday I was surprised to see that with *another* external USB disk
happening to be connected before boot,
the system
Hi,
I am playing with some devices and seems to me that I stuck with
a driver limitation. I connected usb-to-rs323/485 converter
that uses ftdi_sio and usbserial modules and it works. After that
I tried to use a 3g modem and it works passing vendor and product
parameters to the usbserial
Jiri:
This patch series fixes several major and minor bugs in the usbhid
driver related to suspend and resume, and especially autosuspend.
I don't think any of the problems are terribly severe, although some of
them prevent autosuspend from working properly, so I haven't marked the
patches for
This patch (as1592) fixes an obscure problem in the usbhid driver.
Under some circumstances, a control or interrupt-OUT URB can be
submitted twice. This will happen if the first submission fails; the
queue pointers aren't updated, so the next time the queue is restarted
the same URB will be
This patch (as1593) fixes some logic errors in the usbhid driver
relating to runtime PM. The driver does not balance its calls to
usb_autopm_get_interface_async() and usb_autopm_put_interface_async().
For example, when the control queue is restarted the driver does a
_get. But the resume won't
This patch (as1594) simplifies the usbhid driver by inlining a couple
of routines. As a result of an earlier patch, irq_out_pump_restart()
and ctrl_pump_restart() are each used in only one place. Since they
don't really do what their names say, and since they each involve only
about two lines of
This patch (as1595) improves the usbhid driver by using the
HID_SUSPENDED bitflag to indicate that the device is suspended rather
than using HID_REPORTED_IDLE, which the patch removes.
Since HID_SUSPENDED was not being used for anything, and since the
name HID_REPORTED_IDLE doesn't convey much
This patch (as1596) improves the queue-restart logic in usbhid by
checking to see if the device is suspended or a reset is about to
occur. There's no point submitting an URB if either of those is
true.
Signed-off-by: Alan Stern st...@rowland.harvard.edu
CC: Oliver Neukum oli...@neukum.org
---
This patch (as1597) fixes some of the error paths in usbhid's suspend
routine. The driver was not careful to restart everything that might
have been stopped, in cases where a suspend failed.
For example, once the HID_SUSPENDED flag is set, an output report
submission would not restart the
On Thursday 19 July 2012 18:58:38 Ming Lei wrote:
On Thu, Jul 19, 2012 at 5:33 PM, Oliver Neukum oneu...@suse.de wrote:
Yes. That's how reset_resume() works.
If reset_resume flag is set, usbcore will try to reset the device first
during resume, and no disconnect will be involved if reset
On Thursday 19 July 2012 10:42:23 Alan Stern wrote:
1) remote wakeup is requested
2) user space has blocked it via the new sysfs attribute
3) USB_QUIRK_RESET_MORPHS is set
The same is true for external ports if they are marked as
non-removable. For example, consider a compound
Hi,
Thanks for explanation on how things work.
The problem is if I don't pass the vendor and prodId the 3g modem is
detect as an USB mass storage. Even after using usb_modeswitch
usb_modeswitch -default-vendor 0x19d2 -default-product 0×2000
-target-vendor 0x19d2 -target-product 0×0031
On Thu, Jul 19, 2012 at 01:20:14PM +0300, Felipe Balbi wrote:
Hi,
On Thu, Jun 21, 2012 at 07:12:12PM +0530, Keshava Munegowda wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails
On Wed, Jul 18, 2012 at 10:53:09AM +0200, Claudio Scordino wrote:
Il 06/07/2012 19:41, Greg KH ha scritto:
On Wed, Jun 27, 2012 at 06:01:39PM +0200, Claudio Scordino wrote:
Hi Olav,
please find below a patch for the isp1362-hcd.c driver to always
save the message in case of underrun.
On Fri, Jul 20, 2012 at 3:37 AM, Oliver Neukum oli...@neukum.org wrote:
We cannot do this as the device state is specific to a driver. And the driver
must have an interface to be bound to. That is why we use reset_resume()
instead of resume(). resume() means that the device must be brought up
Oh. I recheck find these device will use ordinary resume rather than
reset_resume().
I remeber you said userspace should set USB_QUIRK_RESET_MORPHS for those
kind devices. After reset, they will morph. So reset_resume doesn't
work for them.
Ordinary resume almost just calls
Hi,
On 07/19/2012 03:22 PM, Gupta, Ajay Kumar wrote:
There is no need to call read_fifo for zero byte length.
The same as there's no need to write, and not only here?
Yes, it applies to write also but seems write is taken care
for zero byte length.
Frankly speaking, I
This is to reduce the overhead of dma programming for zero byte
transmit as same can be done using pio mode.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
drivers/usb/musb/musb_gadget.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
This is to reduce the overhead of dma programming for zero byte
transmit as same can be done using pio mode.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
drivers/usb/musb/musb_host.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git
musb-gadget_driver is not getting reset to NULL after the gadget
driver is removed.
Fixing the same by resetting the musb-gadget_driver to NULL when
gadget driver is removed.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
Changes from v1:
- Fixed Sergei's commend on [PATCH 4/4]
Added a check in musb_{read | write}_fifo for zero byte length.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
drivers/usb/musb/musb_core.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/omap_phy_internal.c | 138
Add twl6030-usb data node in twl6030 device tree file
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4-sdp.dts |4
arch/arm/boot/dts/twl6030.dtsi|6 ++
3 files changed, 14 insertions(+)
diff
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/usb/twl-usb.txt| 22 +++
drivers/usb/otg/twl6030-usb.c | 39
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030,
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
Add omap-usb2 data node in omap4 device tree file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 29c6243..15f1890 100644
---
Add device tree support for twl4030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/usb/twl-usb.txt| 19 ++
drivers/usb/otg/twl4030-usb.c |
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 +++-
drivers/usb/musb/omap2430.c|
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
Add twl4030-usb data node in twl4030 device tree file.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index
70 matches
Mail list logo
