From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Prashanth K <quic_prashk@quicinc.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] usb: common: usb-conn-gpio: Set last role to unknown before initial detection
Date: Wed, 24 May 2023 11:40:15 +0200 [thread overview]
Message-ID: <ebbbee51-8792-6c35-c29b-adb7f83dda23@collabora.com> (raw)
In-Reply-To: <1684918441-14794-1-git-send-email-quic_prashk@quicinc.com>
Il 24/05/23 10:54, 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, last_role is set to USB_ROLE_UNKNOWN before
> performing the initial detection.
>
> Fixes: 4602f3bff266 ("usb: common: add USB GPIO based connection detection driver")
> Signed-off-by: Prashanth K <quic_prashk@quicinc.com>
> ---
> drivers/usb/common/usb-conn-gpio.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/usb/common/usb-conn-gpio.c b/drivers/usb/common/usb-conn-gpio.c
> index e20874c..00af735 100644
> --- a/drivers/usb/common/usb-conn-gpio.c
> +++ b/drivers/usb/common/usb-conn-gpio.c
> @@ -27,6 +27,8 @@
> #define USB_CONN_IRQF \
> (IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING | IRQF_ONESHOT)
>
> +#define USB_ROLE_UNKNOWN -1
I would add USB_ROLE_UNKNOWN to `enum usb_role` instead.
enum usb_role {
USB_ROLE_UNKNOWN = -1,
USB_ROLE_NONE,
....
};
Regards,
Angelo
> +
> struct usb_conn_info {
> struct device *dev;
> struct usb_role_switch *role_sw;
> @@ -257,6 +259,9 @@ static int usb_conn_probe(struct platform_device *pdev)
> platform_set_drvdata(pdev, info);
> device_set_wakeup_capable(&pdev->dev, true);
>
> + /* 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);
>
next prev parent reply other threads:[~2023-05-24 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 8:54 Prashanth K
2023-05-24 9:40 ` AngeloGioacchino Del Regno [this message]
2023-05-24 13:36 ` 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=ebbbee51-8792-6c35-c29b-adb7f83dda23@collabora.com \
--to=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 \
--cc=quic_prashk@quicinc.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®