From: Prashanth K <quic_prashk@quicinc.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: common: usb-conn-gpio: Set last role to unknown before initial detection
Date: Thu, 25 May 2023 13:57:50 +0530 [thread overview]
Message-ID: <05ff6015-aecf-8fb4-ee29-ea7b37060a13@quicinc.com> (raw)
In-Reply-To: <64825178-2310-8c8a-2ed9-4ae14a46915e@collabora.com>
On 25-05-23 01:37 pm, AngeloGioacchino Del Regno wrote:
> Il 24/05/23 15:50, Prashanth K ha scritto:
>> Currently if we bootup a device without cable connected, then
>> usb-conn-gpio won't call set_role() since last_role is same as
>> current role. This happens because during probe last_role gets
>> initialized to zero.
>>
>> To avoid this, added a new constant in enum usb_role, last_role
>> is set to USB_ROLE_UNKNOWN before performing initial detection.
>>
>> Fixes: 4602f3bff266 ("usb: common: add USB GPIO based connection
>> detection driver")
>> Signed-off-by: Prashanth K <quic_prashk@quicinc.com>
>
> There's an issue with drivers/usb/cdns3/core.c as pointed out by the
> test robot; the solution is to handle `default` in the switch, I'd say
> that it would be safe to handle it as
>
> default:
> break;
>
> after solving that:
>
> Reviewed-by: AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com>
Yea sure, thanks for the suggestion Agnelo
Regards,
Prashanth K
prev parent reply other threads:[~2023-05-25 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 13:50 Prashanth K
2023-05-24 20:07 ` kernel test robot
2023-05-25 6:57 ` Chunfeng Yun (云春峰)
2023-05-25 8:26 ` Prashanth K
2023-05-25 8:07 ` AngeloGioacchino Del Regno
2023-05-25 8:27 ` Prashanth K [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=05ff6015-aecf-8fb4-ee29-ea7b37060a13@quicinc.com \
--to=quic_prashk@quicinc.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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
all inboxes | Powered by JetHome®