Hi Balbi,
> -Original Message-
> From: Neil Zhang
> Sent: 2012年7月25日 19:52
> To: Neil Zhang; ba...@ti.com; gre...@linuxfoundation.org
> Cc: Chao Xie; khoroshi...@ispras.ru; linux-usb@vger.kernel.org
> Subject: RE: [PATCH 0/7 v2] usb: gadget: mv_udc: bug fix and feature
> add
>
> Hi Balbi,
On Wednesday 01 August 2012 23:14:03 Lan Tianyu wrote:
> On 2012/8/1 22:48, Oliver Neukum wrote:
> > Strictly speaking, no. It is possible that there are devices that may
> > do something bad in case of a reset, but sometimes work well. In
> > such cases we should try.
> Do you mean some devices o
From: fangxiaozhi
1. This patch is based on the kernel of 3.5
2. In this patch, we add new micro for matching the series USB devices with
vendor ID and interface information.
3. In this patch, we add new declarations into option.c to support the new
interfaces of Huawei Data Card devices. And a
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Ido Shayevitz
> Sent: Wednesday, August 01, 2012 11:44 PM
> To: Anton Tikhomirov
> Cc: 'Ido Shayevitz'; 'Felipe Balbi'; paul.zimmer...@synopsys.com; linux-
> u...@vger.ker
Do not rely on any hints from gadget drivers and use DMA mode 1
whenever we expect more data than the endpoint's packet size and
have not yet received a short packet.
The last packet if short is always transferred using DMA mode 0.
This patch fixes USB throughput issues in mass storage mode for
h
(Adding in the USB mailing list)...
It seems that the clocks are registered with a .dev_id of "usbhs_omap" on
OMAP3xxx, but not OMAP4xxx, and that this causes the clk_get() in ehci-omap.c
to fail.
The following fixes the problem for me, but I've no idea if this is the correct
fix or not?
(sor
No functional change. Just replaced the call to platform_device_del and
platform_device_put with platform_device_unregister.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/musb/omap2430.c
uname
next-20120730
I used the new feature
echo "vid pid" >/sys/bus/usb/drivers/qmi_wwan/new_id
dmesg
[ 229.784142] usb 1-2: new high-speed USB device number 3 using ehci_hcd
[ 229.919579] usb 1-2: New USB device found, idVendor=19d2, idProduct=1017
[ 229.919594] usb 1-2: New USB device st
The network connection is working via wwan1 , at least with IPv4.
The LTE speed here with 8-16Mbit/s is limited by my contract, not the device.
At the moment I have problems with IPv6, but I think this is not a problem of
the device, more a problem of my apn, which may be only accessible via 3G.
On Thu, Aug 02, 2012 at 12:06:42PM +0530, Virupax Sadashivpetimath wrote:
> In case of USB bulk transfer, when himem page
> is received, the usb_sg_init function sets the
> urb transfer buffer to NULL. When such URB
> transfer is handled, kernel crashes in PIO mode.
> Handle this by mapping the hig
On Thursday 02 August 2012, Praveen Paneri wrote:
> Yes! I understand this problem and this is the reason these patches
> were sitting in my system for couple of weeks. In a discussion with
> Thomas an idea of using the existing regulator framework to
> enable/disable numerous PHYs came up. For ex
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, August 02, 2012 4:30 PM
> To: Virupax SADASHIVPETIMATH
> Cc: ba...@ti.com; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org;
> Praveena
> NADAHALLY
> Subject: Re: [PATCH] usb:musb:musb_host:
On 2012年8月2日 14:44:12, Oliver Neukum wrote:
On Wednesday 01 August 2012 23:14:03 Lan Tianyu wrote:
On 2012/8/1 22:48, Oliver Neukum wrote:
Strictly speaking, no. It is possible that there are devices that may
do something bad in case of a reset, but sometimes work well. In
such cases we shoul
From: Ajay Kumar Gupta
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 dm
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
This patch series uses 'phandle' based API devm_usb_get_phy_by_phandle() to
g
From: Ajay Kumar Gupta
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
Signed-off-by: Ravi Babu
---
arch/arm/boot/dts/am33xx.dtsi |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --gi
AM33xx has two PHY of same type used by each musb controller so
use phandle of phy nodes to get the phy pointer.
Signed-off-by: Ajay Kumar Gupta
Signed-off-by: Ravi Babu
---
.../devicetree/bindings/usb/am33xx-usb.txt |2 ++
drivers/usb/musb/musb_dsps.c |5 +
From: Ajay Kumar Gupta
Added device tree support for dsps musb glue driver and updated the
Documentation with device tree binding information.
Signed-off-by: Ajay Kumar Gupta
Signed-off-by: Ravi Babu
---
.../devicetree/bindings/usb/am33xx-usb.txt | 14 +
drivers/usb/musb/musb_ds
From: Ajay Kumar Gupta
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
Signed-off-by: Ravi Babu
---
arch/arm/boot/dts/am33xx.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/a
From: Ajay Kumar Gupta
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
Signed-off-by: Ravi Babu
---
arch/arm/boot/dts/am33xx.dtsi | 11 +++
1 files change
From: Ajay Kumar Gupta
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
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/
From: Ajay Kumar Gupta
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
Si
From: Ajay Kumar Gupta
Added musb_ida in musb_core.c to manage the multi core ids.
Signed-off-by: Ajay Kumar Gupta
Signed-off-by: Ravi Babu
---
drivers/usb/musb/am35x.c | 42 --
drivers/usb/musb/blackfin.c | 26 --
drive
From: Ajay Kumar Gupta
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
Signed-off-by: Ravi Babu
---
.../devicetree/bindings/usb/am33xx-usb.txt |3 +++
drive
From: Ajay Kumar Gupta
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 Gu
Hi Alan
>
> On Wed, 1 Aug 2012, Ravi Babu wrote:
>
> > When the scsi mass storage device is disconnected, the current urbs
> > queued to hcd driver must be cancelled, otherwise the
> current urbs are
> > pending at hcd driver and the active urb programmed at host
> controller
> > will nev
Hello,
looking at
http://sourceforge.net/apps/mediawiki/mbm/index.php?title=Main_Page#Supported_devices,
there are branded Ericsson devices from Dell and Toshiba.
The to-be-added vendor IDs are 0x413c for Dell and 0x0930 for Toshiba.
Please find attached a patch to add these vendor IDs.
Si
> -Original Message-
> From: Virupax SADASHIVPETIMATH
> Sent: Thursday, August 02, 2012 5:35 PM
> To: 'Greg KH'
> Cc: ba...@ti.com; linux-usb@vger.kernel.org; linux-ker...@vger.kernel.org;
> Praveena
> NADAHALLY
> Subject: RE: [PATCH] usb:musb:musb_host: Handle highmem in PIO mode
>
>
Hi,
Second test-drive for a new USB input driver for eBeam
devices.
Following Dmitry's advice, i've remove device specific infrastructure.
Currently, only the Luidia eBeam classic projection model is supported.
Patch 1 and 2 are here to let the ebeam driver be choose to handle
the device instea
Signed-off-by: Yann Cantin
---
drivers/hid/hid-ids.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 1dcb76f..b985059 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -271,6 +271,9 @@
#define USB_DEVICE_ID_DWAV_EGALA
Signed-off-by: Yann Cantin
---
drivers/hid/hid-core.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 60ea284..b1ed8ee 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1908,6 +1908,9 @@ static const struct hid_de
Signed-off-by: Yann Cantin
---
drivers/input/misc/Kconfig | 16 +
drivers/input/misc/Makefile |1 +
drivers/input/misc/ebeam.c | 760 +++
3 files changed, 777 insertions(+)
create mode 100644 drivers/input/misc/ebeam.c
diff --git a/drivers/input
On Thu, 2 Aug 2012, Yann Cantin wrote:
> Second test-drive for a new USB input driver for eBeam
> devices.
>
> Following Dmitry's advice, i've remove device specific infrastructure.
>
> Currently, only the Luidia eBeam classic projection model is supported.
>
> Patch 1 and 2 are here to let the
On Wed, 1 Aug 2012, Dan Rittersdorf wrote:
> Hello,
>
> I am working on a user-level USB peripheral device driver with a single
> pair of bulk in/out endpoints. It uses the gadgetfs() driver.
>
> I am initially running the usb.c example test program on gadgetfs, using
> the Windows USB 2.0 Co
On Wed, 1 Aug 2012 kuninori.morimoto...@renesas.com wrote:
> It is possible to power-on on platform setup level
> if Rafael and Magnus don't care this style.
> Then, I don't need this patch on ehci/ohci driver.
>
> 1) power-on on platform setup timing
> 2) use ehci/ohci driver
>
On Thu, 2 Aug 2012, Magnus Damm wrote:
> From my point of view this all depends on what the hardware supports.
> If the USB host controller hardware can be powered down (power domain
> off, clock off) when no USB hardware is connected, but still perform
> hotplug detection of a newly added device,
On Thu, 2 Aug 2012, Lan Tianyu wrote:
> > How about if we start with only the first policy rule: Ports that can
> > never have anything plugged in should be shut down automatically.
> So we should add a variable for each port to record whether the port
> has been ever attached with devices. When s
On Thu, 2 Aug 2012, Lan Tianyu wrote:
> A summary about what we should do now after such long discussion. If I
> lost something or miss something, please correct me.
>
> 1) Add "auto" option to each port's power policy sysfs attribute. When
> set to "auto", those ports which have never been atta
On Thu, 2 Aug 2012, Virupax Sadashivpetimath wrote:
> In case of USB bulk transfer, when himem page
> is received, the usb_sg_init function sets the
> urb transfer buffer to NULL. When such URB
> transfer is handled, kernel crashes in PIO mode.
> Handle this by mapping the highmem buffer in PIO mo
On Thu, 2 Aug 2012, B, Ravi wrote:
> > > --- a/drivers/usb/storage/usb.c
> > > +++ b/drivers/usb/storage/usb.c
> > > @@ -844,6 +844,8 @@ static void
> > quiesce_and_remove_host(struct us_data *us)
> > >*/
> > > scsi_lock(host);
> > > set_bit(US_FLIDX_DISCONNECTING, &us->dflags);
> > > + /
- Original Message -
> From: Joao Bonina
> To: Alan Stern
> Cc: "alsa-de...@alsa-project.org" ; linux-usb
> ; Daniel Mack
> Sent: Wednesday, 1 August 2012, 11:07
> Subject: Re: [alsa-devel] Alsa: USB Class 2 Audio soundcard device disappears
> suddenly
>
>
>
>> ___
On Thu, 2 Aug 2012, Lan Tianyu wrote:
> >> 3)Root-hub set port's DeviceRemovable flag where PortIsConnectable and
> >> UserVisible are clear.
> >
> > Set DeviceRemovable whenever UserVisible is set. Right now ehci-hcd
> > and uhci-hcd always set DeviceRemovable to 0.
>
> UserVisible is got from
On Thu, 2 Aug 2012, Joao Bonina wrote:
> Did the copying test and all went well there.
>
> Also did a usbmon session with the DAC disconnecting/reconnecting
> automatically. There was no EMI message in dmesg there, and I'm
> connecting the DAC through a USB hub.
>
> Analyzed the usbmon log wit
Hi
> On Thu, 2 Aug 2012, B, Ravi wrote:
>
> > > > --- a/drivers/usb/storage/usb.c
> > > > +++ b/drivers/usb/storage/usb.c
> > > > @@ -844,6 +844,8 @@ static void
> > > quiesce_and_remove_host(struct us_data *us)
> > > > */
> > > > scsi_lock(host);
> > > > set_bit(US_FLID
On Thu, 2 Aug 2012, B, Ravi wrote:
> Alan you may be correct. Let me explain, the issue occurs while
> unplugging the device during Tx transfer,
> 1) During Tx transfer, TX-DMA is programmed to transfer the data.
> 2) The TX-DMA completes the transfer and generates completion interrupt.
> 3) On
On Thu, 2 Aug 2012, Dan Rittersdorf wrote:
> > It looks like the lesson is not to have one thread accessing an
> > endpoint at the same time as another thread issues a CLEAR_HALT.
>
> Thank you -- that spawned a couple thoughts on a potential solution.
>
> And I appreciate you refraining from si
Hi Thomas,
> The network connection is working via wwan1 , at least with IPv4.
> The LTE speed here with 8-16Mbit/s is limited by my contract, not the device.
>
> At the moment I have problems with IPv6, but I think this is not a problem of
> the device, more a problem of my apn, which may be on
On Thu, 2 Aug 2012, Alan Stern wrote:
> On Thu, 2 Aug 2012, B, Ravi wrote:
>
> > Alan you may be correct. Let me explain, the issue occurs while
> > unplugging the device during Tx transfer,
> > 1) During Tx transfer, TX-DMA is programmed to transfer the data.
> > 2) The TX-DMA completes the tr
Am Donnerstag, 2. August 2012, 21:25:49 schrieben Sie:
> Hi Thomas,
>
> > At the moment I have problems with IPv6, but I think this is not a
> > problem of the device, more a problem of my apn, which may be only
> > accessible via 3G.
>
> if you are on Vodafone Germany LTE, then yes, it only gi
On Wed, 1 Aug 2012, Rafael J. Wysocki wrote:
> What I really thought about was to do _get_noresume(), then check if the
> device is active and if not, queue up a work item (or another delayed
> execution in process context) that will do pm_runtime_resume() and
> then access the hardware.
>
> Why
On Thursday, August 02, 2012, Alan Stern wrote:
> On Wed, 1 Aug 2012, Rafael J. Wysocki wrote:
>
> > What I really thought about was to do _get_noresume(), then check if the
> > device is active and if not, queue up a work item (or another delayed
> > execution in process context) that will do pm_
Hi Ravi,
On 02.08.2012 14:12, Ravi Babu wrote:
> This series of patches adds,
> a) Multi instances support in musb driver
> b) DT support for musb_dsps glue layer
> c) DT support for NOP transceiver
>
> AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
> This patch seri
Hi Sarah,
I have rewritten my code following your recommendations. Could you please
review it and give your comments? If everything is fine I'll proceed to
generate the patch and submit it.
The description of my patch is:
-
The following is formatted in line with the info here:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Kernel.org_Format
and sent as advised at the end of this bug report here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1032342
Thanks in advance for your time, I very much hope I
Hi
Thanks for the quick response.
> >
> > > Alan you may be correct. Let me explain, the issue occurs while
> > > unplugging the device during Tx transfer,
> > > 1) During Tx transfer, TX-DMA is programmed to transfer the data.
> > > 2) The TX-DMA completes the transfer and generates
> compl
Hi
>
> On 02.08.2012 14:12, Ravi Babu wrote:
> > This series of patches adds,
> > a) Multi instances support in musb driver
> > b) DT support for musb_dsps glue layer
> > c) DT support for NOP transceiver
> >
> > AM33xx and TI81xx has dual musb controller and has two usb
> PHY of same type.
> >
On Fri, 3 Aug 2012, B, Ravi wrote:
> > > What host controller driver are you using?
>
> It is mentor controller integrated with CPPI41-DMA
Then you're using the musb driver?
> > > Why doesn't the controller hardware detect that the device fails to
> > > send handshake packets and abort the tr
On Thu, 2 Aug 2012, Rafael J. Wysocki wrote:
> > I don't know about that -- the logic involved in doing the processing
> > within the resume callback isn't terribly complicated. At least, not
> > much more complicated than the logic involved in setting up a custom
> > work routine as you sugge
Hi Alan, Felipe, Greg
These are v2 of ehci/ohci-platform patches.
These are based on latest linus/master (and linux-next/mastere)
I tested these patches on R-Car H1 marzen board.
But I couldn't test suspend/resume.
So, I added [RFC] on this patch.
Please check these patches carefully
Kuninori M
On Fri, 3 Aug 2012, mat brown wrote:
> The following is formatted in line with the info here:
> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Kernel.org_Format
> and sent as advised at the end of this bug report here:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1032342
>
> T
This patch enables to call platform specific power callback function.
Signed-off-by: Kuninori Morimoto
---
drivers/usb/host/ehci-platform.c | 33 +
include/linux/usb/ehci_pdriver.h |2 ++
2 files changed, 31 insertions(+), 4 deletions(-)
diff --git a/driver
This patch enables to call platform specific power callback function.
Signed-off-by: Kuninori Morimoto
---
drivers/usb/host/ohci-platform.c | 29 ++---
include/linux/usb/ohci_pdriver.h |2 ++
2 files changed, 28 insertions(+), 3 deletions(-)
diff --git a/drivers/us
On Fri, Aug 3, 2012 at 3:32 AM, Alan Stern wrote:
>
> What mount options are used for the flash drive? In particular, does
> Ubuntu use the "sync" option?
>
> Also, do any error messages show up in the system log during the slow
> data transfers?
>
> Alan Stern
>
mount reports the following:
/d
On Fri, Aug 3, 2012 at 10:20 AM, Alan Stern wrote:
> On Thu, 2 Aug 2012, Rafael J. Wysocki wrote:
> Hmmm. You'd probably want a version that does a "get" at the same
> time. I suppose you would call func directly if the device was already
> resumed, without going through the workqueue?
Maybe i
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Friday, August 03, 2012 7:15 AM
> To: B, Ravi
> Cc: Matthew Dharm; Greg Kroah-Hartman;
> linux-usb@vger.kernel.org; usb-stor...@lists.one-eyed-alien.net
> Subject: RE: [PATCH] usb: storage: stop all curr
Hi,
kernel panic when called usb_control_msg(), like this:
usb_control_msg(serial->dev, usb_sndctrlpipe(serial->dev, 0),
XR_SET_REG, USB_DIR_OUT | USB_TYPE_VENDOR, value, regnum | (block <<
8), NULL, 0, 5000)
The kernel's version is 2.6.33_rc4, but I think it will happen in
lastest statable vers
Hi,
On Thu, Jul 5, 2012 at 2:12 PM, Ruslan Bilovol wrote:
> The original issue with powering on the PHY (and using
> 200 ms delay after this) is not related to internal
> processes in the PHY but is in the incorrect charger
> detection feature usage.
>
> Now when it is fixed, we can safely remove
Hi,
On Fri, Aug 03, 2012 at 11:19:36AM +0800, taylor Wang wrote:
> Hello,
> kernel panic when called usb_control_msg(), like this:
>usb_control_msg(serial->dev, usb_sndctrlpipe(serial->dev, 0),
> XR_SET_REG, USB_DIR_OUT | USB_TYPE_VENDOR, value, regnum | (block << 8),
> NULL, 0, 5000)
> The ke
68 matches
Mail list logo
