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 v3] usb: common: usb-conn-gpio: Set last role to unknown before initial detection
Date: Thu, 25 May 2023 14:20:37 +0530 [thread overview]
Message-ID: <fbfc6917-d938-a055-2f58-e70a6d454ea2@quicinc.com> (raw)
In-Reply-To: <2117b7c4-d164-de17-5a2d-ef3d51304983@collabora.com>
On 25-05-23 02:15 pm, AngeloGioacchino Del Regno wrote:
> Il 25/05/23 10:40, 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
>> initialised 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>
>
> I'm sorry to make a call for v4, but you have to mention that you're
> touching
> the cdns3 driver in the commit description, if you want to keep the entire
> change set in one commit... otherwise you'll have to split it in two,
> one adding
> the new entry to the enum and fixing cdns3; the other setting the last
> role to
> unknown in usb-conn-gpio.c.
>
> I can suggest text for keeping that in one commit, but the choice is yours;
>
> "While at it, also handle default case for the usb_role switch
> in cdns3 to avoid build warnings."
>
Yea that's right, will add it in next version. Thanks for the suggestion.
Regards,
Prashanth K
prev parent reply other threads:[~2023-05-25 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 8:40 Prashanth K
2023-05-25 8:45 ` AngeloGioacchino Del Regno
2023-05-25 8:50 ` 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=fbfc6917-d938-a055-2f58-e70a6d454ea2@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®