From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, Greg KH <greg@kroah.com>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Subject: [v4,2/2] usb/gadget: Add driver for Aspeed SoC virtual hub
Date: Tue, 20 Mar 2018 15:36:38 +1100 [thread overview]
Message-ID: <1521520598.16434.240.camel@kernel.crashing.org> (raw)
On Sat, 2018-03-17 at 09:50 -0400, Alan Stern wrote:
> On Sat, 17 Mar 2018, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2018-03-16 at 16:56 -0400, Alan Stern wrote:
> > > On Fri, 16 Mar 2018, Benjamin Herrenschmidt wrote:
> > >
> > > > On Thu, 2018-03-15 at 08:03 +1100, Benjamin Herrenschmidt wrote:
> > > > > > > Do you have more comments for the rest of the driver or that's it ?
> > > > > >
> > > > > > so far, that's it.
> > > > >
> > > > > Ok. I'll re-send.
> > > >
> > > > So I'll resend in a minute, doing a few more tests, however, I've
> > > > noticed something which I wont' have time to track down til at
> > > > best next week, I wonder if it's normal/expected.
> > > >
> > > > If I just create a mass storage function set to be "removable" and
> > > > "cdrom" with no file attached, and enable it, I get an endless stream
> > > > of resets. It looks like the host constantly does USB resets.
> > >
> > > That's not why I get. There's an endless stream of messages, but it
> > > doesn't include any resets. Just command failures and endpoint halts.
> > > For example:
> >
> > .../...
> >
> > In my case, I was getting resets on the host:
>
.../...
> Output from usbmon could help.
So that ended up being a bug in my UDC driver. For IN requests I had a
problem with 0-length requests when enabling the multi-descriptor mode
in the EP which seems to affect some MODE_SENSE responses among others.
I fixed that and now see only the silent errors you mentioned.
Felipe, I'll send a respin of the driver with a fix tomorrow.
.../...
> Maybe... Even after cdrom support was added to the gadget, the scope
> was limited. It was intended to emulate _only_ a CD drive, not a DVD
> drive.
>
> Also, if I'm not mistaken, the commands that the emulation doesn't
> handle are all optional.
Right. One low hanging fruit seems to be
GET_EVENT_STATUS_NOTIFICATION (0x4a). I'll look into it in my copious
spare time ;-)
There are a few more, which as long as we only support "read only"
CD/DVD should be fairly easy to deal with.
Cheers,
Ben.
> Alan Stern
>
> > The Aspeed chip is a BMC chip, ie server management processor, and is
> > connected via the USB gadget to the actual server (the host). One of
> > the usage scenario here is to use USB gadget to present distro ISOs as
> > USB CD/DVDs to the host for remote provisioning (sourced over the
> > network via something like nbd).
> >
> > Note that due to the limitation of having to use a file or a block
> > device, we might end up doing a userspace CDROM emulation instead that
> > can source ISOs via things like HTTPS instead, but initially the above
> > is what we are toying with.
> >
> > Cheers,
> > Ben.
---
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-20 4:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 4:36 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-17 13:50 [v4,2/2] usb/gadget: Add driver for Aspeed SoC virtual hub Alan Stern
2018-03-17 0:40 Benjamin Herrenschmidt
2018-03-17 0:38 Benjamin Herrenschmidt
2018-03-17 0:29 Benjamin Herrenschmidt
2018-03-16 20:56 Alan Stern
2018-03-16 7:23 Felipe Balbi
2018-03-16 0:40 Benjamin Herrenschmidt
2018-03-14 21:03 Benjamin Herrenschmidt
2018-03-14 8:54 Felipe Balbi
2018-03-14 3:53 Benjamin Herrenschmidt
2018-03-12 22:35 Benjamin Herrenschmidt
2018-03-09 9:20 Felipe Balbi
2018-01-26 0:01 Benjamin Herrenschmidt
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=1521520598.16434.240.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=balbi@kernel.org \
--cc=greg@kroah.com \
--cc=joel@jms.id.au \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.