From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bin Liu <b-liu@ti.com>,
linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Apelete Seketeli <apelete@seketeli.net>,
Hans de Goede <hdegoede@redhat.com>,
Mian Yousaf Kaukab <mian.yousaf.kaukab@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>,
Fabio Baltieri <fabio.baltieri@linaro.org>
Subject: [RFC] musb: removing otg protocol support
Date: Sun, 18 Mar 2018 14:16:25 +0100 [thread overview]
Message-ID: <20180318131625.GE20139@kroah.com> (raw)
On Fri, Mar 16, 2018 at 02:09:51PM -0500, Bin Liu wrote:
> Hi,
>
> The kernel usb stack and musb drivers have gone through some changes in
> the past several kernel versions, such as adding otg fsm, musb runtime
> PM, and musb otg state moving from musb to musb->xceiv... I am wondering
> if the otg protocol (hnp, srp) functions are already broken in the musb
> drivers, but I don't have a platform to confirm it.
>
> Do we know by any chance there is still someone using the musb otg
> functions in any relatively newer kernel and we still need to support
> otg in musb? If not, I am thinking to clean up the otg functions in
> musb drivers to make the code easy to read and maintain.
By "clean up" do you mean "delete it"? :)
I don't know of any real OTG hardware that ever shipped, does anyone
else?
> If we can make the conclusion to remove it, I propose the patch below
> to disable musb otg first, then clean up the driver later if nobody
> complains about the otg function removal.
It will take years for people who make these types of devices to notice
that OTG is removed, so be careful about this. Refactor away, but
watch out you don't break someone's stuff and get told about it in 2
years :(
good luck!
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-03-18 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 13:16 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-19 14:59 [RFC] musb: removing otg protocol support Bin Liu
2018-03-19 14:40 Greg Kroah-Hartman
2018-03-19 14:24 Bin Liu
2018-03-19 14:20 Bin Liu
2018-03-18 16:36 Hans de Goede
2018-03-16 19:09 Bin Liu
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=20180318131625.GE20139@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apelete@seketeli.net \
--cc=b-liu@ti.com \
--cc=balbi@kernel.org \
--cc=fabio.baltieri@linaro.org \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=mian.yousaf.kaukab@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.