* Yegor Yefremov [191021 01:40]:
> Hi Tony,
>
> On Thu, Oct 3, 2019 at 10:39 AM Yegor Yefremov
> wrote:
> >
> > Hi Tony,
> >
> > On Wed, Oct 2, 2019 at 6:52 PM Tony Lindgren wrote:
> > >
> > > * Yegor Yefremov [191002 06:57]:
> > > > On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > >
Hi Tony,
On Thu, Oct 3, 2019 at 10:39 AM Yegor Yefremov
wrote:
>
> Hi Tony,
>
> On Wed, Oct 2, 2019 at 6:52 PM Tony Lindgren wrote:
> >
> > * Yegor Yefremov [191002 06:57]:
> > > On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > > > The other way to fix this would be to just wake up cpp
Hi Tony,
On Wed, Oct 2, 2019 at 6:52 PM Tony Lindgren wrote:
>
> * Yegor Yefremov [191002 06:57]:
> > On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > > The other way to fix this would be to just wake up cpp41 in
> > > cppi41_dma_prep_slave_sg() and return NULL so that we can
> > > have
* Yegor Yefremov [191002 06:57]:
> On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
> > The other way to fix this would be to just wake up cpp41 in
> > cppi41_dma_prep_slave_sg() and return NULL so that we can
> > have musb_ep_program() continue with PIO while cppi41 is
> > asleep.
> >
> > An
On Wed, Oct 2, 2019 at 12:03 AM Tony Lindgren wrote:
>
> Hi,
>
> * Tony Lindgren [191001 16:52]:
> > * Yegor Yefremov [191001 09:20]:
> > > I've tried to increase the autosuspend_delay_ms and to set control to
> > > "on" but nothing changes. Below you can see the output of my testing
> > > scrip
Hi,
* Tony Lindgren [191001 16:52]:
> * Yegor Yefremov [191001 09:20]:
> > I've tried to increase the autosuspend_delay_ms and to set control to
> > "on" but nothing changes. Below you can see the output of my testing
> > script [1] (Py2 only). As one can see, the first cycle i.e. after the
> >
* Yegor Yefremov [191001 09:20]:
> On Tue, Oct 1, 2019 at 10:03 AM Johan Hovold wrote:
> >
> > On Mon, Sep 30, 2019 at 09:54:11PM +0200, Sebastian Reichel wrote:
> > > Hi,
> > >
> > > On Mon, Sep 30, 2019 at 08:23:30AM -0700, Tony Lindgren wrote:
> >
> > > > Actually playing with the cppi41 timeo
On Tue, Oct 1, 2019 at 10:03 AM Johan Hovold wrote:
>
> On Mon, Sep 30, 2019 at 09:54:11PM +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > On Mon, Sep 30, 2019 at 08:23:30AM -0700, Tony Lindgren wrote:
>
> > > Actually playing with the cppi41 timeout might be more suitable here,
> > > they use the
On Mon, Sep 30, 2019 at 09:54:11PM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Sep 30, 2019 at 08:23:30AM -0700, Tony Lindgren wrote:
> > Actually playing with the cppi41 timeout might be more suitable here,
> > they use the same module clock from what I remember though. So
> > maybe increa
Hi,
On Mon, Sep 30, 2019 at 08:23:30AM -0700, Tony Lindgren wrote:
> * Tony Lindgren [190930 14:57]:
> > * Yegor Yefremov [190930 08:20]:
> > > On Mon, Sep 30, 2019 at 8:59 AM Yegor Yefremov
> > > wrote:
> > > >
> > > > On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
> > > > wrote:
> > > > >
>
* Tony Lindgren [190930 14:57]:
> * Yegor Yefremov [190930 08:20]:
> > On Mon, Sep 30, 2019 at 8:59 AM Yegor Yefremov
> > wrote:
> > >
> > > On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
> > > wrote:
> > > >
> > > > On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> > > > > Looks like I'm
* Yegor Yefremov [190930 08:20]:
> On Mon, Sep 30, 2019 at 8:59 AM Yegor Yefremov
> wrote:
> >
> > On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
> > wrote:
> > >
> > > On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> > > > Looks like I'm unable to reproduce this with bbb and FT232R
> > >
On Mon, Sep 30, 2019 at 8:59 AM Yegor Yefremov
wrote:
>
> On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
> wrote:
> >
> > On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> > >
> > > * Tony Lindgren [190927 15:20]:
> > > > * Yegor Yefremov [190927 12:31]:
> > > > > On Fri, Sep 27, 2019 at
On Sat, Sep 28, 2019 at 6:09 PM Yegor Yefremov
wrote:
>
> On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
> >
> > * Tony Lindgren [190927 15:20]:
> > > * Yegor Yefremov [190927 12:31]:
> > > > On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
> > > > wrote:
> > > > >
> > > > > I was porting
On Fri, Sep 27, 2019 at 5:57 PM Tony Lindgren wrote:
>
> * Tony Lindgren [190927 15:20]:
> > * Yegor Yefremov [190927 12:31]:
> > > On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
> > > wrote:
> > > >
> > > > I was porting my system from 3.18/4.2 to 5.3. During this process I
> > > > noticed th
* Tony Lindgren [190927 15:20]:
> * Yegor Yefremov [190927 12:31]:
> > On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
> > wrote:
> > >
> > > I was porting my system from 3.18/4.2 to 5.3. During this process I
> > > noticed that FT4232 that is attached directly to musb is not working
> > > corre
* Yegor Yefremov [190927 12:31]:
> On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
> wrote:
> >
> > I was porting my system from 3.18/4.2 to 5.3. During this process I
> > noticed that FT4232 that is attached directly to musb is not working
> > correctly when opened for the first time: tx is work
On Fri, Sep 27, 2019 at 10:18 AM Yegor Yefremov
wrote:
>
> I was porting my system from 3.18/4.2 to 5.3. During this process I
> noticed that FT4232 that is attached directly to musb is not working
> correctly when opened for the first time: tx is working but nothing
> can be received. On the seco
I was porting my system from 3.18/4.2 to 5.3. During this process I
noticed that FT4232 that is attached directly to musb is not working
correctly when opened for the first time: tx is working but nothing
can be received. On the second opening everything is working fine.
When the same chip is conne
19 matches
Mail list logo
