On Wed, Feb 6, 2019 at 5:16 PM Frank Mori Hess wrote:
>
> Hi Minas,
>
> On Tue, Feb 5, 2019 at 5:22 AM Minas Harutyunyan
> wrote:
> > Could you please try patch submitted by me today:"[PATCH] usb: dwc2:
> > gadget: Consider VBUS discharge time in disconnect flow
Hi Minas,
On Tue, Feb 5, 2019 at 5:22 AM Minas Harutyunyan
wrote:
> Could you please try patch submitted by me today:"[PATCH] usb: dwc2:
> gadget: Consider VBUS discharge time in disconnect flow"
I should be able to try it tonight or tomorrow to see if it makes the
driver recognize a cable disco
On Tue, Dec 25, 2018 at 2:12 AM Minas Harutyunyan
wrote:
> On 12/24/2018 7:04 PM, Frank Mori Hess wrote:
> > On Mon, Dec 24, 2018 at 12:41 AM Minas Harutyunyan
> >> You didn't see dummy USBRst interrupt on disconnect, follow to above
> >> interrupts?
> &g
Hi Minas,
On Mon, Dec 24, 2018 at 12:41 AM Minas Harutyunyan
wrote:
>
> >
> > With DEBUG defined in dwc2/core_intr.c I get:
> >
> > #unplugging
> > [ 364.111260] dwc2 ffb0.usb: GINTSTS_ErlySusp
> > [ 364.115831] dwc2 ffb0.usb: gintsts=04008828 gintmsk=d08c3cc4
> > [ 364.121906] dwc2 f
>
> According data book Disconnect Interrupt asserted only in Host mode.
> Programming guide says for device initialization unmask follow device
> specific interrupts: USB reset, Enum Done, Early suspend, Suspend and SOF.
> And on device disconnect asserted interrupts:
> - In OTG_MODE=0,1,3: GOTGIN
On Fri, Dec 21, 2018 at 6:01 AM Minas Harutyunyan
wrote:
>
> According data book Disconnect Interrupt asserted only in Host mode.
> Programming guide says for device initialization unmask follow device
> specific interrupts: USB reset, Enum Done, Early suspend, Suspend and SOF.
> And on device di
On Thu, Dec 20, 2018 at 2:12 AM Felipe Balbi wrote:
>
> You're using a really old kernel. Please try with v4.19.11 or v4.20-rc7
>
I have to use an altera patched kernel linux-socfpga to boot my board,
and it always lags behind mainline kernel. If I really had to, I can
probably backport an indiv
Hi Felipe,
I'm using a usb composite gadget (g_serial) and it initially has a
sysfs attribute "suspended" which is zero. When I physically unplug
the usb cable, the "suspend" callback is called and the "suspended"
attribute becomes 1. However, when I plug the gadget back in, the
"reset" callback
