On Thu, Dec 15, 2016 at 9:40 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Adam Ford <aford173@xxxxxxxxx> [161215 07:27]: >> On Thu, Dec 15, 2016 at 2:44 AM, Daniel Gomez <dgomez@xxxxxxxxxxx> wrote: >> > Thanks for your answer Tony, >> > >> > I would like to fix it but I don't know how to start. Any idea or >> > suggestion please? >> > I have patched kernel 4.3 with this patch with the same result: >> > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/294018.html >> > >> > Furthermore, which kernel version is recommended to be use? >> > >> > Daniel >> > >> > 2016-12-14 20:52 GMT+01:00 Tony Lindgren <tony@xxxxxxxxxxx>: >> >> >> >> * Daniel Gomez <dgomez@xxxxxxxxxxx> [161214 08:14]: >> >> > HI, >> >> > >> >> > I would like to know about the status for supporting 1GHz of DM3730 >> >> > processor (omap3) in the kernel mainline. >> >> >> >> Yeah unfortunately the voltdomain support is still missing. Somebody >> >> just needs to fix it.. >> >> >> >> I modified the om36xx.dtsi file to list 1000000 and 1375000 uV, but I >> couldn't figure out how to autodetect whether or not the >> DM3730/OMAP3630 was 800MHz or 1000. >> >> I was also told we should be running Smartreflex 1.5 (not 3), but I >> wasn't very successful in integrating the SR 1.5 patch to a modern >> kernel (but I didn't spend much time on it). >> >> From my understanding we need to have ABB, but it seems to >> semi-working on my 4.9 kernel. The min and max microvolts appear to >> be correct, but the microvolts reading is returning -22, so I think >> there might be something more remaining. > > Probably the version of smartreflex 1.5 patch to look at is the old > Nokia n9/n950 tree. > Looking at Smartreflex 2 in the 4.9 kernel, it shows: V2 is the update for the 45nm version of the IP used in OMAP3630 and OMAP4430 Based on that, is porting 1.5 really necessary? My understanding is that the DM3730 and the OMAP3630 are basically the same thing. adam > Regards, > > Tony -- 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
