[PATCH 0/3] OMAP3: PM: Make PRM setup times and CPUidle latencies/threshold board specific

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

The setup times to be programmed in the PRM module on OMAP (for clksetup, voltsetup etc)
are board specific. They depend heavily on the PMIC used and even on different boards
with the same PMIC, they vary based on the sleep/wake sequence used, system clock speed et al.

The CPUidle latencies and hence thresholds (derived from latencies and Power consumption numbers)
and very much dependent on these setup values and hence also need to be board specific.

This patchset makes it possible for the PRM setup times and the CPUidle latencies/threshold numbers to be
configured from board files, and some default values are used if nothing gets passed from board files.

Only the 3430SDP board file is currently been modifed to pass these values and the rest of the 3430
based board's still pass NULL and hence use the default values defined.

regards,
Rajendra


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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux