From: Prashanth K <quic_prashk@quicinc.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: 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, 31 May 2023 20:17:23 +0530 [thread overview]
Message-ID: <665be8f7-0892-3446-72ca-4c45457c9153@quicinc.com> (raw)
In-Reply-To: <1685544074-17337-1-git-send-email-quic_prashk@quicinc.com>
On 31-05-23 08:11 pm, Prashanth K wrote:
>
> diff --git a/drivers/usb/musb/jz4740.c b/drivers/usb/musb/jz4740.c
> index 5aabdd7..6d880c4 100644
> --- a/drivers/usb/musb/jz4740.c
> +++ b/drivers/usb/musb/jz4740.c
> @@ -95,6 +95,8 @@ static int jz4740_musb_role_switch_set(struct usb_role_switch *sw,
> case USB_ROLE_HOST:
> atomic_notifier_call_chain(&phy->notifier, USB_EVENT_ID, phy);
> break;
> + default:
> + break;
> }
>
> return 0;
> diff --git a/drivers/usb/roles/intel-xhci-usb-role-switch.c b/drivers/usb/roles/intel-xhci-usb-role-switch.c
> index 5c96e92..4d6a3dd 100644
> --- a/drivers/usb/roles/intel-xhci-usb-role-switch.c
> +++ b/drivers/usb/roles/intel-xhci-usb-role-switch.c
> @@ -97,6 +97,8 @@ static int intel_xhci_usb_set_role(struct usb_role_switch *sw,
> val |= SW_VBUS_VALID;
> drd_config = DRD_CONFIG_STATIC_DEVICE;
> break;
> + default:
> + break;
> }
> val |= SW_IDPIN_EN;
> if (data->enable_sw_switch) {
> diff --git a/include/linux/usb/role.h b/include/linux/usb/role.h
> index b5deafd..65e790a 100644
> --- a/include/linux/usb/role.h
> +++ b/include/linux/usb/role.h
> @@ -11,6 +11,7 @@ enum usb_role {
> USB_ROLE_NONE,
> USB_ROLE_HOST,
> USB_ROLE_DEVICE,
> + USB_ROLE_UNKNOWN,
> };
>
> typedef int (*usb_role_switch_set_t)(struct usb_role_switch *sw,
Hi Greg, I have fixed the drivers that doesn't have default case while
using usb_role enum. Added the same on intel-xhci-usb-role-switch.c &
musb/jz4740.c files. I was able to compile successfully. Please check
once if this fixed the build issue.
Thanks in advance,
Prashanth K
next prev parent reply other threads:[~2023-05-31 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:41 Prashanth K
2023-05-31 14:47 ` Prashanth K [this message]
2023-06-13 9:58 ` Greg Kroah-Hartman
2023-06-13 11:10 ` Heikki Krogerus
2023-06-14 4:25 ` Prashanth K
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=665be8f7-0892-3446-72ca-4c45457c9153@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®