2008-07-25 10:50:48     system ticks

Document created by Aaronwu Employee on Aug 7, 2013
Version 1Show Document
  • View in full screen mode

2008-07-25 10:50:48     system ticks

Appalayagari Sreedhar (INDIA)

Message: 59406   

 

Hi,

 

I need to get the system ticks since systemboot from reset, there is an API in VDK VDK_Getuptime();

 

I tried using the gettimeofday function, it is saying undefined reference for me, i think i am missing something/doing silly can anyone help me how to get the system ticks.

 

Best Regards,Sreedhar.

QuoteReplyEditDelete

 

 

2008-07-25 11:46:15     Re: system ticks

Mike Frysinger (UNITED STATES)

Message: 59409   

 

what exactly are you trying to do ?  right a kernel driver or linux userspace application or ?

QuoteReplyEditDelete

 

 

2008-08-01 12:00:16     Re: system ticks

Appalayagari Sreedhar (INDIA)

Message: 59762   

 

Hi Mike,

 

I want to use it in the kernel side.

 

I need to poll the PF pin for enabling the sport for avoiding the L/R channel swap anamoly in BF533.

 

In VDK we used VDK_Getuptime();

 

Can you please suggest me how to implement this.

 

Best Regards,Sreedhar.

QuoteReplyEditDelete

 

 

2008-08-01 14:01:44     Re: system ticks

Robin Getz (UNITED STATES)

Message: 59763   

 

Sreedhar:

 

Which anomaly are you talking about? All the existing anomalies should already have workarounds in the existing drivers.

 

-robin

QuoteReplyEditDelete

 

 

2008-08-02 06:49:31     Re: system ticks

Appalayagari Sreedhar (INDIA)

Message: 59802   

 

Hi Robin,

 

Anamoly is : 05000265 ( It still applies to 0.5 silicon revisons also as per the anamoly sheet of ADSP BF531/532/533)

 

So i want to poll the PF pin for avoiding the Channel swap,

if this workaround is already implemented for any other revisions, can you please let me know the path where i can find the work around.

 

Best Regards,Sreedhar

QuoteReplyEditDelete

 

 

2008-08-03 21:49:54     Re: system ticks

Mike Frysinger (UNITED STATES)

Message: 59815   

 

i dont see how those three topics are related at all.  the anomaly talks about poor board design leads to extra interrupts being fired.  binding to interrupt a or interrupt b wont workaround the problem.  simply "using VDK_Getuptime" wont change anything about the state either.

 

the end of the anomaly says that with 0.5+ silicon, you can enable the SPORT hysteresis function.  we do this for all parts already with 2008R1+.

Attachments

    Outcomes