On Tue, May 13, 2014 at 12:33:30AM +, Peter Chen wrote:
>
> >
> > On Sat, May 10, 2014 at 09:57:39PM +0800, Li Jun wrote:
> > > On Sat, May 10, 2014 at 09:18:36PM +0800, Shawn Guo wrote:
> > > > + Robin and David,
> > > >
> > > > diff --git a/drivers/usb/core/Kconfig b/drivers/usb/core/Kconf
On Tue, May 13, 2014 at 09:10:36AM +0800, Li Jun wrote:
> Firstly, w/o USB_OTG and USB_OTG_FSM, your OTG port will work well as before
> (i.e. it can be host or can be gadget as you want, so it's enough for you if
> connect normal usb device or PC host), I assume you are not wanting more here,
> th
On Tue, May 13, 2014 at 09:42:48AM +0800, Shawn Guo wrote:
> On Tue, May 13, 2014 at 08:25:18AM +0800, Chen Peter-B29397 wrote:
> >
> > > > >
> > > >
> > > > In your case, you should not set CONFIG_USB_OTG no matter at defconfig
> > > > and at menuconfig.
> > >
> > > Hmm, at least in my testing
> >
> > > > >
> > > >
> > > > In your case, you should not set CONFIG_USB_OTG no matter at
> > > > defconfig and at menuconfig.
> > >
> > > Hmm, at least in my testing (USB mouse/keyboard connected to OTG
> > > port), it works as before even I enable CONFIG_USB_OTG, as long as I
> > > do *not* en
On Tue, May 13, 2014 at 08:25:18AM +0800, Chen Peter-B29397 wrote:
>
> > > >
> > >
> > > In your case, you should not set CONFIG_USB_OTG no matter at defconfig
> > > and at menuconfig.
> >
> > Hmm, at least in my testing (USB mouse/keyboard connected to OTG port),
> > it works as before even I e
> > >
> >
> > In your case, you should not set CONFIG_USB_OTG no matter at defconfig
> > and at menuconfig.
>
> Hmm, at least in my testing (USB mouse/keyboard connected to OTG port),
> it works as before even I enable CONFIG_USB_OTG, as long as I do *not*
> enable CONFIG_USB_OTG_FSM.
>
> Since
>
> On Sat, May 10, 2014 at 09:57:39PM +0800, Li Jun wrote:
> > On Sat, May 10, 2014 at 09:18:36PM +0800, Shawn Guo wrote:
> > > + Robin and David,
> > >
> > > diff --git a/drivers/usb/core/Kconfig b/drivers/usb/core/Kconfig
> > > index cb8e991..9081757 100644
> > > --- a/drivers/usb/core/Kconfi
On Mon, May 12, 2014 at 09:22:33AM +0800, Chen Peter-B29397 wrote:
>
> > >
> > > So when the board is OTG & EH (CONFIG_USB_OTG is set), it should have
> > > TPL according to spec. In fact, even the CONFIG_USB_OTG_WHITELIST is
> > > not set, the non-TPL devices have not worked well, eg, it will no
On Sat, May 10, 2014 at 09:57:39PM +0800, Li Jun wrote:
> On Sat, May 10, 2014 at 09:18:36PM +0800, Shawn Guo wrote:
> > + Robin and David,
> >
> > diff --git a/drivers/usb/core/Kconfig b/drivers/usb/core/Kconfig
> > index cb8e991..9081757 100644
> > --- a/drivers/usb/core/Kconfig
> > +++ b/driver
> >
> > So when the board is OTG & EH (CONFIG_USB_OTG is set), it should have
> > TPL according to spec. In fact, even the CONFIG_USB_OTG_WHITELIST is
> > not set, the non-TPL devices have not worked well, eg, it will not be
> > enumerated again after it has disconnected from host 10 seconds late
On Sun, May 11, 2014 at 08:40:25AM +0800, Chen Peter-B29397 wrote:
> As I explained before:
> "OTG devices and Embedded Hosts both have Targeted Host functionality,
> and each Targeted Host has its TPL (Targeted Peripheral List), only the
> devices are at TPL are supported by Targeted Host."
>
>
On Sat, May 10, 2014 at 09:57:39PM +0800, Li Jun wrote:
> As Peter suggested, do not enable OTG_FSM in defconfig since there are very
> few
> HNP&SRP capable device in market. With OTG_FSM enabled, even USB_OTG_WHITELIST
> is not selected, the OTG port still can't work the same as before if you
>
>
> On Sat, May 10, 2014 at 07:10:05PM +0800, Peter Chen wrote:
> > On Fri, May 09, 2014 at 09:00:47PM +0800, Shawn Guo wrote:
> > > I'm running next-20140508 kernel on imx6q-sabresd board with USB
> > > mouse/keyboard connected to OTG port. It works well on 3.15-rc but
> > > is broken on rece
On Sat, May 10, 2014 at 09:18:36PM +0800, Shawn Guo wrote:
> + Robin and David,
>
> On Sat, May 10, 2014 at 07:10:05PM +0800, Peter Chen wrote:
> > On Fri, May 09, 2014 at 09:00:47PM +0800, Shawn Guo wrote:
> > > I'm running next-20140508 kernel on imx6q-sabresd board with USB
> > > mouse/keyboard
On Fri, May 09, 2014 at 09:00:47PM +0800, Shawn Guo wrote:
> I'm running next-20140508 kernel on imx6q-sabresd board with USB
> mouse/keyboard connected to OTG port. It works well on 3.15-rc but
> is broken on recent linux-next kernel with the message like below.
>
> ...
> usb 1-1: device v413c
+ Robin and David,
On Sat, May 10, 2014 at 07:10:05PM +0800, Peter Chen wrote:
> On Fri, May 09, 2014 at 09:00:47PM +0800, Shawn Guo wrote:
> > I'm running next-20140508 kernel on imx6q-sabresd board with USB
> > mouse/keyboard connected to OTG port. It works well on 3.15-rc but
> > is broken on
16 matches
Mail list logo
