From: Ming Lei
Date: Tue, 6 Nov 2012 22:53:03 +0800
> This patchset avoids accessing auto-suspended device in ioctl path,
> which is generally triggered by some network utility(ethtool, ifconfig,
> ...)
>
> Most of network devices have the problem, but as discussed in the
> thread:
>
>
12. c. The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified it.
I think that's the case, doesn't is?
Do we really need all of this intricacy to apply this very simple patch? [1]
[1] https://bugs.launchpad.net/ubuntu/+source/linux
On Tue, 6 Nov 2012, Forest Bond wrote:
> From: Forest Bond
>
> Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
> with class HID and protocol None, so they would be claimed by whichever
> driver was loaded first. Some of these devices do in fact work with
> usbhid, but not
Hi Felipe,
On 11/06/2012 07:22 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Nov 06, 2012 at 05:58:57PM +0100, Benoit Cousson wrote:
>> On 11/06/2012 05:44 PM, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Tue, Nov 06, 2012 at 07:26:06PM +0530, Afzal Mohammed wrote:
OMAP2+ family of devices are now obt
Hello.
On 06-11-2012 22:41, Forest Bond wrote:
From: Forest Bond
Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
with class HID and protocol None, so they would be claimed by whichever
driver was loaded first. Some of these devices do in fact work with
usbhid, but no
On 11/07/2012 12:22 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: linux-...@vger.kernel.org
> Cc: linux-in...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Cc: net...@vger.kernel.org
> Cc
Hi all,
On Tue, Oct 30, 2012 at 10:27 AM, Praveen Paneri wrote:
>
> This driver uses usb phy framework to interact with s3c-hsotg. Supports
> phy_init and phy_shutdown functions to enable/disable usb phy. Support
> will be extended to host controllers and more Samsung SoCs.
>
> Signed-off-by: Pr
Hi Greg,
Our host controller sets PRC and CSC bits at the time of initialization
even though no USB device is attached. At the time of initialization,
hub_probe() gets called and in-turn it calls hub_activate().
hub_activate() clears the CSC bit, but PRC bit does not get cleared (in
linux 3.6.1).
Unfortunately I have some issues with git send-email.
I've attached the patch itself ..
regards,
-- dmytro
On Tue, Nov 6, 2012 at 12:27 PM, Felipe Balbi wrote:
> On Sun, Nov 04, 2012 at 03:30:21PM +0100, Dmytro Milinevskyy wrote:
>> Convert USB descriptor's fields to CPU byte order before using
Hi,
On Tue, Nov 6, 2012 at 10:13 PM, Felipe Balbi wrote:
> On Tue, Nov 06, 2012 at 08:58:49PM +0530, Vivek Gautam wrote:
>> Adding DWC3 device tree node for Exynos5250 along with the
>> device address and clock support needed for the controller.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>> arch
Hi,
On Wed, Nov 7, 2012 at 5:10 AM, Sylwester Nawrocki
wrote:
>
> Hi,
>
> I have a few comments. Please see below...
>
>
> On 11/06/2012 04:36 PM, Vivek Gautam wrote:
>>
>> Adding support for USB3.0 phy for dwc3 controller on
>> exynso5250 SOC.
>
>
> exynso -> exynos
Sure, will correct this.
>
Hi Sergei,
On Wed, Nov 07, 2012 at 03:29:16PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 06-11-2012 22:41, Forest Bond wrote:
>
> >From: Forest Bond
>
> >Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
> >with class HID and protocol None, so they would be claimed by w
On Wed, 7 Nov 2012, Forest Bond wrote:
> > /*
> > * bla
> > * bla
> > */
> >
> > WBR, Sergei
>
> Thanks for the feedback. I had scanned the file and saw both styles. It
> would
> be nice if checkpatch.pl issued a warning for this.
>
> Jiri, would you like me to resend?
Not necessary, min
On Wed, Nov 07, 2012 at 03:02:39PM +0100, Jiri Kosina wrote:
> On Wed, 7 Nov 2012, Forest Bond wrote:
>
> > > /*
> > > * bla
> > > * bla
> > > */
> > >
> > > WBR, Sergei
> >
> > Thanks for the feedback. I had scanned the file and saw both styles. It
> > would
> > be nice if checkpatch.pl i
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Nov 07, 2012 at 08:40:05AM -0200, Marco Biscaro wrote:
> 12. c. The contribution was provided directly to me by some other
> person who certified (a), (b) or (c) and I have not modified it.
>
>
This patch (as1631) fixes a bug that shows up when a config change
fails for a device under an xHCI controller. The controller needs to
be told to disable the endpoints that have been enabled for the new
config. The existing code does this, but before storing the
information about which endpoints
On Tue, 6 Nov 2012, Jason J. Herne wrote:
> I was comparing the two USB captures and I noticed the Windows capture
> uses a READ(16) and Linux is using a READ(10). I'm not sure how the
> kernel determines which read command to use, but I'm wondering if this
> could be the problem here?
It could
On Wed, Nov 7, 2012 at 11:00 AM, Alan Stern wrote:
> On Tue, 6 Nov 2012, Jason J. Herne wrote:
>
>> I was comparing the two USB captures and I noticed the Windows capture
>> uses a READ(16) and Linux is using a READ(10). I'm not sure how the
>> kernel determines which read command to use, but I'm
Hi,
On Wed, Nov 07, 2012 at 06:55:03PM +0530, Vivek Gautam wrote:
> Hi,
>
>
> On Tue, Nov 6, 2012 at 10:13 PM, Felipe Balbi wrote:
> > On Tue, Nov 06, 2012 at 08:58:49PM +0530, Vivek Gautam wrote:
> >> Adding DWC3 device tree node for Exynos5250 along with the
> >> device address and clock supp
On Wed, 7 Nov 2012, Jason J. Herne wrote:
> > Most likely that's the answer. Of course, for a device to recognize
> > READ(16) but not READ(10) is a violation of the SCSI spec.
> >
> > I don't know what criterion Windows uses. Maybe it uses READ(16)
> > whenever the total capacity is >= 2^32 blo
Hi Vivek, Felipe,
On Wednesday 07 of November 2012 18:43:22 Felipe Balbi wrote:
> Hi,
>
> On Wed, Nov 07, 2012 at 06:55:03PM +0530, Vivek Gautam wrote:
> > Hi,
> >
> > On Tue, Nov 6, 2012 at 10:13 PM, Felipe Balbi wrote:
> > > On Tue, Nov 06, 2012 at 08:58:49PM +0530, Vivek Gautam wrote:
> > >>
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Cc: Nicolas Ferre
Cc: linux-...@vger.kernel.org
Cc: linux-in...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: net...@vger.kernel.org
Cc: linux-pcm...@lists.infradead.org
Cc: rtc-li...@googlegroups.com
Cc: spi-devel-
On Wed, Nov 7, 2012 at 12:14 PM, Alan Stern wrote:
> On Wed, 7 Nov 2012, Jason J. Herne wrote:
>
>> > Most likely that's the answer. Of course, for a device to recognize
>> > READ(16) but not READ(10) is a violation of the SCSI spec.
>> >
>> > I don't know what criterion Windows uses. Maybe it u
On Mon, 5 Nov 2012, Christof Meerwald wrote:
> BTW, I have been able to reproduce the problem on a completely
> different machine (also running Ubuntu 12.10, but different hardware).
> The important thing appears to be that the USB audio device is
> connected via a USB 2.0 hub (and then using the
On Wed, Nov 7, 2012 at 12:27 PM, Jason J. Herne wrote:
> On Wed, Nov 7, 2012 at 12:14 PM, Alan Stern wrote:
>> On Wed, 7 Nov 2012, Jason J. Herne wrote:
>>
>>> > Most likely that's the answer. Of course, for a device to recognize
>>> > READ(16) but not READ(10) is a violation of the SCSI spec.
If we do have endpoints named like "ep-a" then bEndpointAddress is
counted internally by the gadget framework.
If we do have endpoints named like "ep-1" then bEndpointAddress is
assigned from the digit after "ep-".
If we do have both, then it is likely that after we used up the
"generic" endpoints
This introduces the function interface and converts f_acm into a module
and makes all its users use the function interface.
Patch #1 and #2 fix two things I've found during testing.
I am still thinking about a mechanism to share a function among two
configs. I have two ideas but for now I clone t
The setup request can be sent to an interface/endpoint or to the device
itself. If it is sent to an interface then we forward it to the function
that is mapped to that interface. The same is true if an endpoint is the
target of the setup request.
If the device is the target of a setup request then
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig |4 ++
drivers/usb/gadget/Makefile |1 +
drivers/usb/gadget/f_loopback.c | 129 +--
drivers/usb/gadget/g_zero.h | 22 ---
drivers/usb/gadget/zero.c | 129
Lets assume nokia_bind() starts with "return -EINVAL". After loading the
gadget we end up with:
|udc dummy_udc.0: registering UDC driver [g_nokia]
|BUG: unable to handle kernel NULL pointer dereference at 0040
|IP: [] __list_add+0x25/0xf0
|Call Trace:
| [] rollback_registered+0x21/0x40
| [] un
The significant part of this function was removed in 90f7976 ("USB:
Remove unsupported usb gadget drivers"). I would move this to function
bind time but I don't see the point in moving an empty function.
Therefore bye bye.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_acm.c |
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig|4 +
drivers/usb/gadget/Makefile |3 +
drivers/usb/gadget/f_sourcesink.c | 193 ++---
drivers/usb/gadget/zero.c | 97 +--
4 files changed, 235 i
This patch provides an infrastructure to register & unregister an USB
function. This allows to turn a function into a module and avoid the
'#include "f_.*.c"' magic and we get a clear API / cut between the bare
gadget and its functions.
The concept is simple:
Each functions defines the DECLARE_USB_
f_loopback should only include the bare function but it also includes
the config descriptor. This patch moves the config descriptor into
zero.c, the only user of this function.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_loopback.c | 44 ++-
f_sourcesink should only include the bare function but it also includes
the config descriptor. This patch moves the config descriptor into
zero.c, the only user of this function.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_sourcesink.c | 48 +++
This patch converts the acm_ms gadget to make use of the function
framework to request the ACM function.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/multi.c | 63 +---
2 files changed, 54 insertion
This will be used to remove a single function from a given config. Right
now "ignore" that an error at ->bind() time and cleanup later during
composite_unbind() / remove_config().
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/composite.c | 12
include/linux/usb/c
This patch converts the acm_ms gadget to make use of the function
framework to request the ACM function.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/acm_ms.c | 30 +++---
2 files changed, 24 insertions(+), 7 dele
This patch factors out the three possible functions into three possible
bind functions which are passed as an argument to usb_add_config(). This
will ease the step by step converting of the individual functions to the
new function registration method.
Signed-off-by: Sebastian Andrzej Siewior
---
Every user of u_serial has now to select the U_SERIAL symbol instead of
including the file.
There is one limition with this: ports and and gs_tty_driver are global
variables in u_serial. Since all users share them, there can be only one
user loaded at a time i.e. either g_serial or g_nokia.
Signed
This patch converts f_acm into a module which uses the new function
interface. It also converts one of its users that is g_serial to make
use of it. The other users of it (g_nokia for instance) are still using
the old include file system and should not notice the change at all. So
they can be conve
This patch converts the acm_ms gadget to make use of the function
framework to request the ACM function.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/cdc2.c | 25 -
2 files changed, 21 insertions(+), 5 deletions(-
This patch converts the acm_ms gadget to make use of the function
framework to request the ACM function.
With nokia beeing the last user of the include interface, it is gone
now.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/Kconfig|1 +
drivers/usb/gadget/f_acm.c|
Hi Vivek,
On 11/06/2012 04:36 PM, Vivek Gautam wrote:
Adding base address information and required platform data
support for enabling USB DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi|3 ++-
arch/arm/mach-exynos/include/mach/regs
On Wed, Nov 07, 2012 at 01:56:49PM +0330, A Sh wrote:
> 1. There is no xhci-hcd.ko at least for 3.2 kernels( I'm sure either for
> community compiled kernels or self-compiled kernels.) but it's the module
> responsible for usb3 and it's being used by kernel (for example command
> dmesg | grep xhci
On Tue, Nov 06, 2012 at 07:28:34PM -0500, cov...@ccs.covici.com wrote:
> Thanks much -- should I leave the previous patch in?
Yes. Sorry for not being clear. Did you leave the first patch in for
the log file you sent me?
Sarah Sharp
--
To unsubscribe from this list: send the line "unsubscribe l
On Wed, 7 Nov 2012, Jason J. Herne wrote:
> On Wed, Nov 7, 2012 at 12:27 PM, Jason J. Herne wrote:
> > On Wed, Nov 7, 2012 at 12:14 PM, Alan Stern
> > wrote:
> >> On Wed, 7 Nov 2012, Jason J. Herne wrote:
> >>
> >>> > Most likely that's the answer. Of course, for a device to recognize
> >>> >
On Wed, 7 Nov 2012, Sebastian Andrzej Siewior wrote:
> If we do have endpoints named like "ep-a" then bEndpointAddress is
> counted internally by the gadget framework.
> If we do have endpoints named like "ep-1" then bEndpointAddress is
> assigned from the digit after "ep-".
> If we do have both,
On Wed, 7 Nov 2012, Chris Stankevitz wrote:
> Hello,
>
> Background: I'm running an experiment that is sensitive to USB
> latency of a few milliseconds. During a typical overnight run I
> encounter a handful such "high latency events" and I am trying to
> understand why they happen. If you can
At Wed, 7 Nov 2012 12:34:43 -0500 (EST),
Alan Stern wrote:
>
> On Mon, 5 Nov 2012, Christof Meerwald wrote:
>
> > BTW, I have been able to reproduce the problem on a completely
> > different machine (also running Ubuntu 12.10, but different hardware).
> > The important thing appears to be that th
On 11/07/2012 02:35 PM, Vivek Gautam wrote:
@@ -180,10 +273,12 @@ enum samsung_cpu_type {
/*
* struct samsung_usbphy - transceiver driver state
* @phy: transceiver structure
+ * @phy3: transceiver structure for USB 3.0
* @plat: platform data
* @dev: The parent device supplied t
Yep, I did leave the first patch in.
Sarah Sharp wrote:
> On Tue, Nov 06, 2012 at 07:28:34PM -0500, cov...@ccs.covici.com wrote:
> > Thanks much -- should I leave the previous patch in?
>
> Yes. Sorry for not being clear. Did you leave the first patch in for
> the log file you sent me?
>
> S
On 10/02/2012 09:16 AM, Olivier Sobrie wrote:
> This driver provides support for several Kvaser CAN/USB devices.
> Such kind of devices supports up to three CAN network interfaces.
>
> It has been tested with a Kvaser USB Leaf Light (one network interface)
> connected to a pch_can interface.
> The
Em 07-11-2012 12:46, Greg KH escreveu:
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
Ok.
Someone needs to send it, in email, with the proper information, so it
can be applied. I can't scrape it out of a random bugzilla, sorry.
Do you mean l
On Wed, 7 Nov 2012, Takashi Iwai wrote:
> > What is the right solution for this problem?
>
> How about the patch below? (It's for 3.6, and won't be applied cleanly
> to 3.7, but easy to adapt.)
I simplified your patch a little. This is for 3.7, not 3.6. I
verified that it does fix the proble
On Wed, Nov 07, 2012 at 08:19:19PM +0100, Takashi Iwai wrote:
> How about the patch below? (It's for 3.6, and won't be applied cleanly
> to 3.7, but easy to adapt.)
Thanks, that patch seems to fix the problem.
Christof
--
http://cmeerw.org sip:cmeerw at cmeerw.or
On Nov 8, 2012, Takashi Iwai wrote:
> How about the patch below? (It's for 3.6, and won't be applied cleanly
> to 3.7, but easy to adapt.)
This patch fixes my problem, thank you!
You can add me as "Tested by".
Artem
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
t
This patch (as1630) cleans up a few minor items resulting from the
split-up of the ehci-hcd driver:
Remove the product_desc string from the ehci_driver_overrides
structure. All drivers will use the generic "EHCI Host
Controller" string. (This was requested by Felipe Balbi
This patch (as1632) fixes a bug in ehci-hcd. The USB core uses
urb->hcpriv to determine whether or not an URB is active; host
controller drivers are supposed to set this pointer to a non-NULL
value when an URB is queued. However ehci-hcd sets it to NULL for
isochronous URBs, which defeats the che
This patch (as1633) changes slightly the way usbcore handled
submissions of URBs that are already active. It will now return
-EBUSY rather than -EINVAL, and it will call WARN_ONCE to draw
people's attention to the bug.
Signed-off-by: Alan Stern
---
Documentation/usb/error-codes.txt |2 ++
Patch #2 does not apply cleanl to the net tree.
Please respin and repost this entire series again.
Thanks.
--
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 http://vger.kernel.org/majordomo-info.h
Hi
For testing purposes i would like to make my usb host connect only with
12MBit/s instead of 480Mbit/s. On a pc platform i would just unload the ehci
module but as the USB_EHCI_MXC depends on ehci this is not possible.
Are there any other options to disable hispeed mode. Like some magic in
s
On Wed, Nov 7, 2012 at 12:28 AM, Bjørn Mork wrote:
> Linus Walleij writes:
>> So all MTP devices manufactured before that spec, and numerous produced
>> after that spec came out, and several still being produced don't use the
>> class code, i.e. they violate the spec. But we still have to detect
On Wed, Nov 7, 2012 at 2:54 AM, Peter Stuge wrote:
>> - some devices bug out on libusb_open()
>
> Please send me a debug log from when this happens. Exact steps are at
> http://libusb.org/wiki/debug
I'll see what I can dig up. Mostly this has come from upstream,
Alessio do you have something at
cdc_eem USB host driver and gadget driver both are broken in 1500 MTU
case while using 802.1Q VLANs. In both cases, this is due to the
assumption of standard Ethernet frame length.
v2: rebase against Dave Miller's 'net/master' tree
Ian Coolidge (2):
usb: gadget: g_ether: fix frame size check fo
Checking skb->len against ETH_FRAME_LEN assumes a 1514
ethernet frame size. With an 802.1Q VLAN header, ethernet
frame length can now be 1518. Validate frame length against that.
Signed-off-by: Ian Coolidge
---
drivers/usb/gadget/u_ether.c |3 ++-
1 files changed, 2 insertions(+), 1 deletion
cdc_eem frames might need to contain 802.1Q VLAN Ethernet frames.
URB/skb sizing from usbnet will default to the hard_mtu,
so account for the VLAN header by expanding that via hard_header_len
Signed-off-by: Ian Coolidge
---
drivers/net/usb/cdc_eem.c |3 ++-
1 files changed, 2 insertions(+),
On 07.11.2012 20:19, Takashi Iwai wrote:
> At Wed, 7 Nov 2012 12:34:43 -0500 (EST),
> Alan Stern wrote:
>>
>> On Mon, 5 Nov 2012, Christof Meerwald wrote:
>>
>>> BTW, I have been able to reproduce the problem on a completely
>>> different machine (also running Ubuntu 12.10, but different hardware).
>
> On Mon, Oct 22, 2012 at 03:13:09PM +0800, Peter Chen wrote:
> > The real reason causes mx23 fail are:
> >
> > - Calling mxs_phy_hw_init(mxs_phy) again at connection
> > - Error connect/disconnect nodity at hub.c
> >
> > The coming patch will fix above two problems, Mike Thompson
> > tested h
>
> On Mon, Oct 22, 2012 at 5:13 AM, Peter Chen
> wrote:
> > The real reason causes mx23 fail are:
> >
> > - Calling mxs_phy_hw_init(mxs_phy) again at connection
> > - Error connect/disconnect nodity at hub.c
> >
> > The coming patch will fix above two problems, Mike Thompson
>
> So shouldn't
> > @@ -89,14 +89,34 @@ static struct ci13xxx_platform_data
> > ci13xxx_imx_platdata __devinitdata = { .name =
> "ci13xxx_imx",
> > .flags = CI13XXX_REQUIRE_TRANSCEIVER |
> > CI13XXX_PULLUP_ON_VBUS |
> > -
>
> Just a nitpick really, but what about parametrizing this code so we won't
> have
> two copies of the same loop?
>
> Say:
>
> uint32_t bit = low ? OTGSC_BSV : OTGSC_AWW;
> const char *name = low ? "B_SESS_VALID" : "A_VBUS_VALID";
>
> while (!(otgsc & bit)) {
> if (time_after(jiffies,
>
> On Mon, Nov 05, 2012 at 08:27:40PM +0300, Dan Carpenter wrote:
> > Hello Richard Zhao,
> >
> > The patch 8c4fc031954b: "USB: chipidea: add vbus detect for udc" from
> > Sep 12, 2012, leads to the following Smatch warning:
> > drivers/usb/chipidea/udc.c:1683 udc_irq()
> > warn: odd binop
From: Ian Coolidge
Date: Wed, 7 Nov 2012 16:39:17 -0800
> cdc_eem USB host driver and gadget driver both are broken in 1500 MTU
> case while using 802.1Q VLANs. In both cases, this is due to the
> assumption of standard Ethernet frame length.
>
> v2: rebase against Dave Miller's 'net/master' tr
Change since v1:
[PATCH 3] Rename link file's name "child" to "device", add check of
return value of
sysfs_create_link() and handle error return value properly.
Change since v2:
[PATCH 1] fix a logic backward problem. Add changelog about change ehci
root hub descriptors based on A
ACPI provide "_PLD" and "_UPC" aml methods to describe usb port
visibility and connectability. This patch is to use those information
to change ehci root hub descriptors and set usb hub port's DeviceRemovable
in the hub_configure(). When hub descriptor request is issued at first time,
usb port devi
This patch is to set xhci root hub's DeviceRemovable according to usb port's
connect type which currently comes from ACPI information rather than xhci PORTSC
register due to Windows prefers to ACPI information. If ACPI information was
different with PORTSC, there would be a warning.
Signed-off-by:
To show the relationship between usb port and child device,
add link file "port" under usb device's sysfs directoy and
"device" under usb port device's sysfs directory. They are linked
to each other.
Signed-off-by: Lan Tianyu
---
drivers/usb/core/hub.c | 26 ++
1 file c
Some platforms provide usb port connect types through ACPI. This
patch is to add this new attribute to expose these information
to user space.
Signed-off-by: Lan Tianyu
---
Documentation/ABI/testing/sysfs-bus-usb |9 +++
drivers/usb/core/hub.c | 43
On Wed, Nov 07, 2012 at 06:31:20PM -0200, Marco Biscaro wrote:
> Em 07-11-2012 12:46, Greg KH escreveu:
> >A: No.
> >Q: Should I include quotations after my reply?
> >
> >http://daringfireball.net/2007/07/on_top
>
> Ok.
>
> >Someone needs to send it, in email, with the proper information, so it
>
Hi,
On Wed, Nov 7, 2012 at 10:48 PM, Tomasz Figa wrote:
> Hi Vivek, Felipe,
>
> On Wednesday 07 of November 2012 18:43:22 Felipe Balbi wrote:
>> Hi,
>>
>> On Wed, Nov 07, 2012 at 06:55:03PM +0530, Vivek Gautam wrote:
>> > Hi,
>> >
>> > On Tue, Nov 6, 2012 at 10:13 PM, Felipe Balbi wrote:
>> > >
At Thu, 08 Nov 2012 01:42:59 +0100,
Daniel Mack wrote:
>
> On 07.11.2012 20:19, Takashi Iwai wrote:
> > At Wed, 7 Nov 2012 12:34:43 -0500 (EST),
> > Alan Stern wrote:
> >>
> >> On Mon, 5 Nov 2012, Christof Meerwald wrote:
> >>
> >>> BTW, I have been able to reproduce the problem on a completely
>
At Wed, 7 Nov 2012 15:37:17 -0500 (EST),
Alan Stern wrote:
>
> On Wed, 7 Nov 2012, Takashi Iwai wrote:
>
> > > What is the right solution for this problem?
> >
> > How about the patch below? (It's for 3.6, and won't be applied cleanly
> > to 3.7, but easy to adapt.)
>
> I simplified your patch
Changes from v1:
- Changed the device node names from 'ehci' and 'ohci' to
'usb@1211' and 'usb@1212' as per discussion for the
change 'http://www.spinics.net/lists/linux-usb/msg73993.html'
- Rebased on for-next branch of linux-samsung.
Vivek Gautam (2):
ARM: Exynos5250: Enabling
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
.../devicetree/bindings/usb/exynos-usb.txt | 25
arch/arm/boot/dts/exynos5250-smdk5250.dts |4 ++
Adding OHCI device tree node for Exynos5250 along with
the device base address.
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
---
.../devicetree/bindings/usb/exynos-usb.txt | 15 +++
arch/arm/boot/dts/exynos5250.dtsi |6 ++
arch/arm/mach-exynos/
On 08.11.2012 07:43, Takashi Iwai wrote:
> At Thu, 08 Nov 2012 01:42:59 +0100,
> Daniel Mack wrote:
>>
>> On 07.11.2012 20:19, Takashi Iwai wrote:
>>> At Wed, 7 Nov 2012 12:34:43 -0500 (EST),
>>> Alan Stern wrote:
On Mon, 5 Nov 2012, Christof Meerwald wrote:
> BTW, I have been ab
87 matches
Mail list logo
