Hi,
> > > >
> > > > # insmod kagen2_udc.ko
> > > > # insmod g_file_storage.ko file=/dev/mmcblk0
> > > > gadget: controller 'kagen2_usb' not recognized
> > >
> > > this should have caught your attention!! Also, rebase to a newer
> > > kernel as
> > that
> > > message has already been dropped.
> >
Hi,
On 12/14/2012 07:44 PM, Paul Walmsley wrote:
> Hi
>
> On Fri, 14 Dec 2012, Tony Lindgren wrote:
>
>> Paul, what about this patch? Looks like you've acked the other clock
>> patches in this series but not this one?
>
> I commented on it briefly here:
>
> https://patchwork.kernel.org/patch/
This patch removes gserial_setup() and gserial_cleanup() and adds
gserial_alloc_line() and gserial_free_line() to replace them.
The initial setup of u_serial happens now on module load time. A
maximum of four TTY ports can be requested which is the current limit.
In theory we could extend this lim
On Mon, 17 Dec 2012, [KOI8-R] � wrote:
> Guys, possibly found bug in usb host controller.
This is not a new bug; it has been known for many, many years. The
ehci-hcd driver does not allocate periodic schedules very well for
full-speed and low-speed devices.
> Attempting to read /dev/
On Mon, 17 Dec 2012, Chen Gang wrote:
> 于 2012年12月17日 11:08, Alan Stern 写道:
> > It is pretty much as I explained in my previous email.
> >
> > finish_urb calls usb_free_priv while holding the lock. Then while
> > still holding the lock, it calls usb_hcd_unlink_urb_from_ep.
> >
> > In addition,
On Sun, 16 Dec 2012, Vincent Pelletier wrote:
> Le dimanche 16 décembre 2012 20:46:38, Vincent Pelletier a écrit :
> > I checked the specs, and the warnings about wMaxPacketSize seem
> > justified (although it's unclear to me wether wMaxPacketSize is
> > restricted to exactly 512B in HS, or only u
On Mon, Dec 17, 2012 at 02:37:17PM +0100, Sebastian Andrzej Siewior wrote:
> diff --git a/drivers/usb/gadget/nokia.c b/drivers/usb/gadget/nokia.c
> index 60937d0..93c5b4c 100644
> --- a/drivers/usb/gadget/nokia.c
> +++ b/drivers/usb/gadget/nokia.c
> @@ -191,8 +203,10 @@ static int __init nokia_bind
On Thu, Dec 13, 2012 at 03:11:19PM +0100, Armando Visconti wrote:
> In the IN case, since the USB request is allocated only when
> the source/sink function is started and never freed, the USB ept
> buffer needs to be inited only at the beginning. This change
^^
> results in
On Sun, 16 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> I applied the modifications you suggested, this is the output:
>
> [ 110.922009] ehci_hcd :00:0b.1: async off
> [ 209.362134] ehci_hcd :00:0b.1: async on
> [ 241.794760] ehci_hcd :00:0b.1: alan start cur time 429490899
On 12/17/2012 10:13 AM, Benoit Cousson wrote:
> Hi,
>
> On 12/14/2012 07:44 PM, Paul Walmsley wrote:
>> Hi
>>
>> On Fri, 14 Dec 2012, Tony Lindgren wrote:
>>
>>> Paul, what about this patch? Looks like you've acked the other clock
>>> patches in this series but not this one?
>>
>> I commented on
On Fri, Dec 14, 2012 at 05:38:10PM -0800, ian coolidge wrote:
> Felipe, Tony, Grazvydas, Thanks for the responses,
>
> On Fri, Dec 14, 2012 at 4:13 AM, Felipe Balbi wrote:
>
> > Hi,
> >
> > On Fri, Dec 14, 2012 at 02:13:07PM +0200, Grazvydas Ignotas wrote:
> > > On Fri, Dec 14, 2012 at 11:53 AM,
On Mon, Dec 17, 2012 at 04:12:13PM +0800, victor wrote:
> Hi,
>
> > > > >
> > > > > # insmod kagen2_udc.ko
> > > > > # insmod g_file_storage.ko file=/dev/mmcblk0
> > > > > gadget: controller 'kagen2_usb' not recognized
> > > >
> > > > this should have caught your attention!! Also, rebase to a new
On 12/17/2012 05:13 PM, Roger Quadros wrote:
> On 12/17/2012 10:13 AM, Benoit Cousson wrote:
>> Hi,
>>
>> On 12/14/2012 07:44 PM, Paul Walmsley wrote:
>>> Hi
>>>
>>> On Fri, 14 Dec 2012, Tony Lindgren wrote:
>>>
Paul, what about this patch? Looks like you've acked the other clock
patches
On Thu, 13 Dec 2012 00:45:05 -0800, Lan Tianyu
wrote:
diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
index f034716..9335f1b 100644
--- a/drivers/usb/core/hcd.c
+++ b/drivers/usb/core/hcd.c
@@ -2509,7 +2509,8 @@ int usb_add_hcd(struct usb_hcd *hcd,
* they only forward requ
Sarah pointed out that the USB3.0 spec also updates the amount of power
that may be consumed by the device and quoted 9.2.5.1:
|"The amount of current draw for SuperSpeed devices are increased to 150
|mA for low-power devices and 900 mA for high-power"
This patch tries to update all users to use
The USB 2.0 specification says that bMaxPower is the maximum power
consumption expressed in 2 mA units and the USB 3.0 specification says
that it is expressed in 8 mA units.
This patch adds a helper function usb_get_max_power() which computes the
value based on config & usb_device's speed value. Th
On 12/17/2012 04:45 PM, Sebastian Andrzej Siewior wrote:
On Thu, Dec 13, 2012 at 03:11:19PM +0100, Armando Visconti wrote:
In the IN case, since the USB request is allocated only when
the source/sink function is started and never freed, the USB ept
buffer needs to be inited only at the beginning
On Mon, Dec 17, 2012 at 7:33 AM, Alan Stern wrote:
> On Sun, 16 Dec 2012, Vincent Pelletier wrote:
>
>> Le dimanche 16 décembre 2012 20:46:38, Vincent Pelletier a écrit :
>> > I checked the specs, and the warnings about wMaxPacketSize seem
>> > justified (although it's unclear to me wether wMaxPac
Hi Alan,
I applied the latest patch, changing the unlinking
behavior of EHCI.
I tested quite extensively and I could not see the
issue (as expected). At a certain point I lost 3 HDDs,
but this is something I saw before (it happens very
seldom, maybe future debugging) and it was not really
locking
On Mon, 17 Dec 2012, Piergiorgio Sartor wrote:
> Hi Alan,
>
> I applied the latest patch, changing the unlinking
> behavior of EHCI.
>
> I tested quite extensively and I could not see the
> issue (as expected). At a certain point I lost 3 HDDs,
> but this is something I saw before (it happens ve
On Mon, 17 Dec 2012, Octavio Alvarez wrote:
> On Thu, 13 Dec 2012 00:45:05 -0800, Lan Tianyu
> wrote:
>
> > diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
> > index f034716..9335f1b 100644
> > --- a/drivers/usb/core/hcd.c
> > +++ b/drivers/usb/core/hcd.c
> > @@ -2509,7 +2509,8 @@ i
On Mon, 17 Dec 2012, Sebastian Andrzej Siewior wrote:
> The USB 2.0 specification says that bMaxPower is the maximum power
> consumption expressed in 2 mA units and the USB 3.0 specification says
> that it is expressed in 8 mA units.
> This patch adds a helper function usb_get_max_power() which co
On Mon, 17 Dec 2012, Sebastian Andrzej Siewior wrote:
> Sarah pointed out that the USB3.0 spec also updates the amount of power
> that may be consumed by the device and quoted 9.2.5.1:
>
> |"The amount of current draw for SuperSpeed devices are increased to 150
> |mA for low-power devices and 900
On Mon, 17 Dec 2012, Benoit Cousson wrote:
> It was done for legacy reason but should disappear once the modulemode
> will be be removed from the clock nodes.
Here's a start at taking care of the low-hanging fruit:
http://marc.info/?l=linux-omap&m=135577685007813&w=2
Only lightly tested, so tes
On 12/13/2012 11:59 PM, Venu Byravarasu wrote:
> As Tegra USB host driver is using instance number for resetting
> PORT0 twice, adding a new DT property for handling this.
Alan, Greg, Felip,e
This series looks fine to me.
I'd like to take all the Tegra-related USB patches through the Tegra
tree
On Mon, Dec 17, 2012 at 03:12:14PM -0500, Alan Stern wrote:
> On Mon, 17 Dec 2012, Sebastian Andrzej Siewior wrote:
>
> > Sarah pointed out that the USB3.0 spec also updates the amount of power
> > that may be consumed by the device and quoted 9.2.5.1:
> >
> > |"The amount of current draw for Sup
On Mon, Dec 17, 2012 at 02:07:59PM -0700, Stephen Warren wrote:
> On 12/13/2012 11:59 PM, Venu Byravarasu wrote:
> > As Tegra USB host driver is using instance number for resetting
> > PORT0 twice, adding a new DT property for handling this.
>
> Alan, Greg, Felip,e
>
> This series looks fine to m
Add support for canbus activity led indicators on usb_8dev devices by
calling appropriate can_led functions.
These are only enabled when CONFIG_CAN_LEDS is Y, becomes no-op
otherwise.
Signed-off-by: Bernd Krumboeck
---
drivers/net/can/usb/usb_8dev.c | 11 +++
1 file changed, 11 insert
On Sun, Dec 16, 2012 at 12:37:00AM +, Ben Hutchings wrote:
> Since Linux 3.2.16, my desktop with an Asus P8Z68-V LX motherboard
> always wakes up a few seconds after I shutdown. I then have to switch
> it off a second time. This still occurs in Linux 3.6.9 (haven't tried
> 3.7 yet).
>
> I ini
On Mon, 17 Dec 2012, Stephen Warren wrote:
> On 12/13/2012 11:59 PM, Venu Byravarasu wrote:
> > As Tegra USB host driver is using instance number for resetting
> > PORT0 twice, adding a new DT property for handling this.
>
> Alan, Greg, Felip,e
>
> This series looks fine to me.
>
> I'd like to
On Mon, 17 Dec 2012, Greg KH wrote:
> You can't pick anything up for 3.9 until after 3.8-rc1 is out, according
> to the rules of linux-next
Well, you can accept a submission and store it in a private tree until
then. You just can't put it in any tree that feeds into linux-next.
Alan Stern
--
On Sun, Dec 16, 2012 at 04:49:42PM -0500, Alan Stern wrote:
> On Sun, 16 Dec 2012, Vincent Pelletier wrote:
>
> > Hi.
> >
> > I have a device which enumerates properly on this superspeed host controler:
> >
> > 06:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host
> > Controller (re
A high speed control or bulk endpoint may have bInterval set to zero,
which means it does not NAK. If bInterval is non-zero, it means the
endpoint NAKs at a rate of 2^(bInterval - 1).
The xHCI code to compute the NAK interval does handle the special case
of zero properly. The current code uncond
On Mon, Dec 17, 2012 at 11:08 AM, Steve Calfee wrote:
> On Mon, Dec 17, 2012 at 7:33 AM, Alan Stern wrote:
>> On Sun, 16 Dec 2012, Vincent Pelletier wrote:
>>
>>> Le dimanche 16 décembre 2012 20:46:38, Vincent Pelletier a écrit :
>>> > I checked the specs, and the warnings about wMaxPacketSize se
Hi Javier,
Thanks for catching this! The patch is going to have to wait until
after the 3.8 merge window closes, since I believe Greg isn't accepting
usb-next pull requests yet.
Sarah Sharp
On Sun, Dec 16, 2012 at 04:21:31AM +0100, Javier Martinez Canillas wrote:
> The union xhci_trb *trb varia
于 2012年12月17日 23:27, Alan Stern 写道:
> On Mon, 17 Dec 2012, Chen Gang wrote:
>
>> 于 2012年12月17日 11:08, Alan Stern 写道:
>>> It is pretty much as I explained in my previous email.
>>>
>>> finish_urb calls usb_free_priv while holding the lock. Then while
>>> still holding the lock, it calls usb_hcd_u
On Tue, Dec 18, 2012 at 12:01:35AM -0200, Fabio Estevam wrote:
> Hi,
>
> Booting a 3.7 kernel on a mx6qsabrelite board via NFS and using an
> asix USB/Ethernet adapter and then I try to transfer a 10MB file from
> the target to the host:
Has this ever worked before on any older kernel?
thanks,
From: fangxiaozhi
1. Define a new macro for USB storage match rules:
matching with Vendor ID and interface descriptors.
Signed-off-by: fangxiaozhi
diff -uprN linux-3.7_bak/drivers/usb/storage/usb.c
linux-3.7/drivers/usb
From: fangxiaozhi
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
2. Add to support new switch command for new Huawei USB dongles.
Signed-off-by: fangxiaozhi
-
于 2012年12月17日 23:27, Alan Stern 写道:
> On Mon, 17 Dec 2012, Chen Gang wrote:
>
>> 于 2012年12月17日 11:08, Alan Stern 写道:
>>> It is pretty much as I explained in my previous email.
>>>
>>> finish_urb calls usb_free_priv while holding the lock. Then while
>>> still holding the lock, it calls usb_hcd_u
When I connect a wired Xbox 360 controller (black, in case it matters),
the four LEDs around the "X" button start blinking and never stop. The
controller is a retail "Xbox 360 Controller for Windows" device. dmesg:
usb 2-1.1: new full-speed USB device number 3 using ehci_hcd
input: Micros
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 10 +++
drivers/usb/phy/samsung-usbphy.c | 80 ++--
2 files ch
Based on patches for samsung-usbphy driver available at:
https://patchwork.kernel.org/patch/1794651/
In this patch we are adding support to parse device tree data for
samsung-usbphy driver and further setting pmu_isolation to
enable/disable phy as and when needed.
This further chucks out the need
My USB2.0 cameras are enumerated fine on ehci systems. But not on my new Ubuntu
12.10:
$uname -a
Linux VAIO 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
here xhci_hcd is compiled in the kernel, and the device is not enumerated. I
tried unbinding x
Using devm_kzalloc for allocating memory needed for PHY
pointer and hence removing kfree calls to PHY pointer.
Signed-off-by: Venu Byravarasu
---
drivers/usb/phy/tegra_usb_phy.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/phy/tegra_usb_phy.c b/drivers/
As pointer to PHY structure can be stored in struct usb_hcd
making use of it, to call PHY APIs.
Call to usb_phy_shutdown() is moved up in tegra_ehci_remove(),
so that to avoid dereferencing of hcd after its freed up.
Signed-off-by: Venu Byravarasu
---
This patch depends on patch
http://marc.inf
On 12/17/2012 11:40 PM, Sarah Sharp wrote:
> Hi Javier,
>
> Thanks for catching this! The patch is going to have to wait until
> after the 3.8 merge window closes, since I believe Greg isn't accepting
> usb-next pull requests yet.
>
> Sarah Sharp
>
> On Sun, Dec 16, 2012 at 04:21:31AM +0100, Ja
47 matches
Mail list logo