> >
> > Have you opened the mouse by apps (like evtest)?, for USB mouse,
> > the usbhid->intf->needs_remote_wakeup is only set at .open/.close
> > API. That means if you have not opened mouse, the runtime pm status
> > for mouse will changed to RPM_ACTIVE (choose_wakeup ->
> pm_runtime_resume)
>
Hi Alan,
Thanks for your information. It really helps a lot!
We checked the user-space software which use libusb to
communicate to the device. The interrupt transfer was
initiate once and re-submitted in the completion callback.
The transfer buffer length was initiated to be 2048 !! which
actuall
On Thu, 4 Jul 2013, James Stone wrote:
> > Can you post the part of the trace showing where the audio-in Zi lines
> > first appear?
> >
>
> I think this is the start of the Zi lines:
>
> 8800b3585f00 3572683229 C Ci:1:004:0 0 4 = 44ac
> 8800a4976200 3572683283 S Zi:1:004:2 -115:1:168
Signed-off-by: Jóhann B. Guðmundsson
---
drivers/usb/misc/sisusbvga/sisusb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/misc/sisusbvga/sisusb.c
b/drivers/usb/misc/sisusbvga/sisusb.c
index c21386e..de98906 100644
--- a/drivers/usb/misc/sisusbvga/sisusb.c
+++ b/drivers/usb/mi
On Thu, Jul 4, 2013 at 10:13 PM, Alan Stern wrote:
> On Thu, 4 Jul 2013, James Stone wrote:
>
>> OK.. How is this:
>>
>> -71:63:0 -71:126:0 -71:189:0 -71:252:0 504 =
>>
>
> To all appearances, this shows what happens when you
On Thu, 4 Jul 2013, James Stone wrote:
> OK.. How is this:
>
> 8800a4976200 3574521627 S Zi:1:004:2 -115:1:3144 8 -18:0:63
> -18:63:63 -18:126:63 -18:189:63 -18:252:63 504 <
> 8800a49dc600 3574521634 C Zi:1:004:1 0:8:3151:0 1 0:0:4 4 = 08830500
> 8800a49dc600 3574521636 S Zi:1:004:1 -
On Thu, Jul 4, 2013 at 9:12 PM, Alan Stern wrote:
> On Thu, 4 Jul 2013, James Stone wrote:
>
>> > Another hint: The important lines are the ones containing "Zi:1:002:2"
>> > -- the actual string may be slightly different, but it will definitely
>> > contain "Zi" and it will match the " E " lines.
On Thu, 4 Jul 2013, Manjunath Goudar wrote:
> Separate the OHCI pxa27x/pxa3xx host controller driver from
> ohci-hcd host code so that it can be built as a separate driver
> module. This work is part of enabling multi-platform kernels on
> ARM.
> +config USB_OHCI_HCD_PXA27X
> + tristate "Sup
On Thu, 4 Jul 2013, Manjunath Goudar wrote:
> Separate the OHCI EP93XX host controller driver from ohci-hcd
> host code so that it can be built as a separate driver module.
> This work is part of enabling multi-platform kernels on ARM.
> @@ -79,7 +93,10 @@ static int usb_hcd_ep93xx_probe(const st
On Thu, 4 Jul 2013, James Stone wrote:
> > Another hint: The important lines are the ones containing "Zi:1:002:2"
> > -- the actual string may be slightly different, but it will definitely
> > contain "Zi" and it will match the " E " lines.
> >
> >
>
> OK. So I think this is something else then.
On Thu, Jul 4, 2013 at 4:19 PM, Alan Stern wrote:
>
> On Thu, 4 Jul 2013, James Stone wrote:
>
> > Apologies - I realised I hadn't also applied the 1ms usb patch. With that
> > applied, it will start OK at 256, but not at 128 frames/period. (on earlier
> > kernels it can start at 64 frames/period)
On Thu, 4 Jul 2013, Clemens Ladisch wrote:
> Alan Stern wrote:
> > On Thu, 4 Jul 2013, Ming Lei wrote:
> >>> Changing the altsetting is another way to tell the HCD that a stream is
> >>> starting fresh.
> >>
> >> Yes, it might work, but many details need to be payed attention to, such
> >> as, cha
Alan Stern wrote:
> On Thu, 4 Jul 2013, Ming Lei wrote:
>>> Changing the altsetting is another way to tell the HCD that a stream is
>>> starting fresh.
>>
>> Yes, it might work, but many details need to be payed attention to, such
>> as, changing altsetting may not be done during suspend/resume.
>
Separate the OHCI pxa27x/pxa3xx host controller driver from
ohci-hcd host code so that it can be built as a 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.kern
Separate the OHCI EP93XX host controller driver from ohci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM.
Signed-off-by: Manjunath Goudar
Cc: Arnd Bergmann
Cc: Alan Stern
Cc: Greg KH
Cc: linux-usb@vger.kernel.org
-
These patches are for separating the SOC On-Chip ohci host controller
from ohci-hcd host code into its own driver module.
This work is part of enabling multi-platform kernels on ARM.
Manjunath Goudar (2):
USB: OHCI: make ohci-ep93xx a separate driver
USB: OHCI: make ohci-pxa27x a separate driv
On 07/04/2013 06:41 PM, Sebastian Andrzej Siewior wrote:
> The am335x PHY code is well hidden in multiple places. The glue layer
> uses the nop and does up/down in the background. This patch copies the
> power on / power off part out of dsps so it can be removed later in
> dsps. At this point I am
The am335x PHY code is well hidden in multiple places. The glue layer
uses the nop and does up/down in the background. This patch copies the
power on / power off part out of dsps so it can be removed later in
dsps. At this point I am not sure if it is better to write a new phy
driver for am335x or
On Thu, 4 Jul 2013, Mariusz Grecki wrote:
> Hi all,
> I have made some experiments and things looks much more clear. Although
> I do not understand why once a time the device was initialized by Linux
> to HS operation but probably this is not so important.
> It seems that some additional configura
On Thu, 4 Jul 2013 at 14:44, Frank Schäfer wrote:
Even more interesting would be the Windows driver that has been used
for reverse-engineering. ;) AFAIK, the standard Windows driver
doesn't use the second method (last checked 2-3 years ago)...
The thread opener said he can set the non-standa
Am 04.07.2013 14:44, schrieb Frank Schäfer:
> ...
> To summarize our current knowledge:
>
> divisor = 2^A * B
>
> with
>
> A = buf[1] & 0x0E
> B = buf[0] + (buf[1] & 0x01) << 8
Update / addition:
=> for B <= 8 the device always uses the maximum value B = 512 instead
=> for 8 < B < 1
On Thu, 4 Jul 2013, James Stone wrote:
> Apologies - I realised I hadn't also applied the 1ms usb patch. With that
> applied, it will start OK at 256, but not at 128 frames/period. (on earlier
> kernels it can start at 64 frames/period).
>
> Output file (for 128 frames/period) attached.
The part
On Thu, 4 Jul 2013, Rong Wang wrote:
> Hi Greg,
>
> Thanks for your suggestion. We are trying to move to kernel-3.10.
>
> But I still have a question about EHCI which actually abstracts our question.
> I have noticed Figure 4-14. Host Controller Queue Head Traversal State Machine
> in EHCI spec.
On Thu, 4 Jul 2013, Peter Chen wrote:
> > I tried doing the same thing on a slightly modified 3.10 kernel. It
> > worked okay. But my mouse was attached to a UHCI controller rather
> > than EHCI, which may make a difference.
> >
> > Have you tried running this test with 3.10?
> >
>
> Have y
On Thu, 2013-07-04 at 13:35 +0100, Rupesh Gujare wrote:
> This patch series splits earlier patch from Joe, into smaller patches.
Please add commit messages to the patches
that are slightly more than trivial.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a
On Thu, 4 Jul 2013, Bjørn Mork wrote:
> > It may be that the device simply takes longer to resume than it should.
> > Or longer than btusb expects it to, which may not be the same thing.
>
> Yes, that is what it looks like. But the URBs are submitted as part of
> the resume callback. Shouldn'
On Thu, 4 Jul 2013, Ming Lei wrote:
> >> If so, your coming change may break ABI because as you described
> >> that "the flag should be set in the first URB of a new stream", but
> >> some user-space drivers may not set it before. Even USB audio driver
> >> doesn't set it in current -next tree.
>
On Tuesday 25 June 2013 13:20:33 Sarah Sharp wrote:
> I wonder if these webcams need a reset endpoint request sent to them,
> even though their endpoints aren't halted. The xHCI driver doesn't
> currently handle that very well. The device receives the reset endpoint
> request, but the xHCI comman
From: Wei Yongjun
free_irq() expects the same device identity that was passed to
corresponding request_irq(), otherwise the IRQ is not freed.
Signed-off-by: Wei Yongjun
---
drivers/usb/gadget/mv_u3d_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadg
On 04/07/13 13:35, Rupesh Gujare wrote:
From: Joe Perches
Pardon my ignorance, above error occurred while creating patch series.
I should had been careful about it.
--
Regards,
Rupesh Gujare
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to m
Am 04.07.2013 00:52, schrieb Reinhard Max:
> On Wed, 3 Jul 2013 at 23:35, Frank Schäfer wrote:
>
>> When I wrote the patch in 2009, only the first baud rate programming
>> method was in place.
>> The second method has been added later with commit 8d48fdf6.
>
> Hmm - it would be interesting to know
From: Joe Perches
Signed-off-by: Joe Perches
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/ozcdev.c |2 --
drivers/staging/ozwpan/ozhcd.c | 28
2 files changed, 8 insertions(+), 22 deletions(-)
diff --git a/drivers/staging/ozwpan/ozcdev.c b/driver
This patch series splits earlier patch from Joe, into smaller patches.
Joe Perches (5):
staging: ozwpan: Remove extra debug logs.
staging: ozwpan: Replace oz_trace with oz_dbg
staging: ozwpan: Remove old debug macro.
staging: ozwpan: Convert macro to function.
staging: ozwpan: Rename Kbu
From: Joe Perches
Signed-off-by: Joe Perches
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/ozurbparanoia.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/ozwpan/ozurbparanoia.h
b/drivers/staging/ozwpan/ozurbparanoia.h
index 00f5a3a..5080ea
From: Joe Perches
Signed-off-by: Joe Perches
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/Kbuild | 16
drivers/staging/ozwpan/Makefile | 16
2 files changed, 16 insertions(+), 16 deletions(-)
delete mode 100644 drivers/staging/ozwpan/Kbuild
From: Joe Perches
Signed-off-by: Joe Perches
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/Kbuild |6 ++
drivers/staging/ozwpan/ozcdev.c|2 --
drivers/staging/ozwpan/ozconfig.h | 26 ---
drivers/staging/ozwpan/ozeltbuf.c |
Hi,
On Thursday 04 July 2013 05:14 PM, Tony Lindgren wrote:
* Kishon Vijay Abraham I [130619 01:58]:
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham
* Kishon Vijay Abraham I [130619 01:58]:
> In order for controllers to get PHY in case of non dt boot, the phy
> binding information (phy label) should be added in the platform
> data of the controller.
>
> Signed-off-by: Kishon Vijay Abraham I
> Acked-by: Felipe Balbi
> Tested-by: Tomi Valkein
On Wed, Jul 03, 2013 at 12:29:08PM -0400, Alan Stern wrote:
> On Wed, 3 Jul 2013, Peter Chen wrote:
>
> > Hi Jiri and Alan,
> >
> > I have run below below at 3.5.7 kernel, but after checking upstream
> > kernel, it may also be existed.
> >
> > 1. evtest /dev/input/event1 &
> > 2. Let mouse auto
Hi
On 07/02/2013 05:03 PM, Roger Quadros wrote:
>
> On 07/02/2013 05:49 PM, Michael Trimarchi wrote:
>> Hi Roger
>>
>> On 07/02/2013 04:42 PM, Roger Quadros wrote:
>>> On 06/28/2013 07:47 PM, Michael Trimarchi wrote:
Hi
>
>
> When you said earlier that the problem doesn't happe
Hi Greg,
Thanks for your suggestion. We are trying to move to kernel-3.10.
But I still have a question about EHCI which actually abstracts our question.
I have noticed Figure 4-14. Host Controller Queue Head Traversal State Machine
in EHCI spec.
Simplified:
execute transaction ---
Alan Stern writes:
> The relative order of those two completions doesn't mean anything,
> because they are on different endpoints and they happened during the
> same frame. It just happens that uhci-hcd scans interrupt URBs before
> bulk URBs when looking for completions, but it could easily be
42 matches
Mail list logo
