On Fri, May 8, 2015 at 10:35 AM, Nikolay Dimitrov <picmas...@mail.bg> wrote: > Hi Tim, > > > On 05/08/2015 06:42 PM, Tim Harvey wrote: >> <snip> >> >> Your right - There is no indication in the IMX6SDLRM that OTP >> indicates either temperature grade 'or' speed grade, however my >> testing looks like they implement the same OTP settings for this as >> the IMX6DUAL/IMX6QUAD as indicated in the IMX6DQRM. >> >> I have tested these patches with the following SoC's I have available: >> - MCIMX6S7CVM08AC (IMX6S r1.2, Industrial temp, 800MHz) - shows >> 'industrial (-40C to 105C) 792 MHz' (correct) >> - MCIMX6S5EVM10AC (IMX6S r1.2, Extended Commercial temp, 1GHz) - shows >> 'extended commercial (-20C to 105C) 996 MHz (at 792 MHz)' (correct) >> - MCIMX6U7CVM08AB (IMX6DL r1.1, Industrial temp, 800MHz) - shows >> 'industrial (-40C to 105C) 792 MHz' (correct) >> - MCIMX6Q6AVT10AC (IMX6Q r1.2. Automotive temp, 1GHz) - shows >> 'automotive (-40C to 125C) 996 MHz (at 792 MHz)' (correct) >> >> I'll send our FAE a question to verify - perhaps your FAE simply >> answered the questions based on the reference manual (which is >> notoriously lacking info and in some cases wrong). >> >> I encourage anyone with additional parts to test these patches and >> report if they show accurate information. If anyone has any IMX6SX I >> would appreciate removing the check that ignores the OTP for that and >> seeing if the results make sense. > > > Here are the results from riotboard (imx6s) testing with your patches > against Stefano's tree: > > > Before: > CPU: Freescale i.MX6SOLO rev1.1 at 792 MHz > > After patch 1: > CPU: Freescale i.MX6SOLO rev1.1 996 MHz (at 792 MHz) > > After patch 2: > CPU: Freescale i.MX6SOLO rev1.1 996 MHz (at 792 MHz) > > After patch 3: > CPU: Freescale i.MX6SOLO rev1.1 // No idea why I lost the MHz values
Nikolay, thats an issue in my patch if you don't have CONFIG_IMX6_THERMAL. I'll fix in a followup patch version > > After patch 4: > CPU: Freescale i.MX6SOLO rev1.1 > > > MHz values are missing after patch 3, and looking diagonally at the > code I don't see a reason. Next, riotboard doesn't have > CONFIG_IMX6_THERMAL by default. When added, I get this: > > > $ make u-boot.imx > ... <snip> > > Are there additional CONFIG dependencies? Looks like CONFIG_IMX6_THERMAL also needs CONFIG_DM_THERMAL (includes thermal-uclass from drivers/thermal/Makefile) Thanks for testing this. If you can get it working please let me know what the actual part markings are on the parts you test with. Tim > > Regards, > Nikolay _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
