On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> For all ux500 based platforms the maximum number of end-points are used.
> Move this knowledge into the driver so we can relinquish the burden from
> platform data. This also removes quite a bit of complexity from the driver
> and will aid us w
On Wed, May 29, 2013 at 7:57 PM, Felipe Balbi wrote:
> On Wed, May 15, 2013 at 10:51:43AM +0100, Lee Jones wrote:
>> For all ux500 based platforms the maximum number of end-points are used.
>> Move this knowledge into the driver so we can relinquish the burden from
>> platform data. This also remo
On Thu, 30 May 2013, Linus Walleij wrote:
> On Wed, May 29, 2013 at 7:57 PM, Felipe Balbi wrote:
> > On Wed, May 15, 2013 at 10:51:43AM +0100, Lee Jones wrote:
> >> For all ux500 based platforms the maximum number of end-points are used.
> >> Move this knowledge into the driver so we can relinqui
Hi,
>> Ok. What other gadget driver can i test with UDC driver? Is it the
>> mass storage driver (mass_storage.c)?
>
> That is essentially the same as g_file_storage. But there are lots of
> others. You should start with g_zero and run the testusb suite. See
>
> http://www.linux-usb.org
Hello,
On Fri, May 24, 2013 at 09:46:32AM -0400, Alan Stern wrote:
> On Fri, 24 May 2013, Philippe De Muyter wrote:
>
> > On Thu, May 23, 2013 at 08:31:18AM -0700, Greg Kroah-Hartman wrote:
> > > On Thu, May 23, 2013 at 03:07:09PM +0200, Philippe De Muyter wrote:
> > > > Hi all,
> > > >
> > > >
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> The MUSB HDRC configuration never changes between each of the ux500
> supported platforms, so there's little point passing it though platform
> data. If we set it in the driver instead, we can make good use of it
> when booting with either ATAG
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> The dma_mask will always be the same as the coherent_dma_mask, so let's
> cut down on the platform_data burden and set it as such in the driver.
> This also saves us from supporting it separately when we come to enable
> this driver for Device
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> In its current state, the ux500-musb driver uses platform data pointers
> blindly with no prior checking. If no platform data pointer is passed
> this will Oops the kernel. In this patch we ensure platform data and
> board data are present prio
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> If we can ever get to a state where we can solely search for DMA channels
> by name, this will almost completely alleviate the requirement to pass
> copious amounts of information though platform data. Here we take the
> first step towards this
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> This patch will allow ux500-musb to be probed and configured solely from
> configuration found in Device Tree.
>
> Cc: Felipe Balbi
> Cc: Rob Herring
> Cc: linux-usb@vger.kernel.org
> Cc: devicetree-disc...@lists.ozlabs.org
> Acked-by: Linus
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> The recently DT:ed MUSB driver will require clock-name by device-name
> look-up capability, until common clk has is properly supported by the
> ux500 platform.
>
> Acked-by: Linus Walleij
> Acked-by: Fabio Baltieri
> Signed-off-by: Lee Jones
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> Now the ux500-musb driver has been enabled for Device Tree, there is no
> requirement to register it from platform code.
>
> Acked-by: Fabio Baltieri
> Signed-off-by: Lee Jones
Patch applied to my ux500-dma40 branch on top of the musb
stuff.
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> As promised, now all devices which resided in u8500_of_init_devices()
> have been enabled for Device Tree, we can completely remove it.
>
> Acked-by: Fabio Baltieri
> Signed-off-by: Lee Jones
Applied on my ux500-dma40 branch.
And this is lo
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> The aim is to make the code that little more readable.
>
> Acked-by: Vinod Koul
> Acked-by: Arnd Bergmann
> Reviewed-by: Linus Walleij
> Signed-off-by: Lee Jones
Patch applied to my ux500-dma40 branch.
Yours,
Linus Walleij
--
To unsubscri
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> STEDMA40_*_TO_* direction definitions are identical in all but name to
> the pre-defined generic DMA_*_TO_* ones. Let's make things easy by not
> duplicating such things.
>
> Signed-off-by: Lee Jones
Vinod, I'm lacking your ACK on this patch,
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> STEDMA40_*_TO_* direction definitions are identical in all but name to
> the pre-defined generic DMA_*_TO_* ones. Let's make things easy by not
> duplicating such things.
>
> Cc: Vinod Koul
> Cc: Dan Williams
> Cc: Per Forlin
> Cc: Rabin Vin
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> We're now using the transfer direction definitions provided by the DMA
> sub-system, so the home-brew ones have become obsolete.
>
> Signed-off-by: Lee Jones
Tentatively applied, also missing Vinod's ACK on this, but it seems
it was implicitl
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> The aim is to make the code that little more readable.
>
> Cc: Vinod Koul
> Cc: Dan Williams
> Cc: Per Forlin
> Cc: Rabin Vincent
> Signed-off-by: Lee Jones
Patch applied with Vinod's ACK.
Yours,
Linus Walleij
--
To unsubscribe from this
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> When a DMA client requests and configures a DMA channel, it requests
> data_width in Bytes. The DMA40 driver then swiftly converts it over to
> the necessary register bit value. Unfortunately, for any subsequent
> calculations we have to shift
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> Unsure of the author's intentions, rather than just removing the nop,
> we're replacing it with a comment containing the possible intention
> of the statement OR:ing with 0.
>
> Cc: Vinod Koul
> Cc: Dan Williams
> Cc: Per Forlin
> Cc: Rabin
On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
> At this moment in time the memcpy channels which can be used by the D40
> are fixed, as each supported platform in Mainline uses the same ones.
> However, platforms do exist which don't follow this convention, so
> these will need to be tailore
On Wed, May 15, 2013 at 11:52 AM, Lee Jones wrote:
> The DMA platform data is now empty due to some recent refactoring,
> so there is no longer a requirement to pass it though.
>
> Acked-by: Arnd Bergmann
> Signed-off-by: Lee Jones
Applied to dma40 branch, hm now I may get a conflict with all
On Wed, May 15, 2013 at 11:52 AM, Lee Jones wrote:
> Some platforms insist on obscure physical channel availability. This
> information is currently passed though platform data in internal BSP
> kernels. Once those platforms land, they'll need to configure them
> appropriately, so we may as well
On Wed, May 15, 2013 at 11:52 AM, Lee Jones wrote:
> Some platforms have channels which are not available for normal use.
> This information is currently passed though platform data in internal
> BSP kernels. Once those platforms land, they'll need to configure them
> appropriately, so we may as
This series patch begins the process of splitting ohci-platform up
into independent driver modules and add a name for the platform-private field.
Patch 1/2 separate ohci-platform into independent driver modules.
Patch 2/2 adds an ohci->priv field for private use by OHCI platform drivers.
Ma
This patch splits the ohci-platform code from ohci-hcd out
into its own separate driver module.This work is part of enabling
multi-platform kernels on ARM.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Cc: Greg KH
Cc: Alan Stern
Cc: linux-usb@vger.kernel.org
---
drivers/usb/host/Kconfig
This patch adds an ohci->priv field for private use by OHCI
platform drivers.
Until now none of the platform drivers has used this private space,
but that's about to change in the next patch of this series.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Cc: Greg KH
Cc: Alan Stern
Cc: linux
Pci_enable_device() will set device power state to D0,
so it's no need to do it again in ci13xxx_pci_probe().
Signed-off-by: Yijing Wang
---
drivers/usb/chipidea/ci13xxx_pci.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/chipidea/ci13xxx_pci.c
b/drivers/u
Pci_enable_device() will set device power state to D0,
so it's no need to do it again in dwc3_pci_probe().
Signed-off-by: Yijing Wang
---
drivers/usb/dwc3/dwc3-pci.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c
Pci_enable_device() will set device power state to D0,
so it's no need to do it again in dwc2_driver_probe().
Signed-off-by: Yijing Wang
---
drivers/staging/dwc2/pci.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/dwc2/pci.c b/drivers/staging/dwc2/pci.
On 05/29/2013 08:37 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, May 29, 2013 at 11:58:01AM +0800, Chao Xie wrote:
>> On Wed, May 29, 2013 at 12:24 AM, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Mon, May 13, 2013 at 10:13:44AM -0400, Alan Stern wrote:
On Mon, 13 May 2013, Chao Xie wrote:
>
While reading the config parsing code I noticed this check is missing, without
this check config->desc.wTotalLength can end up with a value larger then the
dev->rawdescriptors length for the config, and when userspace then tries to
get the rawdescriptors bad things may happen.
Signed-off-by: Hans
The config descriptors as read from /proc/bus/usb/BBB/DDD are in *bus* endian
format. Correct proc_usb_info.txt to correctly reflect that.
Signed-off-by: Hans de Goede
---
Documentation/usb/proc_usb_info.txt | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentati
Correct use of devnum in supports_autosuspend documentation, the sysfs path
contains busnum-port.port.port not busnum-devnum (which is the usb bus device
address).
Signed-off-by: Hans de Goede
---
Documentation/ABI/testing/sysfs-bus-usb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Signed-off-by: Hans de Goede
---
Documentation/ABI/testing/sysfs-bus-usb | 29 +
1 file changed, 29 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-usb
b/Documentation/ABI/testing/sysfs-bus-usb
index bbccdbf..0778140 100644
--- a/Documentation/ABI/test
I'm struggling with this issue since a while and as the author of the
USB-Serial module I thought experts here might provide some help... As
it's a USB-serail issue, I've posted on both USB and Serial lists.
thanks in advance!
The problem is about connecting with a 3G USB modem, a ZTE MF-210
mini-
From: Jassi Brar
prm_to_uac2() is broken because it tests against pointer it itself
mapped onto, which will never be different.
Fix the mapping by adding pointer to parent chip in each rtd param
and removing the prm_to_uac2().
Reported-by: Julien Rouviere
Signed-off-by: Jassi Brar
---
drivers
Hi Michael,
On Wed, May 29, 2013 at 02:41:08PM +0200, Michael Grzeschik wrote:
> Peters patches need some more care, as they are not cleanly sperated.
> One patch e.g. adds an delayed worker to handle the otg events. Another
> one above that patch is removing the worker afterwards.
I see, thanks!
Hello list!
I'm using a http://www.septentrio.com/products/receivers/asterx2i-oem
INS/GNSS receiver. When connected via USB to a windows-host, there's two
(or even three, don't remember exactly) virtual serial ports to talk to it.
When connected to a 3.8.0-19-generic #30-Ubuntu SMP i686 GNU/L
On Thu, 30 May 2013, Roger Quadros wrote:
> >> So what are your idea about making the PHY layer more generic? How
> >> ehci-hcd will make use of PHY layer?
> >
> >
> > on probe grab the phy and initialize it. On suspend/resume,
> > suspend/resume the PHY and so on. Whatever you were going to do
On Thu, 30 May 2013, victor yeo wrote:
> I tested the g_zero with USB 2.0 Command Verifier. After the Command
> Verifier is run, the UDC gadget driver queue function is continuously
> being called, and the linux command prompt is frozen. Please see the
> attached UDC driver log. It looks like endp
On Thu, 30 May 2013, Hans de Goede wrote:
> While reading the config parsing code I noticed this check is missing, without
> this check config->desc.wTotalLength can end up with a value larger then the
> dev->rawdescriptors length for the config, and when userspace then tries to
> get the rawdescr
On Thu, 30 May 2013, Hans de Goede wrote:
> +What:/sys/bus/usb/devices/.../bConfigurationValue
> +KernelVersion: since atleast 2.6.18
s/atleast/at least/ and ditto for the preceding entry.
> +Description:
> + bConfigurationValue of the *active* configuration for
Hi,
On 05/30/2013 04:51 PM, Alan Stern wrote:
On Thu, 30 May 2013, Hans de Goede wrote:
While reading the config parsing code I noticed this check is missing, without
this check config->desc.wTotalLength can end up with a value larger then the
dev->rawdescriptors length for the config, and whe
Dear Maxime,
On 05/29/2013 09:50 AM, maxime.rip...@free-electrons.com wrote:
Hi,
On Wed, May 29, 2013 at 07:11:30AM +, Chen Peter-B29397 wrote:
Hello,
Am I right in assuming that the MXS USB on-the-go port does not currently
support the
device (gadget) functionality?
Anybody out there w
2013/5/30 Hans de Goede:
> +are wTotalLength bytes apart. If a device returns less configuration
> +descriptor data then indicated by wTotalLength there will be a hole in
s/then/than/
--
Daniele Forsi
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messa
On Thu, 30 May 2013, Hans de Goede wrote:
> Hi,
>
> On 05/30/2013 04:51 PM, Alan Stern wrote:
> > On Thu, 30 May 2013, Hans de Goede wrote:
> >
> >> While reading the config parsing code I noticed this check is missing,
> >> without
> >> this check config->desc.wTotalLength can end up with a val
2013/5/30 Hans de Goede:
> + be trusted, as the device may have a smaller config descriptor
> + then it advertises. The bLength field of each (sub) descriptor
as in the other text: s/then/than/
--
Daniele Forsi
--
To unsubscribe from this list: send the line "unsubsc
On Thu, 30 May 2013, Manjunath Goudar wrote:
> This patch splits the ohci-platform code from ohci-hcd out
> into its own separate driver module.This work is part of enabling
> multi-platform kernels on ARM.
Okay, except...
> +static const struct ohci_driver_overrides platform_overrides = {
> +
On Thu, 30 May 2013, Manjunath Goudar wrote:
> This patch adds an ohci->priv field for private use by OHCI
> platform drivers.
>
> Until now none of the platform drivers has used this private space,
> but that's about to change in the next patch of this series.
As far as I'm concerned, this does
Hello.
On 05/30/2013 09:23 PM, Alan Stern wrote:
This patch splits the ohci-platform code from ohci-hcd out
into its own separate driver module.This work is part of enabling
multi-platform kernels on ARM.
Okay, except...
+static const struct ohci_driver_overrides platform_overrides = {
+
On Thu, May 30, 2013 at 06:16:34AM +0200, Alexander Holler wrote:
> Am 30.05.2013 00:25, schrieb Sarah Sharp:
> >
> > On Wed, May 29, 2013 at 11:14:32PM +0200, Alexander Holler wrote:
> >> Current Renesas Electronics XHCI hosts (which were formerly NEC)
> >> do support the same vendor command to s
This patch adds the possibility of the "mode" being specified in a device
tree. This allows the scenario when there maybe multiple USB subsystems
operating in different modes.
Signed-off-by: Ruchika Kharwar
---
Documentation/devicetree/bindings/usb/dwc3.txt |3 ++-
drivers/usb/dwc3/core.c
On Thu, 30 May 2013, Grant wrote:
> > There are two things you can do to help diagnose this. One is to build
> > a kernel with CONFIG_USB_DEBUG enabled and then post the portion of the
> > dmesg log showing what happens when you eject, unplug, and replug the
> > device.
>
> I've enabled CONFIG_U
> From: Yijing Wang [mailto:wangyij...@huawei.com]
> Sent: Thursday, May 30, 2013 3:24 AM
>
> Pci_enable_device() will set device power state to D0,
> so it's no need to do it again in dwc2_driver_probe().
>
> Signed-off-by: Yijing Wang
> ---
> drivers/staging/dwc2/pci.c |2 --
> 1 files ch
On Thu, May 30, 2013 at 06:16:34AM +0200, Alexander Holler wrote:
> Am 30.05.2013 00:25, schrieb Sarah Sharp:
> >
> > On Wed, May 29, 2013 at 11:14:32PM +0200, Alexander Holler wrote:
> >> Current Renesas Electronics XHCI hosts (which were formerly NEC)
> >> do support the same vendor command to s
On Wed, May 29, 2013 at 10:45:04AM -0700, Sarah Sharp wrote:
> On Wed, May 29, 2013 at 10:27:50AM +0900, Greg Kroah-Hartman wrote:
> > On Fri, May 24, 2013 at 05:42:52PM -0700, Sarah Sharp wrote:
> > > This patchset address some (but not all) of the security issues found
> > > with the Klockwork st
On Thu, May 30, 2013 at 11:04:23AM +0200, Linus Walleij wrote:
> On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
>
> > Unsure of the author's intentions, rather than just removing the nop,
> > we're replacing it with a comment containing the possible intention
> > of the statement OR:ing with
On Wed, 29 May 2013, Joe Julian wrote:
> On 05/22/2013 12:27 PM, Alan Stern wrote:
> > On Wed, 22 May 2013, Joe Julian wrote:
> >
> >> On 05/21/2013 03:20 PM, Joe Julian wrote:
> >>> I have about 100 of these creditcard/check scanners that are dropping
> >>> events. I was able to find some overflo
On Thu, 30 May 2013, Tobias Diedrich wrote:
> Alan Stern wrote:
> > On Sat, 25 May 2013, Tobias Diedrich wrote:
> >
> > > I've recently upgraded my kernel from 3.8.5 to 3.9.2 and ran into an
> > > issue with usb-audio:
> > > With two different usb-headsets, pulseaudio is now regularily losing the
HI
On Thu, May 30, 2013 at 09:12:11AM +0100, Lee Jones wrote:
> On Thu, 30 May 2013, Linus Walleij wrote:
>
> > On Wed, May 29, 2013 at 7:57 PM, Felipe Balbi wrote:
> > > On Wed, May 15, 2013 at 10:51:43AM +0100, Lee Jones wrote:
> > >> For all ux500 based platforms the maximum number of end-poi
On Thu, 30 May 2013, Alan Stern wrote:
> On Thu, 30 May 2013, Tobias Diedrich wrote:
>
> > Alan Stern wrote:
> > > On Sat, 25 May 2013, Tobias Diedrich wrote:
> > >
> > > > I've recently upgraded my kernel from 3.8.5 to 3.9.2 and ran into an
> > > > issue with usb-audio:
> > > > With two differe
On 05/30/2013 12:56 PM, Ruchika Kharwar wrote:
> This patch adds the possibility of the "mode" being specified in a device
> tree. This allows the scenario when there maybe multiple USB subsystems
> operating in different modes.
Nitpick. Maybes and possibilities can we get more concrete statements
Addition of the M and N recommended values for the USB3 PHY DPLL.
Sysclk for DRA7xx is 20MHz.
This yields:
Clk = 20MHz * M/(N+1) = 20MHz * 1000 /(7+1) = 2.5 Ghz
Signed-off-by: Ruchika Kharwar
---
drivers/usb/phy/phy-omap-usb3.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
di
This patch adds an optional parameter "dr_mode" to the dwc3 core device node.
In the case the compile flag for the DWC3 controller is set to
"USB_DWC3_DUAL_ROLE" a device tree could restrain to either functionality of
host or gadget. In the case the device tree does not use this optional flag or
sp
* Felipe Balbi [130528 09:42]:
> Hi,
>
> On Mon, May 27, 2013 at 05:02:09PM +0200, Arnd Bergmann wrote:
> > Hi Felipe,
> >
> > We've gone through remaining work items for getting the ARM kernel
> > to full multiplatform support again, and MUSB came up. I'm sure you
> > have your own thoughts on
Hello.
On 05/31/2013 12:14 AM, Ruchika Kharwar wrote:
This patch adds an optional parameter "dr_mode" to the dwc3 core device node.
In the case the compile flag for the DWC3 controller is set to
"USB_DWC3_DUAL_ROLE" a device tree could restrain to either functionality of
host or gadget. In the
On Thu, May 30, 2013 at 10:18 PM, Tony Lindgren wrote:
> TUSB would work with dmaengine, but AFAIK we're still missing the
> dmaengine configuration options to support increasing device end
> FIFO address.
Can you elaborate on this? What is the usecase here?
Yours,
Linus Walleij
--
To unsubscri
This patch adds an optional parameter "dr_mode" to the dwc3 core device node.
In the case the compile flag for the DWC3 controller is set to
"USB_DWC3_DUAL_ROLE" a device tree could restrain to either functionality of
host or gadget. In the case the device tree does not use this optional flag or
sp
* Linus Walleij [130530 13:27]:
> On Thu, May 30, 2013 at 10:18 PM, Tony Lindgren wrote:
>
> > TUSB would work with dmaengine, but AFAIK we're still missing the
> > dmaengine configuration options to support increasing device end
> > FIFO address.
>
> Can you elaborate on this? What is the usec
Fix spelling in my own comments
On 05/30/2013 03:31 PM, Dan Murphy wrote:
> On 05/30/2013 03:14 PM, Ruchika Kharwar wrote:
>> This patch adds an optional parameter "dr_mode" to the dwc3 core device node.
>> In the case the compile flag for the DWC3 controller is set to
>> "USB_DWC3_DUAL_ROLE" a de
* Tony Lindgren [130530 13:25]:
>
> TUSB we can make depend on ARMv7, the only implementation we have
> is for omap2420, which is ARMv6. This should solve the issue for
> ARMv7 multiplatform builds for now.
Sorry mean depend on !ARMv7. But thinking about it more, that does
not make much sense as
On Thu, May 30, 2013 at 10:31 PM, Tony Lindgren wrote:
> There are many devices where the device FIFO is memory mapped to the
> GPMC bus on omaps, like TUSB, OneNAND, smc911x etc. I believe the
> only reason why these have not been converted to the dmaengine is
> the fact that dmaengine cannot co
Alan Stern wrote:
> On Thu, 30 May 2013, Tobias Diedrich wrote:
>
> > Alan Stern wrote:
> > > On Sat, 25 May 2013, Tobias Diedrich wrote:
> > >
> > > > I've recently upgraded my kernel from 3.8.5 to 3.9.2 and ran into an
> > > > issue with usb-audio:
> > > > With two different usb-headsets, pulse
Alan Stern wrote:
> On Thu, 30 May 2013, Alan Stern wrote:
>
> > On Thu, 30 May 2013, Tobias Diedrich wrote:
> >
> > > Alan Stern wrote:
> > > > On Sat, 25 May 2013, Tobias Diedrich wrote:
> > > >
> > > > > I've recently upgraded my kernel from 3.8.5 to 3.9.2 and ran into an
> > > > > issue with
On 05/30/2013 03:35 PM, Dan Murphy wrote:
Fix spelling in my own comments
On 05/30/2013 03:31 PM, Dan Murphy wrote:
On 05/30/2013 03:14 PM, Ruchika Kharwar wrote:
This patch adds an optional parameter "dr_mode" to the dwc3 core device node.
In the case the compile flag for the DWC3 controller
On 05/24/2013 11:31 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: Kishon Vijay Abraham I
> ---
> drivers/usb/dwc3/dw
Am 30.05.2013 20:20, schrieb Sarah Sharp:
> On Thu, May 30, 2013 at 06:16:34AM +0200, Alexander Holler wrote:
> The point is that unless Renesas tells us how to know if a host
> supports the firmware fetch vendor command, we should stop issuing that
> command to the host. I think my contacts at R
-Original Message-
From: Wei Yongjun [mailto:weiyj...@gmail.com]
Sent: Tuesday, May 21, 2013 10:41 AM
To: gre...@linuxfoundation.org; Wendy Yuan-Hsin Chen(陳元馨)
Cc: yongjun_...@trendmicro.com.cn; linux-usb@vger.kernel.org
Subject: [PATCH -next] usb: fusbh200-hcd: fix error handling in
fus
On Thu, May 30, 2013 at 01:54:49PM -0700, Tony Lindgren wrote:
> * Tony Lindgren [130530 13:25]:
> >
> > TUSB we can make depend on ARMv7, the only implementation we have
> > is for omap2420, which is ARMv6. This should solve the issue for
> > ARMv7 multiplatform builds for now.
>
> Sorry mean d
Hi,
On Thu, May 30, 2013 at 02:53:10PM -0500, Dan Murphy wrote:
> > @@ -520,9 +520,23 @@ static int dwc3_probe(struct platform_device *pdev)
> > mode = DWC3_MODE_HOST;
> > else if (IS_ENABLED(CONFIG_USB_DWC3_GADGET))
> > mode = DWC3_MODE_DEVICE;
> > - else
> > -
This patch is to add a check of "portnum" which from the usb
port dev's name. The "portnum" will be used as array index
for struct usb_hub->ports in the usb_set_hub_port_connect_type().
Signed-off-by: Lan Tianyu
---
drivers/usb/core/usb-acpi.c |3 +++
1 file changed, 3 insertions(+)
diff --
82 matches
Mail list logo
