Premi, Sanjeev said the following on 12/02/2009 04:23 PM: >> -----Original Message----- >> From: Sergey Lapin [mailto:slapinid@xxxxxxxxx] >> Sent: Wednesday, December 02, 2009 7:04 PM >> To: Premi, Sanjeev >> Cc: linux-omap@xxxxxxxxxxxxxxx >> Subject: Re: SR1: VDD autocomp is not active >> >> >>>> [sp] The code will allow you to do so; but without right values >>>> kernel execution can go haywire. >>>> Actually the entire silicon can go haywire due to bad voltages. :( yep kernel can go crazy as a result.. >>> Is it possible somehow to identify right silicon revision >>> >> before ordering? >> >>> I mean by part number or something? >>> >> Sorry for my ignorance, I've found answer on first question (answer is >> to read errata properly). >> >> >>> Also, is there some safe numbers somebody knows about, or is there >>> some way of generating them? >>> >> I still persist with this question, though. >> > > [sp] These numbers are based on silicon characterization process. > There is no other way to generate them. The numbers can change > between silicon lots. > > Actually can change even between silicons themselves. This is part of EFUSE values which we write on to each of the silicon. If the chip does not have SR NVALUES EFUSED, two options: a) Get a new chip which has SR enabled (or a platform such as zoom2 with 3430 ES3.1 silicon) b) Disable smartreflex :( Regards, Nishanth Menon PS: NOT recommended: you could choose to play around with my original patch for SR http://marc.info/?l=linux-omap&m=125623250803526&w=2 esp looking at the script involved. but I would not recommend to use it on a production system. -- 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
