On Saturday, July 28, 2012, Alan Stern wrote:
> On Sat, 28 Jul 2012, Rafael J. Wysocki wrote:
>
> > On Saturday, July 28, 2012, Alan Stern wrote:
> > > On Fri, 27 Jul 2012, Rafael J. Wysocki wrote:
> > >
> > > > > > > > + if (parent)
> > > > > > > > + pm_runtime_put(parent);
>
On Sun, 29 Jul 2012, James wrote:
> I have 3.5.0+
> How can I find out what the problem is with my USB UPS?
Your logs indicate that the UPS repeatedly disconnects from and
reconnects to the USB bus. At least, that's what it looks like -- it's
hard to say for sure because your logs don't have t
On Sun, 29 Jul 2012, Rafael J. Wysocki wrote:
> The difference is, if you use _put_sync(), you need to wait the extra 10 ms
> for local_pci_probe() to return (if the parent is actually suspended),
> although you might not need to wait for it if you used _put(), right?
Yes, that's the difference.
On Thu, Jul 26, 2012 at 10:26 PM, Alan Stern wrote:
> On Thu, 26 Jul 2012, Rajaram R wrote:
>
>> Hi Felipe/Alan
>>
>> Any comments for the below query ?
>>
>> On Thu, Jul 12, 2012 at 4:53 PM, Rajaram R
>> wrote:
>> > Hi
>> >
>> >
>> > On Thu, Nov 18, 2010 at 6:17 PM, Tatyana Brokhman
>> > wrote
On 07/29/12 10:50, Alan Stern wrote:
> On Sun, 29 Jul 2012, James wrote:
>
>> I have 3.5.0+
>> How can I find out what the problem is with my USB UPS?
>
> Your logs indicate that the UPS repeatedly disconnects from and
> reconnects to the USB bus. At least, that's what it looks like -- it's
>
Hi Alan,
Here is the full log . During a reboot the usb device is
enumerated in High speed (480 Mb/s) . The it change status to full
Speed (12 Mb/s) followed by a disconnect . After this the device
is again enumerated back in High speed .
[0.971658] ehci_
On Sat, Jul 28, 2012 at 8:50 PM, Clemens Ladisch wrote:
> Alexey Filin wrote:
>> On Fri, Jul 27, 2012 at 5:04 PM, Peter Stuge wrote:
>>> If you require consumer interfaces and you want neither USB nor
>>> Ethernet then I guess there is only FireWire left to choose from.
>>
>> "The FireWire host i
On Sunday, July 29, 2012, Alan Stern wrote:
> On Sun, 29 Jul 2012, Rafael J. Wysocki wrote:
>
> > The difference is, if you use _put_sync(), you need to wait the extra 10 ms
> > for local_pci_probe() to return (if the parent is actually suspended),
> > although you might not need to wait for it if
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
The semantic patch (http://coccinelle.lip6.fr/) used in generating this
patch is as follows. Some manual cleanup may be required. This improves
on the previous version in that more devm functions are treated.
virtual after_start
virtual returned
virtual returnedDup
virtual arg
virtual all_args
v
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
The original code was also missing a call to io
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
A new label name is created in one case to bett
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
From: Julia Lawall
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Julia Lawall
---
Not compiled.
On Sun, Jul 29, 2012 at 8:25 PM, Alan Stern wrote:
>
> For me there's also an issue of style: If you do a synchronous get then it
> looks odd not to do a synchronous put. My feeling has always been that
> the async routines are for use in non-process contexts, where the sync
> routines can't be u
Alexey Filin wrote:
> On Sat, Jul 28, 2012 at 8:50 PM, Clemens Ladisch wrote:
>> Alexey Filin wrote:
>>> On Fri, Jul 27, 2012 at 5:04 PM, Peter Stuge wrote:
If you require consumer interfaces and you want neither USB nor
Ethernet then I guess there is only FireWire left to choose from.
On Thu, Jul 26, 2012 at 7:47 PM, Alan Stern wrote:
> You can do this only by hacking up a special driver of your own.
> Since transfer completions would not be reported by IRQs in time, you
> would have to poll for transfer completions at microsecond intervals.
> This would present a rather large
On Sun, 29 Jul 2012, Rajaram R wrote:
> > The ep list doesn't belong to the gadget driver; it belongs to the UDC
> > driver. The maxpacket has to be adjusted to match the value stored in
> > the descriptor so that the UDC will tell the hardware to use the right
> > maxpacket value.
>
> The ep li
On Sun, 29 Jul 2012, James wrote:
> >> It noticeably slows down booting.
> >
> > It shouldn't interfere appreciably with booting, unless you're waiting
> > for some other USB device to be detected. All the USB communication
> > should happen in the background.
>
> It does wait until the UPS is
On Sun, 29 Jul 2012, shaiju shaiju wrote:
> Hi Alan,
>
> Here is the full log . During a reboot the usb device is
> enumerated in High speed (480 Mb/s) . The it change status to full
> Speed (12 Mb/s) followed by a disconnect . After this the device
> is again en
On Mon, 30 Jul 2012, Jassi Brar wrote:
> On Sun, Jul 29, 2012 at 8:25 PM, Alan Stern wrote:
> >
> > For me there's also an issue of style: If you do a synchronous get then it
> > looks odd not to do a synchronous put. My feeling has always been that
> > the async routines are for use in non-proc
Hi Alen,
This error is intermittent . It doesn't happen always .
Regards,
Shaiju.
-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Sunday, July 29, 2012 2:39 PM
To: shaiju shaiju
Cc: 'Sadasivan Shaiju'; 'Peter Chen'; 'USB list'
Subject: RE: usb devic
On Mon, 30 Jul 2012, Alexey Filin wrote:
> On Thu, Jul 26, 2012 at 7:47 PM, Alan Stern wrote:
> > You can do this only by hacking up a special driver of your own.
> > Since transfer completions would not be reported by IRQs in time, you
> > would have to poll for transfer completions at microseco
On Sun, 29 Jul 2012, shaiju shaiju wrote:
> Hi Alen,
>
> This error is intermittent . It doesn't happen always .
Then there may not be any way to determine the cause. Perhaps the
firmware in the USB device intermittently crashes.
Alan Stern
--
To unsubscribe from this list: send the
Hi Bhupesh,
Thanks for the patches.
Just a quick mail to tell you that I'm not forgetting about them, but I'm
currently travelling with limited time available for patch review. I'll try to
address these in the next couple of days.
On Thursday 26 July 2012 10:42:48 Bhupesh Sharma wrote:
> This
Hi Felipe,
have you had a chance to look at this problem in omap2430_mbus_set_vbus yet?
Are you the person responsible?
thanks,
NeilBrown
On Mon, 9 Jul 2012 01:32:33 -0700 Tony Lindgren wrote:
> * NeilBrown [120706 15:44]:
> >
> > Hello `./scripts/get_maintainer.pl -f drivers/usb/musb/omap
The patch is doing a little bit more than what patch subject says.
Please either come up with a better subject and commit message or
split the patch to have it match the subject.
On Thu, Jul 26, 2012 at 06:35:15PM +0800, Richard Zhao wrote:
> Signed-off-by: Richard Zhao
> ---
> arch/arm/boot/dts
Hi Ido,
Some more comments.
> -Original Message-
> From: Ido Shayevitz [mailto:i...@codeaurora.org]
> Sent: Sunday, July 29, 2012 9:55 PM
> To: Anton Tikhomirov
> Subject: RE: [RFC/PATCH v3] usb: dwc3: Introduce OTG driver for dwc3
>
>
> Hi Anton,
>
> Thanks,
> Fixed and will be sent s
On Fri, 2012-07-27 at 11:11 +0200, Bjørn Mork wrote:
> Huang Ying writes:
>
> > Do you have time to try the following patch?
> >
> > Best Regards,
> > Huang Ying
> >
> > ---
> > drivers/pci/pci-driver.c |6 ++
> > 1 file changed, 6 insertions(+)
> >
> > --- a/drivers/pci/pci-driver.c
> >
The hub is always supposed to support reset and its persist is enabled.
So hub doesn't need attribute avoid_reset_quirk. The patch is to take
attribute avoid_reset_quirk out of usb device's attribute group and
add or remove it in the usb_create/remove_sysfs_dev_files() if the device
is not a usb hu
The attribute avoid_reset_quirk means the device should not be reset.
when it is set, persist_enabled also should be set to 0 to prevent
reset-resume when the device resumes.
Current only in the usb_detect_quirks(), persist_enabled will
be set depending on whether the dev's flag USB_QUIRK_RESET_MO
In USB, the word "config" already has a separate meaning. So it will
cause confusion if use "config" as variable's name for other purposes.
This patch is to convert the "config" to "val"
Signed-off-by: Lan Tianyu
---
Patchset is based on usb-next commit e387ef5c47ddeaeaa3cbdc54424cdb7a28dae2c0.
After sending the USB Bus reset, Host waits for High Speed Chirps.
If the soft-disconnect and soft-connect happens during this chirp time,
then Host doesn't detect this disconnect.
Host treats this as Full Speed Device as there are no chirps.
To avoid this Full Speed Enumeration, soft-disconnect an
On Sat, Jul 28, 2012 at 11:02:13AM +0200, Yann Cantin wrote:
> Hi Dmitry,
>
> >> +config INPUT_EBEAM_USB_CLASSIC
> >> + bool "eBeam Classic Projection support"
> >> + depends on INPUT_EBEAM_USB
> >> + default y
> >
> > Will there be support for other eBean devices (are there any)? If there
> >
38 matches
Mail list logo
