[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59ef67eabf72450f988638edbbe1cd47@BL2PR03MB579.namprd03.prod.outlook.com>
Date: Thu, 8 May 2014 14:30:39 +0000
From: "suresh.gupta@...escale.com" <suresh.gupta@...escale.com>
To: "suresh.gupta@...escale.com" <suresh.gupta@...escale.com>,
"balbi@...com" <balbi@...com>, Paul Fertser <fercerpav@...il.com>
CC: "LeoLi@...escale.com" <LeoLi@...escale.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] usb: gadget: fsl: check vbus presence on probe
Hi,
As per my limited knowledge, the purpose of OTGSC_STS_B_SESSION_VALID bit is to tell either VBUS is above the B session valid threshold and which comes only Host is attached.
And Host might be attach after system bootup or after driver initialization. So putting this check in probe will not help much.
> -----Original Message-----
> From: linux-usb-owner@...r.kernel.org [mailto:linux-usb-
> owner@...r.kernel.org] On Behalf Of suresh.gupta@...escale.com
> Sent: Thursday, May 01, 2014 7:58 PM
> To: balbi@...com; Paul Fertser
> Cc: Li Yang-Leo-R58472; linux-usb@...r.kernel.org; linux-
> kernel@...r.kernel.org
> Subject: RE: [PATCH] usb: gadget: fsl: check vbus presence on probe
>
> Give me some time (actually some days), I will try this and update you.
>
> > -----Original Message-----
> > From: Felipe Balbi [mailto:balbi@...com]
> > Sent: Thursday, May 01, 2014 1:42 AM
> > To: Paul Fertser
> > Cc: Felipe Balbi; Li Yang-Leo-R58472; linux-usb@...r.kernel.org;
> > linux- kernel@...r.kernel.org; Gupta Suresh-B42813
> > Subject: Re: [PATCH] usb: gadget: fsl: check vbus presence on probe
> >
> > +Suresh
> >
> > (top-posting, yeah yeah :-)
> >
> > On Wed, Apr 30, 2014 at 11:27:45PM +0400, Paul Fertser wrote:
> > > Hello,
> > >
> > > Thank you for the review.
> > >
> > > On Wed, Apr 30, 2014 at 11:06:25AM -0500, Felipe Balbi wrote:
> > > > On Thu, Apr 24, 2014 at 12:54:13PM +0400, Paul Fertser wrote:
> > > > > If VBUS is already present during the driver initialisation, the
> > > >
> > > > s/initialisation/initialization
> > >
> > > If I'm understanding [1] properly, both spelling variants are
> correct.
> > >
> > > > > + /* Now let it settle a bit and sense VBUS */
> > > > > + msleep_interruptible(1);
> > > > > + if (fsl_readl(&dr_regs->otgsc) & OTGSC_STS_B_SESSION_VALID)
> > > > > + udc_controller->vbus_active = 1;
> > > >
> > > > good fix, should this go to stable ?
> > >
> > > I was reluctant to Cc stable because I'm not sure which versions
> > > need to be fixed, as I've seen an earlier version (3.0 something or
> > > a bit before that probably) working without this (no idea why); also
> > > I'm not sure about that msleep as it's deduced solely from
> > > experimenting with a particular i.MX model, I hoped someone from
> > > Freescale would comment on it. I've seen your review [2] on a
> > > related patch and my fix should have been obvious to Suresh (and
> > > trivial to test on different boards), yet he didn't implement it,
> that worries me a bit.
> > >
> > > [1]
> > > https://en.wikipedia.org/wiki/American_and_British_English_spelling_
> > > di
> > > fferences#-ise.2C_-ize_.28-isation.2C_-ization.29
> > > [2] https://patchwork.kernel.org/patch/3822321/
> > > --
> > > Be free, use free (http://www.gnu.org/philosophy/free-sw.html)
> > software!
> > > mailto:fercerpav@...il.com
> >
> > --
> > balbi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@...r.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists