OMAP PM late init with DT blob

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

 



Hi,

I am looking at adding PM support for AM335x based on l-o/master.
arch/arm/mach-omap2/pm.c has the following comment:

/*
 * In the case of DT, the PMIC and SR initialization will be done using
 * a completely different mechanism.
 * Disable this part if a DT blob is available.
 */
if (of_have_populated_dt())
        return 0;

Basic DT support for AM335x is already in mainline so this check causes
various PM related inits and also the registration of the suspend ops to be
skipped.

I tried searching the list archives for any discussion on this but could not
find anything. Can someone shed some light on the how the device tree is to
be used for PMIC and SR initialization. 

Any objections to moving the suspend ops registration before the DT blob check?

Regards,
Vaibhav B.


--
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