Kishore,

>    We need to find this out during runtime. Which register to read and
> how to
>    know the clock settings of DSP, ARM and L3?

-- You can use this small utility to read/write/dump register values from user 
space. This is only for debug purpose if you want to peek and poke at some 
registers from user space.

https://omapzoom.org/gf/download/frsrelease/152/964/debuginfo.out

The usage is

For reading 
./debuginfo.out r  <Hex registerAddress without 0x prefix> <regAccessSize =8, 
16, 32>

Eg: to read PM_PWSTCTRL_IVA2 register, it would be
./debuginfo.out r 483060E0 32

For writing
 # ./debuginfo.out  w <Hex registerAddress without 0x prefix> <regAccessSize 
=8, 16, 32> <value>

Eg: to write to PM_PWSTCTRL_IVA2 register, it would be
./debuginfo.out w 483060E0 32 <value>

For Dump
 # ./debuginfo.out a  <Hex registerAddress without 0x prefix> <numOfWordsToDump>

Eg: To dump first 100 values of IVA2_PRM registers
./debuginfo.out a  48306000 100

Thank you,
Best regards,
Hari

> -----Original Message-----
> From: [email protected] [mailto:linux-omap-
> [email protected]] On Behalf Of Krishna Kishore
> Sent: Wednesday, January 14, 2009 1:41 AM
> To: [email protected]
> Subject: OMAP3430 clock settings
> 
> 
> Hi,
> 
>    How do we find out clock settings on OMAP3430?
> 
>    We need to find this out during runtime. Which register to read and
> how to
>    know the clock settings of DSP, ARM and L3?
> 
> Regards,
> Kishore.
> SASKEN BUSINESS DISCLAIMER
> -------------------------
> This message may contain confidential, proprietary or legally privileged
> information. In
> case you are not the original intended Recipient of the message, you must
> not, directly or
> indirectly, use, Disclose, distribute, print, or copy any part of this
> message and you are
> requested to delete it and inform the sender. Any views expressed in this
> message are
> those of the individual sender unless otherwise stated. Nothing contained
> in this message
> shall be construed as an offer or acceptance of any offer by Sasken
> Communication
> Technologies Limited ("Sasken") unless sent with that express intent and
> with due
> authority of Sasken. Sasken has taken enough precautions to prevent the
> spread of
> viruses. However the company accepts no liability for any damage caused by
> any virus
> transmitted by this email
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to