Hi, all! It seems discussion went off-list somehow, so I won't delete some quoting. On Wed, Dec 2, 2009 at 2:38 PM, Premi, Sanjeev <premi@xxxxxx> wrote: >> -----Original Message----- >> From: Sergey Lapin [mailto:slapinid@xxxxxxxxx] >> Sent: Wednesday, December 02, 2009 1:54 AM >> To: Premi, Sanjeev >> Subject: Re: SR1: VDD autocomp is not active >> >> > 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/ >> I use PM branch of linux-omap git. >> I just need to make my patches less disgusting by properly >> porting these. >> Actually now I think I could do this work even without >> appropriate tree, since >> amount of patches is not that big and API is not too different. These >> patches are >> not required to make board basically run. >> >> > >> > 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. >> Thanks, looking forward for your reply. > > You should try this with an ES3.1 silicon. If sr_enable() fails, we might > see this issue. It seems I only have ES2.1 silicon, so what should I do - disable SR functionality at all - somehow set values the other way? It seems SR is possible on this silicon, only efuse data are absent, so is there a way I could somehow fake these (with some known working values), so the stuff works? Thanks a lot, S. > >> >> S. >> -- 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
