Hi,
On Thu, Jun 20, 2013 at 8:16 PM, Felipe Balbi wrote:
>
> Hi,
>
> On Thu, Jun 20, 2013 at 01:53:13PM +, Yuan-Hsin Chen wrote:
> > Because fotg210-udc is configured as a non-hotpluggable device,
> > that makes sense to use module_platform_driver_probe() instead of
> > module_platform_drive
On Fri, Jun 21, 2013 at 12:46 PM, Ming Lei wrote:
> On Fri, Jun 21, 2013 at 9:12 AM, Ming Lei wrote:
>> On Fri, Jun 21, 2013 at 12:52 AM, Alan Stern
>> wrote:
>>> On Thu, 20 Jun 2013, Ming Lei wrote:
>>>
On Thu, Jun 20, 2013 at 10:59 PM, Alan Stern
wrote:
>
> By the way, d
On Fri, Jun 21, 2013 at 9:12 AM, Ming Lei wrote:
> On Fri, Jun 21, 2013 at 12:52 AM, Alan Stern
> wrote:
>> On Thu, 20 Jun 2013, Ming Lei wrote:
>>
>>> On Thu, Jun 20, 2013 at 10:59 PM, Alan Stern
>>> wrote:
>>> >
>>> > By the way, did you consider the race that Oliver pointed out? When an
>>
correct for irq. irq number is get by gludriver, while irq is
requested by EHCO HCD.
On Fri, Jun 21, 2013 at 9:07 AM, Chao Xie wrote:
> On Fri, Jun 21, 2013 at 1:25 AM, Alan Stern wrote:
>> On Thu, 20 Jun 2013, Felipe Balbi wrote:
>>
>>> > In fact, the PHY setting and handling is related to plat
On Fri, Jun 21, 2013 at 12:52 AM, Alan Stern wrote:
> On Thu, 20 Jun 2013, Ming Lei wrote:
>
>> On Thu, Jun 20, 2013 at 10:59 PM, Alan Stern
>> wrote:
>> >
>> > By the way, did you consider the race that Oliver pointed out? When an
>> > HCD is removed, all the outstanding URBs for all devices o
On Fri, Jun 21, 2013 at 1:25 AM, Alan Stern wrote:
> On Thu, 20 Jun 2013, Felipe Balbi wrote:
>
>> > In fact, the PHY setting and handling is related to platform or SOC,
>> > and for different SOC they can
>> > have same EHCI HCD but they PHY handling can be different.
>> > Omap'a case is the exam
These devices are all Gobi1K devices (according to the Windows INF
files) and should be handled by qcserial instead of option. Their
network port is handled by qmi_wwan.
Signed-off-by: Dan Williams
---
drivers/usb/serial/option.c | 4
drivers/usb/serial/qcserial.c | 8 +++-
2 files c
On Thu, Jun 20, 2013 at 03:16:42PM -0500, Dan Williams wrote:
> On Thu, 2013-06-20 at 13:27 -0500, Dan Williams wrote:
> > The USB-1000 is a Gobi1K device in USB dongle form, requires firmware
> > download via gobi_loader, and has the Gobi1K descriptor layout. It
> > also supports QMI like any oth
On Thu, 2013-06-20 at 13:27 -0500, Dan Williams wrote:
> The USB-1000 is a Gobi1K device in USB dongle form, requires firmware
> download via gobi_loader, and has the Gobi1K descriptor layout. It
> also supports QMI like any other Gobi1K device, but option grabs
> all the USB interfaces and preven
On Thu, 20 Jun 2013, Manjunath Goudar wrote:
> Suspend scenario in case of ohci bus glue was not properly handled as
> it was not suspending generic part of ohci controller. Calling
> explicitly the ohci_suspend()routine will ensure proper handling
> of suspend scenario.
>
> V2:
> -Incase ohci_s
The USB-1000 is a Gobi1K device in USB dongle form, requires firmware
download via gobi_loader, and has the Gobi1K descriptor layout. It
also supports QMI like any other Gobi1K device, but option grabs
all the USB interfaces and prevents qmi_wwan and qc_serial from
handling the device.
Signed-off
On Thu, 20 Jun 2013, Alan Stern wrote:
> On Thu, 20 Jun 2013, Greg KH wrote:
>
> > > I'm not exactly sure what the implications of combining the modules are
> > > so
> > > I don't know if that would fix it or not.
> > >
> > > It is true that an HWA will always have an associated radio contro
On Thu, 20 Jun 2013, Greg KH wrote:
> > I'm not exactly sure what the implications of combining the modules are so
> > I don't know if that would fix it or not.
> >
> > It is true that an HWA will always have an associated radio controller
> > interface but the inverse is not always true. A UW
On Thu, 20 Jun 2013, Mathias Nyman wrote:
> Make the Linux xHCI driver automatically try to switchover the EHCI ports to
> xHCI when an Intel xHCI host is detected, and it also finds an Intel EHCI
> host.
>
> This means we will no longer have to add Intel xHCI hosts to a quirks list
> when
> th
On Thu, 20 Jun 2013, Roger Quadros wrote:
> > runtime_resume(dev)
> > {
> > ...
> >
> > if (omap->flags & OMAP_EHCI_IRQ_PENDING) {
> > process_pending_irqs(omap);
>
> OK, thanks.
>
> But I'm not sure if the generic ehci_irq handler is able to
> run in a process context. May
On Wed, 19 Jun 2013, Greg KH wrote:
> On Wed, Jun 19, 2013 at 03:33:51PM -0500, Thomas Pugliese wrote:
> > Hi,
> > I am attempting to debug a problem where the hwa_hc module occasionally
> > fails to start correctly when an HWA device is plugged in. An HWA device
> > consists of two USB inte
On Thu, 20 Jun 2013, Felipe Balbi wrote:
> > In fact, the PHY setting and handling is related to platform or SOC,
> > and for different SOC they can
> > have same EHCI HCD but they PHY handling can be different.
> > Omap'a case is the example, and i think some other vendors may have
> > silimar ca
On Thu, 20 Jun 2013, Roger Quadros wrote:
> >> As the omap-ehci controller driver needs to do some additional work to put
> >> itself into suspend/resume and make sure it is resumed to process an
> >> interrupt,
> >> we need to be able to override irq, bus_suspend, and bus_resume handlers.
> >>
On Thu, 20 Jun 2013, victor yeo wrote:
> The problem is in UDC driver. i made the change, it is ok now.
Good. I noticed that the usb_ep_set_wedge routine still isn't working
right. You might try to fix that.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" i
On Thu, Jun 20, 2013 at 12:05:21PM -0500, Thomas Pugliese wrote:
>
>
> On Wed, 19 Jun 2013, Greg KH wrote:
>
> > On Wed, Jun 19, 2013 at 03:33:51PM -0500, Thomas Pugliese wrote:
> > > Hi,
> > > I am attempting to debug a problem where the hwa_hc module occasionally
> > > fails to start correct
On Thu, 20 Jun 2013, Manjunath Goudar wrote:
> > > @@ -686,7 +631,7 @@ ohci_hcd_at91_drv_suspend(struct platform_device
> > *pdev, pm_message_t mesg)
> > >* REVISIT: some boards will be able to turn VBUS off...
> > >*/
> > > if (at91_suspend_entering_slow_clock()) {
> > > -
On Thu, 20 Jun 2013, Ming Lei wrote:
> On Thu, Jun 20, 2013 at 10:59 PM, Alan Stern
> wrote:
> >
> > By the way, did you consider the race that Oliver pointed out? When an
> > HCD is removed, all the outstanding URBs for all devices on its bus get
> > cancelled. The core waits until the urb_li
On Thu, Jun 20, 2013 at 10:59 PM, Alan Stern wrote:
>
> By the way, did you consider the race that Oliver pointed out? When an
> HCD is removed, all the outstanding URBs for all devices on its bus get
> cancelled. The core waits until the urb_list for each endpoint is
> empty.
This should be en
On Thu, 20 Jun 2013, Ming Lei wrote:
> >> Looks not always synchronous, control transfer is synchronous, and
> >> interrupt transfer is still asynchronous. No drivers(hub, usbfs) depend
> >> on that, and IMO, treating root hub same as hub will simplify HCD core,
> >> and finally we can remove all
Make the Linux xHCI driver automatically try to switchover the EHCI ports to
xHCI when an Intel xHCI host is detected, and it also finds an Intel EHCI host.
This means we will no longer have to add Intel xHCI hosts to a quirks list when
the PCI device IDs change. Simply continuing to add new Inte
Hi All,
I'm very happy to announce libusbx-1.0.16-rc1, highlights:
* As Nathan Hjelm already announced in his "libusb and libusbx
merging" mail, Nathan has taken over libusb maintenance and
this release is a combined effort between the libusb and
libusbx projects!
* Hotplug support for Darwin a
Commit 8d2421e ("usb: musb: kill global and static for multi instance")
removed the global dma_mask copy and replaced by parent's DMA mask. The
problem here is that if the parent does not have a dma_mask then
musb_remove() goes kaboom.
Instead trying to fix this I was thinking we do we need to eras
On 06/20/2013 03:02 PM, Roger Quadros wrote:
> On 06/20/2013 02:55 PM, Roger Quadros wrote:
>> On 06/19/2013 09:42 PM, Kevin Hilman wrote:
>>> Roger Quadros writes:
>>>
Add the Idle state pins for USB host and enable WAKEUP on
DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
>>>
On 06/19/2013 08:30 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 06/19/2013 06:05 PM, Roger Quadros wrote:
>
>> To ensure hardware context is restored while resuming from
>> OFF mode we need to enable the Hardware SAR bit for the
>> USB Host power domain.
>
>> Signed-off-by: Roger Quadros
>> ---
On 06/19/2013 06:23 PM, Alan Stern wrote:
> On Wed, 19 Jun 2013, Roger Quadros wrote:
>
>> Hi,
>>
>> This series attempts to suspend the OMAP EHCI host controller on USB
>> Bus suspend.
>
> Why do you want to suspend the host controller during bus suspend?
> They are two different operations an
On 06/20/2013 03:11 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jun 19, 2013 at 05:05:51PM +0300, Roger Quadros wrote:
>> Runtime suspend the controller during bus suspend and resume it
>> during bus resume. This will ensure that the USB Host power domain
>> enters lower power state and does not pre
On 06/19/2013 08:39 PM, Kevin Hilman wrote:
> Hi Roger,
>
> Roger Quadros writes:
>
>> Runtime suspend the controller during bus suspend and resume it
>> during bus resume. This will ensure that the USB Host power domain
>> enters lower power state and does not prevent the SoC from
>> endering d
On 06/20/2013 03:07 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jun 19, 2013 at 05:05:48PM +0300, Roger Quadros wrote:
>> We no longer need to be initialized in any particular order
>> so move driver initialization to the standard place i.e. module_init()
>>
>> CC: Samuel Ortiz
>> Signed-off-by: Ro
On 06/19/2013 08:23 PM, Kevin Hilman wrote:
> Hi Roger,
>
> Roger Quadros writes:
>
>> In order to support wake up from suspend use the pinctrl
>> framework to put the USB host pins in IDLE state during suspend.
>>
>> CC: Samuel Ortiz
>> Signed-off-by: Roger Quadros
>
> You should use helpers
DM9620 is an USB2.0 network adapter rather than DM9601 USB1.1. This
driver processed the RX data 4 bytes header, TX data 2 bytes header,
make the control bit exactly right in PHY write function, and optional
IFF_ALLMUTLI bit for RX control.
Tested good for many platforms, include X86 desktop and A
Hi,
On Thu, Jun 20, 2013 at 08:53:05AM +0800, Chao Xie wrote:
> >> @@ -2674,6 +2693,9 @@ void usb_remove_hcd(struct usb_hcd *hcd)
> >> free_irq(hcd->irq, hcd);
> >> }
> >>
> >> + if (hcd->phy)
> >> + usb_phy_shutdown(hcd->phy);
> >> +
> >> usb_put_
Hi,
On Thu, Jun 20, 2013 at 01:53:13PM +, Yuan-Hsin Chen wrote:
> Because fotg210-udc is configured as a non-hotpluggable device,
> that makes sense to use module_platform_driver_probe() instead of
> module_platform_driver(). This also fixes the section mismatch issue.
>
> Signed-off-by: Yuan
Hi,
On Wed, Jun 19, 2013 at 05:05:51PM +0300, Roger Quadros wrote:
> Runtime suspend the controller during bus suspend and resume it
> during bus resume. This will ensure that the USB Host power domain
> enters lower power state and does not prevent the SoC from
> endering deeper sleep states.
>
Hi,
On Wed, Jun 19, 2013 at 05:05:48PM +0300, Roger Quadros wrote:
> We no longer need to be initialized in any particular order
> so move driver initialization to the standard place i.e. module_init()
>
> CC: Samuel Ortiz
> Signed-off-by: Roger Quadros
> ---
> drivers/mfd/omap-usb-host.c |
On 06/20/2013 02:55 PM, Roger Quadros wrote:
> On 06/19/2013 09:42 PM, Kevin Hilman wrote:
>> Roger Quadros writes:
>>
>>> Add the Idle state pins for USB host and enable WAKEUP on
>>> DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
>>> sleep on any USB activity (e.g. remote wakeup or co
On 06/19/2013 09:42 PM, Kevin Hilman wrote:
> Roger Quadros writes:
>
>> Add the Idle state pins for USB host and enable WAKEUP on
>> DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
>> sleep on any USB activity (e.g. remote wakeup or connect/disconnect).
>>
>> CC: Benoît Cousson
>> Sig
Hello.
On 20-06-2013 13:36, Manjunath Goudar wrote:
Suspend scenario in case of ohci-da8xx glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_da8xx_suspend() will ensure proper
handling of suspend scenari
Hi,
>> Yes, i see the bad characters in the log file. I apologize for that,
>> my eyes was in pain after looking thru the log files and did not
>> notice that when i attached the log file.
>>
>> The good news is i can get gadget to work with Lenovo x100e on Ubuntu
>> and Windows. The change is add
Suspend scenario in case of ohci-platform glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_platform_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Berg
Suspend scenario in case of ohci-pxa27x glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_hcd_pxa27x_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd
Suspend scenario in case of ohci-spear glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in spear_ohci_hcd_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Be
Suspend scenario in case of ohci-sm501 glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_sm501_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Suspend scenario in case of ohci-ep93xx glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_hcd_ep93xx_drv_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd
Suspend scenario in case of ohci-s3c2410 glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_hcd_s3c2410_drv_suspend() will ensure
proper handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arn
Suspend scenario in case of ohci-omap glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_omap_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Cc
Suspend scenario in case of ohci-da8xx glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in ohci_da8xx_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Suspend scenario in case of ohci-exynos glue was not
properly handled as it was not suspending generic part
of ohci controller. Calling explicitly the ohci_suspend()
routine in exynos_ohci_suspend() will ensure proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Suspend scenario in case of OHCI was not properly
handled in ochi_suspend()routine. This does proper
handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Cc: Alan Stern
Cc: Greg KH
Cc: linux-usb@vger.kernel.org
V3: New patch.
V4: No change.
---
drivers/usb/host/oh
Suspend scenario in case of ohci-at91 glue was not properly
handled as it was not suspending generic part of ohci controller.
Calling explicitly the ohci_suspend() routine in ohci_hcd_at91_drv_suspend()
will ensure proper handling of suspend scenario.
Signed-off-by: Manjunath Goudar
Acked-by: Ala
Suspend scenario in case of ohci bus glue was not properly handled as
it was not suspending generic part of ohci controller. Calling
explicitly the ohci_suspend()routine will ensure proper handling
of suspend scenario.
V2:
-Incase ohci_suspend() fails, return right away without executing further.
ATENÇÃO;
Sua caixa de correio excedeu o limite de 5 GB de armazenamento, que é como
definido pelo administrador, você está atualmente em execução no 10.9GB, você
pode não ser capaz de enviar ou receber novas mensagens até que você re-validar
a sua caixa de correio. Para revalidar sua caixa de c
Hi,
On Monday 17 June 2013 09:39 AM, Chanwoo Choi wrote:
On 06/14/2013 10:10 PM, Kishon Vijay Abraham I wrote:
Modified dwc3-omap to receive connect and disconnect notification using
extcon framework. Also did the necessary cleanups required after
adapting to extcon framework.
Signed-off-by: K
* Kevin Hilman [130619 10:30]:
> Hi Roger,
>
> Roger Quadros writes:
>
> > In order to support wake up from suspend use the pinctrl
> > framework to put the USB host pins in IDLE state during suspend.
> >
> > CC: Samuel Ortiz
> > Signed-off-by: Roger Quadros
>
> You should use helpers for th
Hi,
> Yes, i see the bad characters in the log file. I apologize for that,
> my eyes was in pain after looking thru the log files and did not
> notice that when i attached the log file.
>
> The good news is i can get gadget to work with Lenovo x100e on Ubuntu
> and Windows. The change is adding mo
59 matches
Mail list logo
