From: Neel Chakraborty <neelchakrabortykernelwork@gmail.com>
To: b-liu@ti.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neel Chakraborty <neelchakrabortykernelwork@gmail.com>
Subject: [PATCH] drivers: usb: musb: musb_gadget: Removed unneeded code
Date: Tue, 6 Jun 2023 15:50:58 +0530 [thread overview]
Message-ID: <20230606102058.1010324-1-neelchakrabortykernelwork@gmail.com> (raw)
Removed the static int musb_gadget_vbus_session function as it was
doing nothing.It has reduced 13 lines of code
Signed-off-by: Neel Chakraborty <neelchakrabortykernelwork@gmail.com>
---
drivers/usb/musb/musb_gadget.c | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
index 31c44325e828..3cb7fc4c84ed 100644
--- a/drivers/usb/musb/musb_gadget.c
+++ b/drivers/usb/musb/musb_gadget.c
@@ -1612,19 +1612,6 @@ static void musb_pullup(struct musb *musb, int is_on)
musb_writeb(musb->mregs, MUSB_POWER, power);
}
-#if 0
-static int musb_gadget_vbus_session(struct usb_gadget *gadget, int is_active)
-{
- musb_dbg(musb, "<= %s =>\n", __func__);
-
- /*
- * FIXME iff driver's softconnect flag is set (as it is during probe,
- * though that can clear it), just musb_pullup().
- */
-
- return -EINVAL;
-}
-#endif
static int musb_gadget_vbus_draw(struct usb_gadget *gadget, unsigned mA)
{
--
2.40.1
next reply other threads:[~2023-06-06 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:20 Neel Chakraborty [this message]
2023-06-06 10:31 ` [PATCH] drivers: usb: musb: musb_gadget: Removed unneeded code Greg KH
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=20230606102058.1010324-1-neelchakrabortykernelwork@gmail.com \
--to=neelchakrabortykernelwork@gmail.com \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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