On Thu, 18 Oct 2012, vikram pandita wrote:
> >> Why on enable/disable would we not want to ensure PSS state is same as PSE?
> >
> > Because it would be a waste of time. Eventually the controller will
> > set PSS equal to PSE; why should the driver wait for it? The driver
> > can go on to do othe
Alan
On 10/18/2012 09:02 AM, Alan Stern wrote:
On Wed, 17 Oct 2012, vikram pandita wrote:
Alan
I was looking at your implementation [1] on Periodic schedule
enable/disable using hrtimer.
Looks really neat.
Thank you.
Current implementation is:
On Periodic Enable, Sate is: PSE =1 , PS
On Wed, 17 Oct 2012, vikram pandita wrote:
>
> Alan
> I was looking at your implementation [1] on Periodic schedule
> enable/disable using hrtimer.
> Looks really neat.
Thank you.
> Current implementation is:
> On Periodic Enable, Sate is: PSE =1 , PSS dont care - will be set
> automatica
Alan
I was looking at your implementation [1] on Periodic schedule
enable/disable using hrtimer.
Looks really neat.
Current implementation is:
On Periodic Enable, Sate is: PSE =1 , PSS dont care - will be set
automatically after > 7 microframes time
On Periodic Disable, Sate is: PSE =0 ,
