From: Malatesh <malatesh10@gmail.com>
To: jim.cromie@gmail.com
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: work one webcam out of two webcam connect to xhci controller for 2 usb3.0 ports
Date: Wed, 19 Oct 2022 07:54:17 +0530 [thread overview]
Message-ID: <CAFK0S4YpP6rPx28530uo+RQ=DpqUMt8DaXsB6RNicv2=vXO-Wg@mail.gmail.com> (raw)
In-Reply-To: <CAJfuBxxm=mUuP0Eqt3Mx7ehuc0iVSs-ChJVGUPCJ1xfHCEk35g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 7492 bytes --]
Hi Team, This issue seems to be both webcam devices which consumes 500mA
power.
I have verified with two webcam in which one uses 500mA and one uses 244mA
so both cameras working as expected.
Is there any code changes in mainline kernel regarding usb power
consumption.
Thank you all.
Regards,
Malatesh
On Tue, 18 Oct, 2022, 11:52 pm , <jim.cromie@gmail.com> wrote:
> Let's keep this on the list.
> I'm sure I don't have Silver Bullet answers.
>
>
>
> On Tue, Oct 18, 2022, 11:15 AM Malatesh <malatesh10@gmail.com> wrote:
>
>> Hi.
>> Thank you for the interest you have shown.
>>
>>
>> - both cameras work one at a time ?
>> [A]: No. I am using one by one and not at one time both cameras
>> - does order of plugin affect which one blanks ?
>> [A]: First plugged camera will give blank and second plugged will work
>>
>
> This certainly suggests two cameras are on or plugged in at the same time.
> that contradicts your first answer
>
> - are they both the same camera model ?
>> [A]: No one is logitech and another is microsoft
>> - can you borrow a 3rd camera ?
>> [A]: Third camera works
>>
>
> I think you need to retest and permute all combinations or at least some
> of them.
>
> I suspect your application doesn't know what to do with two cameras why
> don't you try another app and see if it works. Cheese is the one on my
> desktop
>
>
>> Actual Error:
>> When I click camera preview with two camera connected, one is giving
>> error some time with "xhci_configure_reset_endpoint:4543 Error to set
>> dequeue ptr for endpoint 3, 81, err 18, 0".
>> This is because "ep status is 0 and *Endpoint is disabled".*
>>
>> Full Log:
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011861> set halted 1
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011890> real interrupt
>> (status=0x00000008)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011897> event[77] = 32
>> (0x0000000000000000 0x0c000000 0x02038000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011901> trb 0x0 status c
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011904> slot=2 epno=3
>> stream=0 remainder=0 status=12, td_event 0x0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011907> stream_id=0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011910>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011940> trb halted 1,
>> running 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011943>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011944> Ep(129) No:129
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011946> Ep ID(129to3):3
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011949> dev 2, ep address 81
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011952> xfer
>> 0xfffffe003198f148, 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011954> ep 81 is not started
>> yet
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011957> ------> epno:3, Oct
>> 18 16:35:42 WT544810D076E1 kernel: <3645.011861> set halted 1
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011890> real interrupt
>> (status=0x00000008)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011897> event[77] = 32
>> (0x0000000000000000 0x0c000000 0x02038000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011901> trb 0x0 status c
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011904> slot=2 epno=3
>> stream=0 remainder=0 status=12, td_event 0x0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011907> stream_id=0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011910>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011940> trb halted 1,
>> running 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011943>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011944> Ep(129) No:129
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011946> Ep ID(129to3):3
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011949> dev 2, ep address 81
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011952> xfer
>> 0xfffffe003198f148, 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011954> ep 81 is not started
>> yet
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011957> ------> epno:3,
>> *epstatus:0* device:2, ep_address 81
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011960> ----> *Endpoint is
>> disabled*
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011962>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011965> command[5] = 16
>> (0x0000000009891001, 0x00000000, 0x02034000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012003> real interrupt
>> (status=0x00000008)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012010> event[78] = 33
>> (0x0000000100fffdd0 0x13000000 0x02008400)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012013> Received command
>> event
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012042> trb 13000000, 2008400
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012046> src 16,
>> (0x0000000009891001, 0x00000000, 0x02034000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012051> -----> Set dequeue
>> ptr for EP No:3, EP Addr:81, EP Status:0, EP Error:18
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012057> [ERROR] -
>> xhci_configure_reset_endpoint:4543 Error to set dequeue ptr for endpoint
>> 3, 81, err 18, 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012061> ---> kick_ep 1
>> called:
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012064> endpoint is not
>> running 3, 81, 18 device:2, ep_address 81
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011960> ---->* Endpoint is
>> disabled*
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011962>
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.011965> command[5] = 16
>> (0x0000000009891001, 0x00000000, 0x02034000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012003> real interrupt
>> (status=0x00000008)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012010> event[78] = 33
>> (0x0000000100fffdd0 0x13000000 0x02008400)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012013> Received command
>> event
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012042> trb 13000000, 2008400
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012046> src 16,
>> (0x0000000009891001, 0x00000000, 0x02034000)
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012051> -----> Set dequeue
>> ptr for EP No:3, EP Addr:81, EP Status:0, EP Error:18
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012057> [ERROR] -
>> xhci_configure_reset_endpoint:4543 Error to set dequeue ptr for endpoint
>> 3, 81, err 18, 0
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012061> ---> kick_ep 1
>> called:
>>
>> Oct 18 16:35:42 WT544810D076E1 kernel: <3645.012064> endpoint is not
>> running 3, 81, 18
>>
>>
>>
>>
>>
>>
>> Regards,
>> Malatesh
>>
>>
>> On Thu, Oct 13, 2022 at 8:45 PM <jim.cromie@gmail.com> wrote:
>>
>>> On Wed, Oct 12, 2022 at 11:21 AM Malatesh <malatesh10@gmail.com> wrote:
>>> >
>>> > Hi Team,
>>> >
>>> > Good Morning/Afternoon/Evening.
>>> >
>>> > I connect two usb webcameras and one mouse, one keyboard to xhci
>>> controller, which has 4 usb v3.x ports.
>>> > Here, keyboard and mouse works fine without any issue.
>>> > But out of two cameras, only one camera works( I mean when I click
>>> preview only one camera show and one camera show blank )
>>> >
>>>
>>> lemme ask some obvious questions:
>>> - both cameras work one at a time ?
>>> - does order of plugin affect which one blanks ?
>>> - are they both the same camera model ?
>>> - can you borrow a 3rd camera ?
>>>
>>
[-- Attachment #1.2: Type: text/html, Size: 13559 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-10-19 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 17:20 work one webcam out of two webcam connect to xhci controller for 2 usb3.0 ports Malatesh
2022-10-13 15:15 ` jim.cromie
[not found] ` <CAFK0S4Z0QmjyrUMbF6z7pwpOoLUTzzRwiy3-fTZ2Kt3JjQ3LfQ@mail.gmail.com>
2022-10-18 18:22 ` jim.cromie
2022-10-19 2:24 ` Malatesh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFK0S4YpP6rPx28530uo+RQ=DpqUMt8DaXsB6RNicv2=vXO-Wg@mail.gmail.com' \
--to=malatesh10@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).