From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT.V2] usb: xhci: Fix vendor command error if the request
Date: Sun, 06 Mar 2016 08:44:44 +0100 [thread overview]
Message-ID: <56DBDFEC.3070803@denx.de> (raw)
In-Reply-To: <CANAwSgQMNuXm-yEu3jR3ck+QcLztXqVcsKrUc1nNARpWeQ-ACw@mail.gmail.com>
On 03/05/2016 06:53 PM, Anand Moon wrote:
> Hi Marek,
Hi!
> On 5 March 2016 at 18:00, Marek Vasut <marex@denx.de> wrote:
>> On 03/05/2016 09:43 AM, Anand Moon wrote:
>>> From: Ted Chen <tedchen@realtek.com>
>>>
>>> From: Ted Chen <tedchen@realtek.com>
>>>
>>> type is USB_REQ_SET_ADDRESS or USB_REQ_SET_CONFIGURATION.
>>> To: marex at denx.de, swarren at nvidia.com, u-boot at lists.denx.de
>>> Cc: linux.amoon at gmail.com, Ted Chen <tedchen@realtek.com>
>>>
>>> Add a condition of set_address and set_configuration to check
>>> if the request is standardized.
>>
>> Can you please rephrase the commit message ? It's really hard to
>> understand. I believe such a patch will be needed for ehci as well,
>> can you prepare one ?
>
> I could not find any need for such check in ehci-hcd driver.
Please explain why this is not needed.
> Sorry for this mess in commit message, I completely missed formatting
> the statement
> because of it got warped up in the message
> Will send this message again with proper commit message.
Yes, the message is complete chaos.
>>
>>> Signed-off-by: Ted Chen <tedchen@realtek.com>
>>> ---
>>> Resend this patch it some how got missed
>>> Changes since v1: None.
>>>
>>> Tested on Odroid XU4: with Ethernet USB3.0 RT8153-VB
>>> ---
>>> drivers/usb/host/xhci.c | 6 ++++--
>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
>>> index ca598aa..cb8a04b 100644
>>> --- a/drivers/usb/host/xhci.c
>>> +++ b/drivers/usb/host/xhci.c
>>> @@ -941,10 +941,12 @@ static int _xhci_submit_control_msg(struct usb_device *udev, unsigned long pipe,
>>> if (usb_pipedevice(pipe) == ctrl->rootdev)
>>> return xhci_submit_root(udev, pipe, buffer, setup);
>>>
>>> - if (setup->request == USB_REQ_SET_ADDRESS)
>>> + if (setup->request == USB_REQ_SET_ADDRESS &&
>>> + (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD)
>>> return xhci_address_device(udev, root_portnr);
>>>
>>> - if (setup->request == USB_REQ_SET_CONFIGURATION) {
>>> + if (setup->request == USB_REQ_SET_CONFIGURATION &&
>>> + (setup->requesttype & USB_TYPE_MASK) == USB_TYPE_STANDARD) {
>>> ret = xhci_set_configuration(udev);
>>> if (ret) {
>>> puts("Failed to configure xHCI endpoint\n");
>>>
>>
>> What happens to the non-standard requests ?
>>
> Device will not able to detect leaving message
> "scanning usb for ethernet devices... Non standard request in USB
> vendor command"
Let me re-phrase, how are the non-standard requests handled ?
>> --
>> Best regards,
>> Marek Vasut
>
> Here is the modified commit message
>
> "Add a condition of set_address and set_configuration to check
> if the requesttype is of standardized in the USB vendor request
> so that usb device is detected"
Add test into xhci_submit_control_message for usb requesttype in USB
vendor request being of standardized type. This fixes detection of
certain USB fixes, for example <fill here>.
> Do you agree with this modified commit statement.
>
> Best regards,
> -Anand Moon
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-03-06 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 8:43 [U-Boot] [U-BOOT.V2] usb: xhci: Fix vendor command error if the request Anand Moon
2016-03-05 12:30 ` Marek Vasut
2016-03-05 17:53 ` Anand Moon
2016-03-06 7:44 ` Marek Vasut [this message]
2016-03-13 9:53 ` Anand Moon
2016-03-14 17:26 ` Marek Vasut
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=56DBDFEC.3070803@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.