Hi Paul,
On 01/17/2013 05:24 PM, Paul Walmsley wrote:
Here's the updated version (at the bottom of this message). Seems to work
based on a quick test on 2430SDP.
# shutdown -r -n now
shutdown: sending all processes the TERM signal...
shutdown: sending all processes the KILL signal.
Hi Jon
On Thu, 10 Jan 2013, Jon Hunter wrote:
During the migration to the common clock framework, calls to the
functions omap2xxx_clkt_vps_late_init() and
omap2xxx_clkt_vps_check_bootloader_rates() were not preserved for
OMAP2420 and OMAP2430. This causes the variables sys_ck_rate and
Hi Paul,
On 01/17/2013 12:51 PM, Paul Walmsley wrote:
Hi Jon
On Thu, 10 Jan 2013, Jon Hunter wrote:
During the migration to the common clock framework, calls to the
functions omap2xxx_clkt_vps_late_init() and
omap2xxx_clkt_vps_check_bootloader_rates() were not preserved for
OMAP2420 and
Hi Jon,
On Thu, 17 Jan 2013, Jon Hunter wrote:
Yes I still see it. You don't see it on reboot?
Ah that's probably explains the discrepancy - I missed the part about the
reboot.
The reason why there is such a large number is because
omap2_round_to_table_rate() is returning the value
Here's the updated version (at the bottom of this message). Seems to work
based on a quick test on 2430SDP.
# shutdown -r -n now
shutdown: sending all processes the TERM signal...
shutdown: sending all processes the KILL signal.
shutdown: turning off swap
shutdown: unmounting all file systems
During the migration to the common clock framework, calls to the
functions omap2xxx_clkt_vps_late_init() and
omap2xxx_clkt_vps_check_bootloader_rates() were not preserved for
OMAP2420 and OMAP2430. This causes the variables sys_ck_rate and
curr_prcm_set to be uninitialised on boot. On reboot, this
