On Tue, Aug 19, 2014 at 06:27:04PM +0300, Mikko Perttunen wrote: > > Well, I would suggest using the hardware documentation as a base here. > > I don't have access to the internal driver, thus, it is hard to judge > > what is right, what is wrong. > > The hardware documentation (TRM) doesn't say anything about these > registers, so I've mostly gone by the downstream driver. FYI, the driver > is publicly available in the L4T kernel sources at > https://developer.nvidia.com/sites/default/files/akamai/mobile/files/L4T/kernel_src.tbz2. > I'm not how useful reading them would be, though. I also haven't seen anything about the calibration calculation in any hardware documentation so it may very well be the case that nothing has been documented and the official information source is the internal driver itself. Btw, this downstream driver code is most likely old code as I can only find kernel/arch/arm/mach-tegra/tegra11_socterm.c in there, and I do remember that on my development branch the file is named differently. The CONFIG2 value comparison I posted is most likely against a newer version of that code. I'm not sure if that new version of that code is publicly available anywhere yet. I'll need to investigate more if a newer version of that code calculates different calibration values than an older version of that code. I'm currently working on soc_therm for future chips, so I have plenty of time to investigate this. At least this internal driver can be used as a benchmark for code clarity. Mikko's code is a lot more clear than this internal driver, so that's why I decided to base my work on Mikko's code instead of this internal driver and which is why I noticed the missing --i bug. But now I'm wondering whether the calibration values are correct... -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
