Dear Simon Glass,
> Hi Julius,
>
> On Mon, Sep 23, 2013 at 8:55 PM, Julius Werner wrote:
> > Hi Simon,
> >
> > > It seems like you could do something like
> > >
> > > /*
> > >
> > > * This is the delay for ...the spec requires a minimum of ...
> > > */
> > >
> > > #define SOME_SUITABLE_NAM
Hi Julius,
On Mon, Sep 23, 2013 at 8:55 PM, Julius Werner wrote:
> Hi Simon,
>
> > It seems like you could do something like
> >
> > /*
> > * This is the delay for ...the spec requires a minimum of ...
> > */
> > #define SOME_SUITABLE_NAME 8000
> >
> > at the top of the file and then use it tw
Hi Simon,
> It seems like you could do something like
>
> /*
> * This is the delay for ...the spec requires a minimum of ...
> */
> #define SOME_SUITABLE_NAME 8000
>
> at the top of the file and then use it twice in your function.
The file contains a dozen handshake() calls that have a literal
Hi Julius,
On Thu, Sep 19, 2013 at 7:39 PM, Julius Werner wrote:
> Hello Marek,
>
> 8 seemed like a reasonable value. It is not the only possible one. As
> I said, the spec requires a minimum of 4.125 (125us to make sure the
> current microframe finishes, and 16 * 125us to wait for the 16 full
Hello Marek,
8 seemed like a reasonable value. It is not the only possible one. As
I said, the spec requires a minimum of 4.125 (125us to make sure the
current microframe finishes, and 16 * 125us to wait for the 16 full
microframes listed on page 20). 8 fulfills that constraint and leaves
a little
Dear Julius Werner,
> > Why 8 * 1000? It's not clear.
>
> I am not quite sure to be honest... it's been a while since I actually
> wrote this patch. The EHCI spec gives no clear max for the
> Periodic/Async Schedule disable (I assume not more than a frame,
> though), and says the Run/Stop bit mus
> Why 8 * 1000? It's not clear.
I am not quite sure to be honest... it's been a while since I actually
wrote this patch. The EHCI spec gives no clear max for the
Periodic/Async Schedule disable (I assume not more than a frame,
though), and says the Run/Stop bit must halt within 16 microframes
(whi
Dear Julius Werner,
> The EHCI controller has some very specific requirements for the USB 2.0
> port test modes, which were not closely followed in the initial test
> mode commit. It demands that the host controller is completely shut down
> (all ports suspended, Run/Stop bit unset) when activatin
Hi,
On Tue, Sep 17, 2013 at 6:29 PM, Julius Werner wrote:
> The EHCI controller has some very specific requirements for the USB 2.0
> port test modes, which were not closely followed in the initial test
> mode commit. It demands that the host controller is completely shut down
> (all ports suspe
The EHCI controller has some very specific requirements for the USB 2.0
port test modes, which were not closely followed in the initial test
mode commit. It demands that the host controller is completely shut down
(all ports suspended, Run/Stop bit unset) when activating test mode, and
will not wor
10 matches
Mail list logo
