linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bin Liu <b-liu@ti.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
	Apelete Seketeli <apelete@seketeli.net>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [RFC] musb: removing otg protocol support
Date: Mon, 19 Mar 2018 09:24:26 -0500	[thread overview]
Message-ID: <20180319142426.GQ14921@uda0271908> (raw)

On Sun, Mar 18, 2018 at 05:36:10PM +0100, Hans de Goede wrote:
> Hi,
> 
> On 18-03-18 14:16, Greg Kroah-Hartman wrote:
> >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?
> 
> I'm not aware of any hardware using the fancier otg functions such as
> role-swapping, etc. either. From an Allwinner pov as long as you keep

Thanks for confirming ;)

> plain gadget and host mode as controlled by the id pin work, I'm happy.

Yes, this is not changed.

> Note I'm not really involved in Allwinnner stuff anymore, so if you
> want some testing of the cleanup, you should probably ask the
> free-electron (now bootlin.com) people.

Thanks, but I am not sure how I can find the exact individual contects.

Regards,
-Bin.
---
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

             reply	other threads:[~2018-03-19 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 14:24 Bin Liu [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:20 Bin Liu
2018-03-18 16:36 Hans de Goede
2018-03-18 13:16 Greg Kroah-Hartman
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=20180319142426.GQ14921@uda0271908 \
    --to=b-liu@ti.com \
    --cc=apelete@seketeli.net \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).