From: Prashanth K <quic_prashk@quicinc.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7] usb: common: usb-conn-gpio: Set last role to unknown before initial detection
Date: Wed, 14 Jun 2023 09:55:10 +0530 [thread overview]
Message-ID: <73854744-03ef-2c5c-a5d6-284f004a5497@quicinc.com> (raw)
In-Reply-To: <ZIhOm5LKwn+YVGzT@kuha.fi.intel.com>
On 13-06-23 04:40 pm, Heikki Krogerus wrote:
> Hi,
>
> On Wed, May 31, 2023 at 08:11:14PM +0530, Prashanth K wrote:
>> 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.
>
> So why can't you fix this by just always setting the role
> unconditionally to USB_ROLE_NONE in your probe function before the
> initial detection?
>
Hi Heikki, thats exactly what we are doing here.
+ /* Set last role to unknown before performing the initial detection */
+ info->last_role = USB_ROLE_UNKNOWN;
+
/* Perform initial detection */
usb_conn_queue_dwork(info, 0);
Thanks,
Prashanth K
next prev parent reply other threads:[~2023-06-14 4:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:41 [PATCH v7] usb: common: usb-conn-gpio: Set last role to unknown before initial detection Prashanth K
2023-05-31 14:47 ` Prashanth K
2023-06-13 9:58 ` Greg Kroah-Hartman
2023-06-13 11:10 ` Heikki Krogerus
2023-06-14 4:25 ` Prashanth K [this message]
2023-06-14 8:36 ` Heikki Krogerus
2023-06-14 9:14 ` Heikki Krogerus
2023-06-15 9:30 ` Greg Kroah-Hartman
2023-06-15 14:22 ` Prashanth K
2023-06-15 14:36 ` Greg Kroah-Hartman
2023-06-15 14:58 ` Prashanth K
2023-06-15 15:05 ` Greg Kroah-Hartman
2023-06-15 18:11 ` Prashanth K
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=73854744-03ef-2c5c-a5d6-284f004a5497@quicinc.com \
--to=quic_prashk@quicinc.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).