________________________________________ From: Sergey Lapin [[email protected]] Sent: Tuesday, December 01, 2009 10:34 PM To: Premi, Sanjeev Cc: [email protected] Subject: Re: SR1: VDD autocomp is not active
On Tue, Dec 1, 2009 at 7:08 PM, Premi, Sanjeev <[email protected]> wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Sergey Lapin >> Sent: Tuesday, December 01, 2009 5:24 PM >> To: [email protected] >> Subject: SR1: VDD autocomp is not active >> >> Hi, all! >> >> on my OMAP3525-based custom board I get SR1: VDD autocomp is not >> active and SR2: VDD autocomp is not active >> quite frequently with PM branch. What that means, and how to fix it? > > Do you see them while trying to set the sr_vdd[1|2]_autocomp? > OR > During normal execution? During normal execution. > > What is the silicon version reported when Linux kernel boot up? OMAP3525 ES2.1 (l2cache iva neon isp ) I did notice an earlier mail where you mentioned about using an older kernel version. have to back-ported patches specific to silicon identification on this kernel/ It appears that efuse data required for SmartReflex to work may not be available on this silicon... leading to these messages. Right now, I am away from source code, will be able to verify in the morning. S. -- 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
