Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: > Paul Walmsley <paul@xxxxxxxxx> writes: > >> Hi Kevin >> >> On Fri, 19 Oct 2012, Paul Walmsley wrote: >> >>> On Thu, 18 Oct 2012, Paul Walmsley wrote: >>> >>> > Here are some basic OMAP test results for Linux v3.7-rc1. >>> > Logs and other details at http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/ >> >> ... >> >>> > Failing tests: needing investigation >>> > ------------------------------------ >>> > >> >> ... >> >>> > PM tests: >>> >>> * 3730 Beagle XM: OPPs do not initialize >>> - Several "find_device_opp: Invalid parameters" messages appear on boot; >>> related warnings follow >>> - Cause unknown >> >> This one seems to be caused by this commit: >> >> commit 24d7b40a60cf19008334bcbcbd98da374d4d9c64 >> Author: Kevin Hilman <khilman@xxxxxx> >> Date: Thu Sep 6 14:03:08 2012 -0700 >> >> ARM: OMAP2+: PM: MPU DVFS: use generic CPU device for MPU-SS >> >> Care to take a look at it and fix it? >> > > Yup, will fix. Looks like this exposed some initcall ordering issues in > the Beagle board file when adding OPPs. Here's the fix: http://marc.info/?l=linux-omap&m=135093801330065&w=2 I'll be adding this to my PM-related fixes queue for v3.7-rc3. Kevin -- 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
