On Mon, Aug 20, 2018 at 4:23 PM Alan Stern wrote:
> It is expected. No notifications for host-initiated ejects were ever
> put into the f_mass_storage driver.
>
> I have never tried to use f_mass_storage under configfs. When you do,
> does the driver create its normal sysfs files?
Is there any
On Sat, 25 Aug 2018, Paul Menzel wrote:
> Dear Alan,
>
>
> Am 03.07.2018 um 20:40 schrieb Alan Stern:
> > I no longer have suitable hardware for testing this patch. If anyone
> > with an OHCI host controller could try it out, I would like to hear if
> > it causes any problems.
>
> Do you
On Tue, 28 Aug 2018, Nuno Gonçalves wrote:
> On Mon, Aug 20, 2018 at 4:23 PM Alan Stern wrote:
> > It is expected. No notifications for host-initiated ejects were ever
> > put into the f_mass_storage driver.
> >
> > I have never tried to use f_mass_storage under configfs. When you do,
> > does
Paul pointed out that the 50-ms sleep during OHCI initialization takes
up a large fraction of a system's boot time. Things get worse when
there are two OHCI controllers present, each requiring 50 ms.
However, there really is no need to send a 50-ms reset signal out all
the root-hub ports during
Hi,
On Tue, Aug 28, 2018 at 11:04 AM, Terin Stock wrote:
>> It would also be good to document what device you were plugging in
>> that you were having problems with and what system you were running
>> on. That would help someone else if they ever wanted to modify the
>> same area of code and
Hi,
On Sat, Aug 25, 2018 at 8:45 PM, Terin Stock wrote:
> Upon upgrading a Raspberry Pi 3B-based project from vanilla 4.14,
> attempts to mount a floppy disk in a generic USB floppy drive would hang
> until the floppy drive was removed from the system.
>
> Tracing shows that during mounting the
Thanks Alan and Doug for your feedback. They've both been extremely helpful
in understanding what you're looking for in messages. A few responses below.
> I think your commit will be more compelling with additional data. As
> Allen says it looks like you're not actually changing the delay. You
> Add compatibility for extcon-usb-gpio which can handle more than one cable per
> instance, allowing coherency of USB cable states (USB/USB-HOST). These states
> can be generated from ID or/and VBUS pins.
>
> In case only one extcon device is associated to the USB device, and this
> device
>
> USB role (host/device), this can be an update of the pins routing or a simple
> GPIO
> value change.
>
> This patch introduces new optional "host" and "device" pinctrls.
> If these pinctrls are defined by the device, they are respectively selected on
> host/device role start.
>
>
